Yeah, i actually implemented it with cron jobs.
I tried to find out how come, without much success. Anyway, i didnt want to spend too much time on this. The cron does the job. Thanks for your answers tho. Jean-Pierre Sevigny -----Original Message----- From: Derek Robert Price [mailto:[EMAIL PROTECTED]] Sent: August 9, 2002 4:33 PM To: Jean-Pierre Sevigny Cc: [EMAIL PROTECTED] Subject: Re: starting background processes from admin files Jean-Pierre Sevigny wrote: >The problem is in client/server mode, the client hangs until the >background process finishes. In my loginfo file, i have > >ALL /u01/cvsutils/bin/cvsWatchOn.sh %{s} & > >In server mode, it is fine. > >My cvs server is on solaris 5.8, version 1.11.2. > >Jean-Pierre Sevigny > > Hmm. Yes, you're correct. Excuse me for my off the cuff answer, but CVS appears to wait for its child processes in client/server mode. As a workaround, you could use your script to queue the run and have a cronjob check the queue once a minute and lauch the real job. I'm not sure how CVS is tracking its children, but you might try having you script daemonize too (close stdin, stdout, and stderr) and see if that lets it escape notice. Derek -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com -- Five days is not too long to wait for a gun. Five days is not too long to wait for a gun. Five days is not too long to wait for a gun... - Bart Simpson on chalkboard, _The Simpsons_ _______________________________________________ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
