RE: PID_MAX (was console hangs, but machine still up)

["Peter Kocks" <peter.kocks@baygate.com>]

I'll happily rebuild my kernel and see if that solves the problem,
but even so shouldn't the PID_MAX value be obeyed regardless of
which kernel I have?  That is, even if it was defined as 99,999
when I built it, I should not be getting preposterous PIDs at
98573.  Right?  Or is there other application code that uses PID_MAX.
I.e. do I have to rebuild all the applications, socks, squid,
newsyslog, etc?

--pk


> -----Original Message-----
> From: Federico G. Schwindt [mailto:fgsch@olimpo.com.br]
> Sent: Wednesday, March 03, 1999 10:41 PM
> To: Phil Homewood
> Cc: peter.kocks@baygate.com; tech@openbsd.org
> Subject: Re: PID_MAX (was console hangs, but machine still up)
> 
> 
> > I did see that once, as I recall. PID in the 30,000's.
> > 
> > 98573 is more than a little bogus, PID_MAX is defined in
> > <sys/proc.h> as 30000, yet I have may many PIDs higher than
> > this:
> > [snip]
> > Something's not right in the process allocation world, methinks.
> > 
> > Looking at sys/kern/kern_fork.c, around line 150, the spaghetti
> > gets the better of me. Somewhere a check for PID_MAX isn't
> > working correctly, apparently.
> 
>   PID_MAX has been updated a few times lately. The first modification
> change the PID_MAX value to 99999, then moved to 65535, and finally
> to the actual value, 32766.
>   Nothing is wrong there. Just need to recompile your kernel.
> 
>   Federico.-
> 
> -- 
> Let the programmers be many and the managers		Federico G. Schwindt
> few -- then all will be productive.			fgsch@openbsd.org
>