[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: starting background processes from admin files

From: Derek Robert Price
Subject: Re: starting background processes from admin files
Date: Fri, 09 Aug 2002 08:49:10 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606

Jean-Pierre Sevigny wrote:


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
runs in background. In client/server mode, the cvs client has to wait for
to finish. Any idea why, and how can i have the client not waiting for the
background process to finish ?


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.



Email: derek@ximbiot.com

Get CVS support at http://ximbiot.com
Computer Lie #1: You'll never use all that disk space.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]