'ps' behavoir in Linux - Was - Re: array limits

Fairlight fairlite at fairlite.com
Sat Apr 17 00:05:24 PDT 2004


At Fri, Apr 16, 2004 at 09:35:59PM -0500 or thereabouts, 
suspect Jerry Rains was observed uttering:
> 
> This tells the files open but not the program that opened them and, again no 
> arguments.  Also, I have to be 'root' to list the directory.
> 
> Coastal:/proc/29589/fd # l
> total 0
> dr-x------    2 root     root            0 2004-04-16 20:58 ./
> dr-xr-xr-x    3 filepro  users           0 2004-04-16 20:58 ../
> lrwx------    1 root     root           64 2004-04-16 20:58 0 -> /dev/pts/2
> lrwx------    1 root     root           64 2004-04-16 20:58 1 -> /dev/pts/2
> lrwx------    1 root     root           64 2004-04-16 20:58 2 -> /dev/pts/2
> lrwx------    1 root     root           64 2004-04-16 20:58 3 -> 
> /appl/filepro/fpcust/key
> lrwx------    1 root     root           64 2004-04-16 20:58 5 -> 
> /appl/filepro/fpcust/index.A
> lrwx------    1 root     root           64 2004-04-16 20:58 6 -> 
> /appl/filepro/fpcust/index.B
> Coastal:/proc/29589/fd #

The arguments would be in cmdline if there were any, as Ken suggested.
However, I'm not sure you'll have more luck with that than with environ on
a swapped out process.

As for which program opened them, the program running at PID 29589 opened
those.  If that was dclerk, then dclerk did it.

Actually, on the system I'm looking at (Cobalt Linux 6.4), the symlink for
exe will be unreadable when the process is swapped out.  I wonder if they
changed that.

As for why it may be swapped out in the first place, try `free` and see
how much physical memory you have left, if any.  If you're buried in swap,
those aren't going to swap back in long enough to check on them until
you're doing something with them that brings (and -keeps-) them out of
a sleep state.  They're all flagged S, which means they're sleeping, so
they were safe to swap out like that.  You'd need to have them pretty much
actively doing something to resolve this situation, unless you toss more
RAM at the machine, or shut down enough that you can wake one up and have
enough room for it to stay swapped in once it's in.  You might consider
switching to a non-X runlevel like 3 for debugging purposes.  (`telinit 3`)
Just make sure you've saved out any of your data in your X apps before
doing that.  :)

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html


More information about the Filepro-list mailing list