[Top][All Lists]

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

Re: Module variable

From: Larry Jones
Subject: Re: Module variable
Date: Wed, 4 Apr 2001 17:40:08 -0400 (EDT)

Laine Stump writes:
> address@hidden (Larry Jones) writes:
> > 
> >
> My problem with that was that it was (potentially) run as a different
> user each time, resulting in permission errors (since the users don't
> have g+w in their umask). I just wrote a short setuid program that
> executed the same command.

It would have been simpler to add a umask command before the update.

> I also seem to recall that it gets called once for each file, which
> leads to bunches of "waiting for xxx's lock on yyy" messages when a
> single cvs commit ends up committing multiple files (since multiple
> copies of it are running at once).

No, it gets called once per directory.  Since locks are done on a
per-directory basis and the example command sleeps for two seconds
before starting the update (to give the commit time to complete), it
usually isn't a problem, although it might be beneficial to increase the
time delay for a sufficiently large tree.

-Larry Jones

My "C-" firmly establishes me on the cutting edge of the avant-garde.
-- Calvin

reply via email to

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