[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Module variable
RE: Module variable
Fri, 6 Apr 2001 15:13:38 +0100
Thanks for the advice. I did not read the contents of that
URL you sent until Laine's posting. It was just what I needed.
From: address@hidden [mailto:address@hidden
Sent: 04 April 2001 22:40
Cc: address@hidden; address@hidden
Subject: Re: Module variable
Laine Stump writes:
> address@hidden (Larry Jones) writes:
> > http://www.cvshome.org/docs/manual/cvs_18.html#SEC171
> 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.
My "C-" firmly establishes me on the cutting edge of the avant-garde.
This message and any attachments are confidential and may be legally
privileged. Any opinion expressed in them may be personal to the author and
may not be shared by ShopSmart Ltd.If you are not the intended recipient you
must not disclose the contents to any other person. Please delete this
message and any attachments if received in error and e-mail the sender or
contact ShopSmart Ltd on +44 (0) 20 8 208 8800. Thank you.
ShopSmart Ltd, Company No: 03711211
Reg. Address: Britannia Business Centre, Cricklewood Lane, London NW2 1DZ