Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
jml at nykredit.dk wrote: > I did not realize the significane of the sleep command in the loginfo! > However there IS in fact a sleep.exe file in the NT Resource Kit, so this > behaviour is surely possible on the NT-platform. The lack of true background processes is probably more important. Even with START, I don't think the initial subshell (running the CVS commit) will exit until the second sub-sub-shell (running the CVS sandbox update). > Another matter is that > having the script wait for 2 seconds is hardly fool-proof. The cvs-commit > may for whatever reason not have finished within the 2 seconds. Remember that the commit is fired for each file individually, so 2 seconds is not unreasonable. This script is not intended to behave well for large updates; in use on a test web site it is great for small incremental updates (single files). Production sites are better handled manually at specific intervals. > I think it > would be more safe to make syncronization on fixed hours (e.g. with the AT > command on NT), and it will probably perform better, since the original > script (if I'm not mistaken) will do a complete update for each committed > file in a multi-file commit. If you look at my CVSNTUpd.exe, I use AT (with a ~1 minute granularity) to do just this... John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs