Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Players (O.T.)
by Sam Drinkard 29 Jan '06

29 Jan '06

Sorry for the off topic posting, but I'm not a real music person and know little about what software will do what. Without turning this into a big discussion for pro or con, could someone drop a line or 3 just stating the name(s) of some type music players? I'd probably want something that would play CD's and perhaps mp3's. I don't guess there is a "catch-all" like the windows media player that does it all is there? Thanks.. Snowman

5 7

dsniff berkley database issues
by Mark Sargent 29 Jan '06

29 Jan '06

Hi All, as a CCNA student and wishing to eventualy do CCSP, I wanted to learn all about what hackers use/do to infiltrate networks, and was introduced to dsniff at a Linux meeting, TLUG, in Tokyo, but, am having problems installing it. Please see below. checking for Berkeley DB with 1.85 compatibility... /usr/local/BerkeleyDB.4.4 configure: error: db_185.h or libdb.a not found in /usr/local/BerkeleyDB.4.4 or not configured with --enable-compat185 [root@localhost <mailto:root@localhost> dsniff-2.3]# ./configure --enable-compat185 --with-db=/usr/local/BerkeleyDB.4.4 I have installed the latest BDB, and have, as you can see, added the correct arguments for ./configure. Anyone know a workaround for this? I also tried via yum, but, nothing. # yum install dsniff Setting up Install Process Setting up repositories addons 100% |=========================| 951 B 00:00 dag 100% |=========================| 1.1 kB 00:00 update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 1.2 MB 00:04 dag : ################################################## 3574/3574 Added 40 new packages, deleted 0 old in 52.25 seconds Parsing package install arguments No Match for argument: dsniff Nothing to do Cheers. Mark Sargent.

4 4

Network Card Priority
by James Gagnon 29 Jan '06

29 Jan '06

Hi, Is it common for CentOS to give priority to one particular network card over a second card when activating on boot up? I have two NIC's in my machine... one is tied into my windows box with an internal IP using xover cable. The other is tied into my hub, which then leads out to the internet with a WAN IP. When I run a constant ping on both IP's from my windows box and watch the boot up phase of CentOS it gets to activating eth0 and I start getting a couple ping replies from the WAN IP as it completes activating. Then it activates eth1 the NIC I have my internal IP on and the ping replies for the WAN IP stop and I then start getting ping replies from the internal IP. Should that be happening by default? If so, is there a way to make it so that both NIC's respond to pings off bootup and are active? In network settings both are marked active and both are marked to activate on bootup... just seems one is forcing the other offline and im not sure if that can be corrected... Any info would be great... Thanks =) James G.

1 0

unsuscribe
by Anthony Lordi 28 Jan '06

28 Jan '06

I would like to unsuscribe from the CentOS group mailing list.What must I do? Tony

2 1

tinydns -some help needed
by Kai Sandsengen 28 Jan '06

28 Jan '06

Is there a tinydns or dns wizard that could give me some hints, please? I am setting up and testing tinydns, but have some problems figuring out how to route. I do get dnscache to listen on tinydns. Also I do not understand why it will not answer the given ip (127.0.0.1) to the name server. 1. Both services are up running and seems to be working fine, so why no reply, (on the first query/reply below)? 2. I am behind a firewall/router and have dynamic ip address from my isp. Can I set up the name server to be dynamic or how can I solve this by routing? --config info Dnscache is listening to the local nic 192.168.1.102 tinydns is listening to the local nic 192.168.1.100 Here's the query to dnscache where no ip given back: # dnsqr a test.example.net 1 test.example.net: 34 bytes, 1+0+0+0 records, response, noerror query: 1 test.example.net # dnsqr a server1.test.example.net 1 server1.test.example.net: 58 bytes, 1+1+0+0 records, response, noerror query: 1 server1.test.example.net answer: server1.test.example.net 86400 A 192.168.1.102 # cat /etc/dnscache/log/main/current | grep tx @4000000043d9f8b118a12724 tx 0 1 test.example.net. test.example.net. 7f000001 c0a80164 @4000000043d9f8b5212dcc1c tx 0 1 server1.test.example.net. test.example.net. c0a80164 7f000001 # cat /etc/tinydns/root/data .test.example.net:127.0.0.1:a:259200 .1.168.192.in-addr.arpa:127.0.0.1:a:259200 =server1.test.example.net:192.168.1.102:86400

4 6

Centos Folding@Home team!
by Sharon Kimble 28 Jan '06

28 Jan '06

Centos now has its own Folding@Home team! If you would like to learn more about what we do, please follow this <a href="http://folding.stanford.edu/">link</a> to the Folding@Home homepage. New to distributed computing?, its not a problem. Here is the simplest description: Many computers working on separate pieces of the same puzzle are faster than a few computers working on many pieces of the puzzle. By "distributing" the work load to as many computers as possible, results are faster and accumulate faster. This provides more information to the people who can use it, thus letting them actually work with the results instead of working to get results. Hopefully the above summary doesn't leave you lost and confused. If you are still with us then great, but if you're feeling lost? You can search <a href="http://www.google.com/search?hl=en&ie=UTF-8&q=distributed+computing&btnG=Go…">google</a> for distributed computing for more in depth information. Now on to Centos folders and Folding@Home. We are a team of members with various computer setups and knowledge. Our primary operating system of choice is Centos and our favourite distributed computing program is Folding@Home. You can see our team stats by clicking <a href="http://vspx27.stanford.edu/cgi-bin/main.py?qtype=teampage&teamnum=48721">here</a>, this should be updated regularly. Would you like to join the team? Well, if so it is as simple as visiting the <a href="http://folding.stanford.edu/download.html"Folding@Home</a> website and downloading the version you prefer. Once you've got it please read this <a href="http://www.fedoraforum.org/forum/showthread.php?t=18393&page=1&pp=15">FAQ</a> written by Jtang613. Please note, our team number is 48721. There now, its just as easy as that and now you are a part of the team. Welcome to the Fold! :) Further information about various installers and monitors can be found <a href="http://forum.folding-community.org/viewtopic.php?t=11700">here</a>. My personal preference is to use <a href="http://www.vendomar.ee/~ivo/">finstall</a> to install and a superkaramba theme to help monitor the work unit. Sharon. -- 13:21:27 up 3 days, 2:12, 1 user, load average: 2.07, 2.06, 1.93 A taste of linux http://www.sharons.org.uk/taste/index.html efever http://www.efever.blogspot.com/ Centos 4.2, KDE 3.5.0-1.7, OpenOffice 2.0.1 Registered Linux user 334501

1 0

Has anyone had success getting on-board sound to work on a Tyan S2895?
by David J. Mellor 28 Jan '06

28 Jan '06

My setup is as follows: Motherboard: Tyan S2895 CPU: Two Opteron 275s Memory: 4 GB Disk: Three 250 GB SATA drives attached to a 3Ware 9500S-4LP RAID card Video: Nvidia GeForce 7800 The only hardware that I have added to the motherboard is the 3Ware card and the Nvidia card. The disks are configured as a RAID 5 array, and the machine boots from this array. I installed CentOS 4.2 x86 on this system without any problems during the installation. The on-board sound card was recognised and the correct driver (snd_intel8x0) installed to handle it. However, on rebooting into the SMP kernel after the install, the installation proved to be completely unstable. The kernel would panic sometimes during startup and sometimes during shutdown. The uniprocessor kernel seemed to be stable, but I noticed the following error messages appearing on the console during startup (the same error messages also appeared when booting into the SMP kernel): 3w-9xxx: scsi0: ERROR: (0x03:0x0104): SGL entry has illegal length:address=0x37077000, length=0xFF, cmd=X. Suspecting that there might be a driver incompatibility with my particular hardware configuration, I downloaded one of the Fedora 4 kernel sources from the 2.6.12 series, and compiled my own SMP kernel. This solved the stability issue, and I have been using this intensively for four months without experiencing any system crashes. Unfortunately, I have been unable to get the on-board sound to work. If I use XMMS to play an MP3 file (I have the XMMS MP3 plugin from the Dag Wieers repository installed), then on hitting the play button nothing happens. It is not that XMMS thinks that it is processing the file but no sound is being produced, rather the playback counter stays at "00:00". If I visit a web page containing a Flash animation with sound, Firefox locks up and has to be killed. I have compiled other Fedora kernels from source (2.6.14) and the same behaviour is observed. I also cannot get sound to work with the 2.6.9 uniprocessor kernel supplied with CentOS 4.2. I know that the hardware on the motherboard is not faulty, because the machine is set up to dual-boot into CentOS or Windows XP. On Windows, there is no problem with the sound, and interestingly once I have booted into Windows if I then reboot into Linux then the sound will work under Linux (although sound mixing is still a problem - one application outputting sound will cause a second application trying to output sound to stall until the first is finished). Has anyone on this list experienced the same problems, and if so found a way to overcome them? Failing that, does anyone have any suggestions for any tweaks I can make to my system to make the sound work without having to boot into Windows first? Thanks, David Mellor.

2 1

gfs performance
by Jure Pečar 28 Jan '06

28 Jan '06

Hi all, Since I've got no reply on redhat cluster list, I'm trying here ... I'm testing a rhcs4 cluster with gfs. I noticed some poor performance while tarring data from a gfs volume to a local disk from both nodes at the same time, so I deceided to have a closer look. Here are the bonnie++ results: http://jure.pecar.org/gfs/ I don't know what to think of these ... but I doubt it's normal for performance to go down by an order of magnitude when both nodes are doing some i/o to the shared file system ... I'd like to see some numbers from other gfs systems to see if this is normal and if it is not, how to figure out what's wrong and how to fix it. Thanks, -- Jure Pečar http://jure.pecar.org/

2 3

can't install cyrus-sasl-devel using yum
by spart cus 28 Jan '06

28 Jan '06

hi guys, im having some erro when installing cysrus-sasl-devel #yum install cyrus-sasl-devel error --------------------------------- What are the most popular cars? Find out at Yahoo! Autos

2 1

php-ldap can't log on with browser
by Kai Sandsengen 28 Jan '06

28 Jan '06

It has been some posting about this issue, but I cant find a solution I can't log on to my ldap server port 389 with my browser. service seems to be running. I am not running selinux, port 389 are open on both client and server. Message from browser: Access to this port is disabled for security reasons. Added command (hint from earlier posting) and got this list # netstat -aptn | grep :389 tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33057 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32833 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33058 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:33053 127.0.0.1:389 ESTABLISHED 2576/httpd tcp 0 0 127.0.0.1:33055 127.0.0.1:389 ESTABLISHED 2574/httpd tcp 0 0 127.0.0.1:33054 127.0.0.1:389 ESTABLISHED 2575/httpd tcp 0 0 127.0.0.1:33057 127.0.0.1:389 ESTABLISHED 2572/httpd tcp 0 0 127.0.0.1:33058 127.0.0.1:389 ESTABLISHED 2569/httpd tcp 0 0 127.0.0.1:33069 127.0.0.1:389 ESTABLISHED 2573/httpd tcp 0 0 127.0.0.1:33068 127.0.0.1:389 ESTABLISHED 2570/httpd tcp 0 0 127.0.0.1:33067 127.0.0.1:389 ESTABLISHED 2571/httpd tcp 0 0 127.0.0.1:33084 127.0.0.1:389 ESTABLISHED 3235/-bash tcp 0 0 127.0.0.1:389 127.0.0.1:33093 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:33093 127.0.0.1:389 ESTABLISHED 3269/-bash tcp 0 0 127.0.0.1:389 127.0.0.1:32837 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:32815 127.0.0.1:389 ESTABLISHED 2443/cupsd tcp 0 0 127.0.0.1:32837 127.0.0.1:389 ESTABLISHED 2494/xinetd tcp 0 0 127.0.0.1:32833 127.0.0.1:389 ESTABLISHED 2479/sshd tcp 0 0 127.0.0.1:32851 127.0.0.1:389 ESTABLISHED 2563/xfs tcp 0 0 127.0.0.1:32861 127.0.0.1:389 ESTABLISHED 2625/dbus-daemon-1 tcp 0 0 127.0.0.1:32856 127.0.0.1:389 ESTABLISHED 2615/atd tcp 0 0 127.0.0.1:32905 127.0.0.1:389 ESTABLISHED 2664/sh tcp 0 0 127.0.0.1:389 127.0.0.1:32905 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33067 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:43309 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43308 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43311 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43310 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43305 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43304 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43307 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43306 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43301 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43303 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43302 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43298 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43325 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43324 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43327 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43326 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43321 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43320 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43323 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43322 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43317 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43316 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43319 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43318 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43313 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43312 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43315 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43314 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:389 127.0.0.1:33069 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:43373 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43372 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43375 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43374 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43369 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43368 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43371 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43370 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43365 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43364 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43367 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43366 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43361 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43360 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43363 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43362 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43389 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43388 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43391 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43390 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43385 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43384 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43387 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43386 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43381 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43380 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43383 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43382 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43377 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43376 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43379 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43378 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43341 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43340 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43343 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43342 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43337 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43336 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43339 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43338 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43333 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43332 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43335 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43334 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43329 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43328 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43331 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43330 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43357 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43356 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43359 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43358 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43353 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43352 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43355 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43354 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43349 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43348 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43351 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43350 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43345 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43344 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43347 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43346 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43437 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43436 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43439 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43438 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43433 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43432 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43435 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43434 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43429 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43428 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43431 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43430 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43425 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43424 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43427 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43426 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43453 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43452 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43455 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43454 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43449 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43448 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43451 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43450 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43445 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43444 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43447 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43446 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43441 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43440 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43443 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43442 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43405 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43404 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43407 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43406 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43401 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43400 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43403 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43402 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43397 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43396 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43399 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43398 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43393 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43392 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43395 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43394 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43421 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43420 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43423 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43422 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43417 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43416 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43419 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43418 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43413 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43412 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43415 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43414 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43409 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43408 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43411 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43410 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43457 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43456 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43459 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:43458 127.0.0.1:389 TIME_WAIT - tcp 0 0 127.0.0.1:389 127.0.0.1:33068 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32815 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32851 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32856 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33053 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:32861 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33084 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33055 ESTABLISHED 2407/slapd tcp 0 0 127.0.0.1:389 127.0.0.1:33054 ESTABLISHED 2407/slapd tcp 0 0 :::389 :::* LISTEN 2407/slapd

2 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss