get process id

[Fairlight]

Is it just me, or did Bill Vermillion say:
> 
> But not on the beast.  Looking at currently running processes
> and performing   grep ^8  on a ps -ax yields this:
> 
> 88166  ??  I      0:00.02 sshd: bv [priv] (sshd)

> Just FYI.  The inode numbers that are over a million usually take
> a second look to get them correct too.
> 
> Much of 'beastie' has been 64 bit for a few years now.   

And UW 7.1 with Non-Stop Clustering (NSC, now defunct and discontinued--not
that it worked exactly correctly unless you specifically recompiled OSR5
binaries with the UDK) not only -used- 60000+ PID-space, it actually
-started- PID's above the range of a regular PID's length on a 32bit
system.  Any processes forking would not work correctly due to the
returning PID value being out of range.  Ugh.

Solaris, OTOH, has been 64bit on Sparc for...well wasn't Sparc always
64bit?  And our PID's roll somewhere around the 30-32K range on the 5.7
and 5.8 systems here.  Not sure how tunable that is, nor do I intend to
ask, since it makes little difference.  Just saying, 64bit OSes don't
necessarily mean that everything is written or configured to utilise the
full resources available.

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