Hi
Today I woke up and was not able to log in to my system (ssh). Some
stuff worked (DNS for example, this box runs bind), altough the IMAP
server didnt work to well...
Anyway, I checked out local console:
maxproc limit exceeded by uid 0, please see tuning(7) and login.conf(5).
Repeated
On 22 jun 2006, at 09.57, [LoN]Kamikaze wrote:
Johan Ström wrote:
Anyway.. I'm using default login.conf, which have unlimited for all
resource limits.. So wtf is this?
Look at
# sysctl kern.maxproc
Okay, 4096 procs... But what was those 4k procs...On my newly booted
i got 127... Well I
Johan Ström wrote:
Anyway.. I'm using default login.conf, which have unlimited for all
resource limits.. So wtf is this?
Look at
# sysctl kern.maxproc
___
freebsd-stable@freebsd.org mailing list
In the last episode (Jun 22), Johan Strm said:
On 22 jun 2006, at 09.57, [LoN]Kamikaze wrote:
Johan Ström wrote:
Anyway.. I'm using default login.conf, which have unlimited for all
resource limits.. So wtf is this?
Look at
# sysctl kern.maxproc
Okay, 4096 procs... But what was those
repeated 38 times
Jun 22 11:30:00 pluto last message repeated 46 times
Jun 22 11:30:00 pluto kernel: maxproc limit exceeded by uid 0, please see
tuning(7) and login.conf(5).
Jun 22 11:30:01 pluto kernel: fxp0: promiscuous mode disabled
I just raised my maxpipekva to 64M .. see if it doesn't lock up yet
On 22 jun 2006, at 17.42, Dan Nelson wrote:
If it ever happens again, you can drop to the debugger with
Ctrl-Alt-ESC and run ps to get a list of running processes. You
might even be able to recover by killing some offending processes with
kill 9 pid, then continue with c.
Hm, I
On 22 jun 2006, at 18.45, Dan Nelson wrote:
In the last episode (Jun 22), Johan Strm said:
On 22 jun 2006, at 17.42, Dan Nelson wrote:
If it ever happens again, you can drop to the debugger with
Ctrl-Alt-ESC and run ps to get a list of running processes. You
might even be able to recover by
