ksh: cannot fork - try again ??
since i've started doing C programming on my openbsd-3.8 release machine, i've had a problem with running processes. sometimes i get the following message when trying to issue shell commands: ksh: cannot fork - try again looking at my ulimit output, i see the following: $ ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 524288 stack(kbytes)4096 lockedmem(kbytes)316622 memory(kbytes) 945236 nofiles(descriptors) 128 processes128 should i change my login class settings in /etc/login.conf, or is sufficient to change them with $ ulimit -n 128, etc.? i'm not sure what's going on here, so any advice is appreciated. this is my desktop machine and i have a lot of stuff open concurrently on it. cheers, jake
Re: ksh: cannot fork - try again ??
On Fri, 14 Apr 2006, Jacob Yocom-Piatt wrote: since i've started doing C programming on my openbsd-3.8 release machine, i've had a problem with running processes. sometimes i get the following message when trying to issue shell commands: ksh: cannot fork - try again looking at my ulimit output, i see the following: $ ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 524288 stack(kbytes)4096 lockedmem(kbytes)316622 memory(kbytes) 945236 nofiles(descriptors) 128 processes128 should i change my login class settings in /etc/login.conf, or is sufficient to change them with $ ulimit -n 128, etc.? i'm not sure what's going on here, so any advice is appreciated. this is my desktop machine and i have a lot of stuff open concurrently on it. First check if your programming efforts aren't generating lots of runaway processes. If that's not the case, login.conf is the answer; ulimit one works for the current shell and processes forked by the current shell. BTW, ulimit -n is for file descriptors, not procceses. -Otto
Re: ksh: cannot fork - try again ??
2006/4/14, Jacob Yocom-Piatt [EMAIL PROTECTED]: since i've started doing C programming on my openbsd-3.8 release machine, i've had a problem with running processes. sometimes i get the following message when trying to issue shell commands: ksh: cannot fork - try again looking at my ulimit output, i see the following: $ ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 524288 stack(kbytes)4096 lockedmem(kbytes)316622 memory(kbytes) 945236 nofiles(descriptors) 128 processes128 should i change my login class settings in /etc/login.conf, or is sufficient to change them with $ ulimit -n 128, etc.? i'm not sure what's going on here, so any advice is appreciated. this is my desktop machine and i have a lot of stuff open concurrently on it. Hhmmm... is it KDE?, it may use many file descriptors, specially while browsing with Konqueror. cheers, jake -- Gerardo Santana Between individuals, as between nations, respect for the rights of others is peace - Don Benito Juarez http://santanatechnotes.blogspot.com/
Re: ksh: cannot fork - try again ??
since i've started doing C programming on my openbsd-3.8 release machine, i've had a problem with running processes. sometimes i get the following message when trying to issue shell commands: ksh: cannot fork - try again [rest deleted for brevity] Are you maybe running out of memory? Is your swap partition big enough? CU, Sico. --
Re: ksh: cannot fork - try again ??
Original message Date: Fri, 14 Apr 2006 21:05:55 +0200 (CEST) From: [EMAIL PROTECTED] Subject: Re: ksh: cannot fork - try again ?? To: [EMAIL PROTECTED] Cc: misc@openbsd.org since i've started doing C programming on my openbsd-3.8 release machine, i've had a problem with running processes. sometimes i get the following message when trying to issue shell commands: ksh: cannot fork - try again [rest deleted for brevity] Are you maybe running out of memory? Is your swap partition big enough? CU, Sico. -- i have 730MB of 1GB available and that likely answers your question about swap. i am also not running KDE, i use the default fvwm. i will change my login class to staff and restart my X session, a la otto's suggestion, to see if that fixes it. everybody who replied CC'ed me, so i got 3 duplicate replies since i'm subscribed to [EMAIL PROTECTED] why the CC fellas?
Re: ksh: cannot fork - try again ??
ksh: cannot fork - try again [rest deleted for brevity] Are you maybe running out of memory? Is your swap partition big enough? CU, Sico. -- i have 730MB of 1GB available and that likely answers your question about swap. I suppose. i am also not running KDE, i use the default fvwm. i will change my login class to staff and restart my X session, a la otto's suggestion, to see if that fixes it. Do try every suggestion, as the solution to your problem could be among them. everybody who replied CC'ed me, so i got 3 duplicate replies since i'm subscribed to [EMAIL PROTECTED] why the CC fellas? A matter of habit I suppose, sorry for that. With procmail I myself kill dupes so as to not have that problem. CU, Sico. --
Re: ksh: cannot fork - try again ??
Jacob Yocom-Piatt wrote:
everybody who replied CC'ed me, so i got 3 duplicate replies
since i'm subscribed to [EMAIL PROTECTED] why the CC fellas?
Add a recipe to your mailfilter; something like this:
# You don't want to miss you are CC-ed after all. You just don't want
# them in your maildir.
if (/^(Cc|To).*(misc|tech|bugs|gnats|source-changes)@/) {
to $DEFAULT/cc
}
# Han
