Steve Rowley wrote: > cron: PID 4388: starting service `cron' failed: fork: 11, Resource > temporarily unavailable. > > It's starting to look to me as though the problem is either at the > cygrunsrv level or the WinXP level.
The problem is that the fork call is failing when cygrunsrv tries to launch cron. There are a number of reasons that fork might fail, but normally when this occurs you see it happen in your normal user account, not just when SYSTEM tries to do it, which I take it is not happening here. Dave already mentioned a number of known software programs that cause fork failures, and I take it they have been ruled out. The next thing I'd try would be running rebaseall, which involves installing the rebase package, stopping all Cygwin binaries, then running the rebaseall script from an ash shell. (There are directions in the README.) If *that* fails, then I'd try getting a SYSTEM-owned bash shell and seeing if you see general fork failures there. The method to do this is a little silly, but I think there is a simple script available to automate it if you search the archives for "sysbash". You might also try the latest snapshot of the cygwin DLL, but I'm not sure there's anything relevant that has changed. It's still worth doing though if you can't get it working. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
