Originally I wrote:
=I am currently having problems running the ps utility with any of the
=options which specify that details on all running processes be
=returned: the process hangs (the session, not the OS), can only be
=interrupted by Ctrl-Z, and even then cannot be killed with signal 9.
=
=The rest of the system seems to be running normally (no errors have
=been reported).
It seems that an "rsh" job which was run by a user somehow locked up
all processes for that specific user, such that the ps utility could
not access any of its processes. This is why ps with any option for
all processes failed - it could not access processes owned by the
specified user. As I could not use ps to give a list of all processes
for this user, I used lsof (available on many FTP sites, definitely
worth getting) to find and kill this user's processes.
I still don't know how or why this user managed to block the process
table - any suggestions would be welcome.
Thanks to Tom Barkanic (tb_at_eci-cec.com) for his reply.
regards,
Matt
matthew.calthrop_at_reuters.com
Received on Wed Jan 15 1997 - 14:24:30 NZDT