Jean-Pierre Sevigny wrote:
>Hi,
>
>I am not sure if this is a CVS issue, or a Unix issue, but here it is.
>
>I would like to start some processes in the background for some operations,
>have something like
>ALL prog %{s}&
>in the loginfo file, for example.
>
>I want to do that so i dont hang the cvs commands for the users, when i dont
>need to,
>for the time prog runs.
>
>When i'm running CVS locally, it is fine, the cvs command finishes and the
>"prog"
>runs in background. In client/server mode, the cvs client has to wait for
>"prog"
>to finish. Any idea why, and how can i have the client not waiting for the
>background process to finish ?
>
>
<http://www.cvshome.org/docs/manual/cvs_18.html#SEC173>
Notice the sleep command in the example. This is so that any cvs
processes run in the subshell won't create locks to stop the cvs server
process, or worse, create a deadlock situation. You can play with the
timing. Since you specified "ALL" in the loginfo file too, your `prog'
will get called once per directory. If it is operating recursively and
locking dirs before the parent process finished running, you might see
similar behavior.
You might like to take a look at the commit_prep.in and log_accum.in
scripts in the contrib directory of the CVS source distribution.
Derek
--
*8^)
Email: [EMAIL PROTECTED]
Get CVS support at http://ximbiot.com
--
Computer Lie #1: You'll never use all that disk space.
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
