A simple but intensive fork bomb were started on 5.0-current UP machine.
After it, /var/log/messages contains:
Mar 3 19:16:46 iv /boot/kernel/kernel: roc: table is full
Mar 3 19:16:46 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:46 iv last message repeated 42 times
Mar 3 19:16:46 iv /boot/kernel/kernel: proc: table <3>proc: table is full
Mar 3 19:16:46 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 41 times
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is fs full
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 42 times
Mar 3 19:16:47 iv /boot/kernel/kernel: proc:ll
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 43 times
Mar 3 19:16:47 iv /boot/kernel/kernel: table is full
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 42 times
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is futable is full
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 42 times
Mar 3 19:16:47 iv /boot/kernel/kernel: l
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 43 times
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: l
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:50 iv last message repeated 10212 times
Mar 3 19:17:16 iv /boot/kernel/kernel: roc: table is full
Mar 3 19:17:16 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table roc: table is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: ull
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 43 times
Mar 3 19:17:17 iv /boot/kernel/kernel: procull
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 43 times
Mar 3 19:17:17 iv /boot/kernel/kernel: table is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is f table is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: ll
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 43 times
Mar 3 19:17:17 iv /boot/kernel/kernel: proc:ll
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 43 times
Mar 3 19:17:17 iv /boot/kernel/kernel: table is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is futable is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: l
Mar 3 19:17:18 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:18 iv last message repeated 43 times
Mar 3 19:17:18 iv /boot/kernel/kernel: proc: l
Mar 3 19:17:18 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:18 iv last message repeated 3524 times
Mar 3 19:17:46 iv /boot/kernel/kernel: roc: table is full
Mar 3 19:17:46 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:47 iv last message repeated 3559 times
The message is generated with command
kern_fork.c:246: tablefull("proc");
The system in question is UP, 5.0-current of 2001-02-27
/netch
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
