Your message dated Wed, 26 Mar 2008 20:51:42 +1100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#472661: psmisc: fuser outputs nothing at all
has caused the Debian Bug report #472661,
regarding psmisc: fuser outputs nothing at all
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
472661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472661
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: psmisc
Version: 22.3-1
Severity: important
I cannot seem to get fuser to report the PID of a process listening on
a given TCP port (9100). I'm trying to port a script used on a redhat
system. If I use lsof, I can see the information:
bigindy0:~# lsof | grep 9100
java 29196 easyask 5u IPv6 70376
TCP *:9100 (LISTEN)
Here's what I get with fuser:
bigindy0:~# fuser -n tcp 9100
bigindy0:~#
Running the same command on the old redhat system gives output:
[EMAIL PROTECTED] /etc/config $ /sbin/fuser -n tcp 9100
9100/tcp: 2157 6871 6961 6962 6963 6964 6965 6966 6967
6968 7004 7006 7010 7011 7012 7013 7015 7017 7020 7021 7022 7024
7025 7026 7027 7028 7039 7040 7041 7042 7044 7045 7047 7049 7050
7051 7052 7055 7056 7070 7071 7072 7073 7074 7075 7076 7077 7078
7079 7080 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 14543
14545 15352
The machine is a Dell PE1950 III and has two quad-core Intel processors
and 32GB of RAM, which may be relevant factors.
bigindy0:~# cat /proc/cpuinfo | grep Intel
vendor_id : GenuineIntel
model name : Intel(R) Xeon(R) CPU E5440 @ 2.83GHz
vendor_id : GenuineIntel
model name : Intel(R) Xeon(R) CPU E5440 @ 2.83GHz
vendor_id : GenuineIntel
model name : Intel(R) Xeon(R) CPU E5440 @ 2.83GHz
vendor_id : GenuineIntel
model name : Intel(R) Xeon(R) CPU E5440 @ 2.83GHz
vendor_id : GenuineIntel
model name : Intel(R) Xeon(R) CPU E5440 @ 2.83GHz
vendor_id : GenuineIntel
model name : Intel(R) Xeon(R) CPU E5440 @ 2.83GHz
vendor_id : GenuineIntel
model name : Intel(R) Xeon(R) CPU E5440 @ 2.83GHz
vendor_id : GenuineIntel
model name : Intel(R) Xeon(R) CPU E5440 @ 2.83GHz
bigindy0:~# free
total used free shared buffers cached
Mem: 32942720 7912812 25029908 0 226620 7236060
-/+ buffers/cache: 450132 32492588
Swap: 9900024 0 9900024
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages psmisc depends on:
ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries
ii libncurses5 5.5-5 Shared libraries for terminal hand
psmisc recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: psmisc
Version 22.4-1
On Tue, Mar 25, 2008 at 10:21:43AM -0600, Shawn Heisey wrote:
> I cannot seem to get fuser to report the PID of a process listening on
> a given TCP port (9100). I'm trying to port a script used on a redhat
> system. If I use lsof, I can see the information:
Hello,
This is a known bug (397033) and was fixed in version 22.4-1 of psmisc
package. Basically I messed up the tcp and udp port parsing and for some
reason it works sometimes. It was almost a year ago so the details are
a bit hazy by now.
RedHat's fuser probably works because they're ages behind.
- Craig
--
Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
http://www.enc.com.au/ csmall at : enc.com.au
http://www.debian.org/ Debian GNU/Linux, software should be Free
--- End Message ---
