PID_MAX (was console hangs, but machine still up)

[Phil Homewood <philh@mincom.com>]

Peter Kocks wrote in private mail:
> I don't think this is related, but I am also getting
> 
> newsyslog: preposterous process number: 98753
> 
> messages from the Cron Daemon.  Are you?  If so, please
> post to tech@openbsd.org ; otherwise, it is something else.

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:

30221 ??  S       0:08.15 /usr/local/bin/socks5
30357 ??  I       0:04.08 /usr/local/bin/socks5
30654 ??  S       0:09.44 /usr/local/bin/socks5
30747 ??  S       0:03.43 /usr/local/bin/socks5
30932 ??  Z       0:00.00 (smtpfwdd)
31703 ??  S       0:03.44 /usr/local/bin/socks5
32079 ??  S       0:04.46 /usr/local/bin/socks5
32160 ??  S<s     0:12.05 /usr/local/sbin/ntpd (xntpd)
32251 ??  S       0:03.64 /usr/local/bin/socks5
32276 ??  S       0:06.12 /usr/local/bin/socks5

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.
-- 
Phil Homewood             DNRC          email: philh@mincom.com
Postmaster and BOFH
Mincom Pty Ltd                          phone:  +61-7-3303-3524 
Brisbane, QLD Australia                 fax:    +61-7-3303-3269