After a few hours of bobs running the server on Mac OS X 10.3,
bobs will cause some processes that normally run and the quit
(sleep, cron, postdrop) to not quit. loopcmd is also listed multiple
times in the process list. After a while the system will exceed it's
maximum process count and not allow anything new to startup.(I
can't open Terminal or Activity Viewer to quit any processes. If I
leave a terminal window open the kill command will return
"Resource currently not available"). Uninstalling bobs completely
removed the problem. I'm attaching my exported process file
from the time that I left Activity Viewer open at startup. It's in
standard xml format
Logged In: YES
user_id=101354
I know there's a problem with the cron check_loop/cmdloop
because check_loop turns into a zombie on my redhat system.
I'm not familiar with Mac OS X and I don't see the Activity
Viewer file attached. Please resubmit this bug to the
bobs-devel mailing list, that's the only list that's
monitored by all the developers.
Thanks,
Joe Zacky
Logged In: YES
user_id=101354
bobs release 0.6.2 will start cmdloop from /etc/init.d/
instead of crontab. Hopefully this will fix you problem. Not
having access to a Mac OS X system I can't test it myself.
Logged In: YES
user_id=101354
Release 0.6.2 is out. Hoping to hear from anonymous user if
the problem is fixed in this release.