What/how does lsof work? In trying to play around trying to identify Unidata user sessions and their port/pid correlation, I tried to do a lsof on one session via the "port" and the command has not returned going on now for 5 minutes. Looking for lsof, I discovered my command along with another one w/o any arguments and a PPID of 1.
Tried killing without and with -9 and yet the process prevails.
was a typo - I had wanted to look at 1199 but inadvertently dropped off the trailing (or first 9). Yeah, yeah â lucky it wasnâ t a kill or something else like that. 8-).
There are two sections of the lsof man page that you should have read BEFORE using lsof: "BLOCKS AND TIMEOUTS" and "AVOIDING KERNEL BLOCKS". Lsof is kernel intrusive and can certainly block on some operations but you are allowed to adjust timeouts and void potentially blocking system calls using the -b option.
Okay, I have been educated as to the future use of lsof AND reading through the entire manpage of a command before trying it. But what do I do now? Do they effectively become zombies and need to wait for a reboot to clear them out? Any potential harm - reason why I am asking is that the box hasn't been rebooted in almost 1/2 year and the people here frown on even thinking of rebooting....
