Re: fork failed: Resource temporarily unavailable

2000-02-24 Thread F.P. Groeneveld
are you using ulimits? i dont know if sash has builtin resource limits, check ulimit -u, for most systems it should say unlimited, unless it is set by you(or another admin) for most of my systems i set it to 12 which is pretty tight. how many processes are running on the system? if its a big

Re: fork failed: Resource temporarily unavailable

2000-02-24 Thread Ethan Benson
On Thu, Feb 24, 2000 at 01:08:21AM +0100, F.P. Groeneveld wrote: I don't run ulimits... ulimits -u : command not found. As for a hard limit on processes... If I log in as root (as opposed to su), I have no problem whatsoever. Only when I su to root do I have this problem? if its only when

Re: fork failed: Resource temporarily unavailable

2000-02-24 Thread aphro
On Thu, 24 Feb 2000, F.P. Groeneveld wrote: derk I don't run ulimits... ulimits -u : command not found. As for a hard limit derk on processes... If I log in as root (as opposed to su), I have no problem derk whatsoever. Only when I su to root do I have this problem? try ulimit -u (not plural)

Re: fork failed: Resource temporarily unavailable

2000-02-24 Thread \F.P. Groeneveld\
Ethan Benson [EMAIL PROTECTED] wrote: : On Thu, Feb 24, 2000 at 01:08:21AM +0100, F.P. Groeneveld wrote: : if its only when you use su it sounds like resource limits. the : command is ulimit -u not ulimits -u. i have not touched resource : limits yet on debian (have not got around to it) but

Re: fork failed: Resource temporarily unavailable

2000-02-24 Thread \F.P. Groeneveld\
aphro [EMAIL PROTECTED] wrote: : *I* can't think of anything else that'd cause this on a lightly loaded : machine(I've seen it without ulimits on a machine say under a syn flood : attack or something) so if its not ulimits im 'fraid i cant offer any : further advice :/ Thanks, it WAS ulimit

Re: fork failed: Resource temporarily unavailable

2000-02-24 Thread aphro
On 24 Feb 2000, F.P. Groeneveld wrote: derk Okay, you are 100% correct. nmbd had respawned a zillion times. Killing derk them solved the problem. Still, I don't understand why logins through ssh derk are not affected? Also, I couldn't find where ulimit is set. Anyone? i think 256 is just the

Re: fork failed: Resource temporarily unavailable

2000-02-24 Thread David Wright
Quoting aphro ([EMAIL PROTECTED]): On 24 Feb 2000, F.P. Groeneveld wrote: derk Okay, you are 100% correct. nmbd had respawned a zillion times. Killing derk them solved the problem. Still, I don't understand why logins through ssh derk are not affected? Also, I couldn't find where ulimit is

fork failed: Resource temporarily unavailable

2000-02-23 Thread \F.P. Groeneveld\
I'm having a very weird problem. I'm running potato, upgraded to the latest version yesterday evening. I'm logging in remotely, using ssh to a normal user on my box, and su to root. Then, whatever command I type, I get: fork failed: Resource temporarily unavailable This happens both as root

Re: fork failed: Resource temporarily unavailable

2000-02-23 Thread aphro
to a normal user on my box, and su to derk root. Then, whatever command I type, I get: derk derk fork failed: Resource temporarily unavailable derk derk This happens both as root and as sashroot (root using sash instead of derk bash) What's happening, and how can I fix it? are you using ulimits? i dont