SUMMARY: lsof on t64u 5.1b - no info for PIDs > 65535

From: Fish, Russell C \(GE Healthcare\) <"Fish,>
Date: Thu, 28 Dec 2006 17:00:25 -0500

Thanks to Kazuro Furukawa, who confirmed that lsof works just fine for
PIDs > 65535. After some testing, it now appears that the problem is
process related--not sure how/why they're getting confused but a restart
of the associated application fixes them right up. I've enclosed the ksh
script I used to test in case anyone else ever runs across this.

Happy new year to everyone on the list.

#!/bin/ksh
for pid in `ps -ef | awk '{print $2}' | grep "^[1-9]"`; do
  if [[ -z `/usr/local/bin/lsof -p $pid` ]]; then
    # show process; skip [icssvr_daemon_fr], <defunct>, etc.
    ps -ef | grep " $pid " | grep -v grep | grep -v ' \<' | grep -v '
\['
  fi
done

-----Original Message-----
From: Fish, Russell C (GE Healthcare)
Sent: Thursday, December 21, 2006 1:13 PM
To: tru64-unix-managers_at_ornl.gov
Subject: lsof on t64u 5.1b - no info for PIDs > 65535

Hi managers--

I'm seeing strange behavior on some but not all of our 5.1b boxes when
running lsof--it returns output fine for lower-numbered process IDs, but
nothing for higher-numbered ones (I'm guessing 65535 based on
experimentation). Other servers run fine. The lsof version is 4.77, and
I've tried all the normal stuff (/proc is mounted, etc.) with no
success. Anyone seen this and have a pointer to a config change or
something?

--Russ
Received on Thu Dec 28 2006 - 22:02:18 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:45 NZDT