Hi, long time lurker here, appreciate the list's work, noticed that Stephan Tinnemeyer wrote: <clip> > You should, however, make use of the OS's file lock mechanism > (if there is any) to prevent two instances of your script (which may be > started by a web user?) from concurrent access to the file.
I agree, I make & update static web site pages routinely, using the methods recommended in other posts to this thread, but rather than flocking files I write the new copy in a 'safe' place and then make a copy of it on the web server. This has the advantage of maintaining a backup file, and I also backup the old web site file before replacing it with the new copy. -- Dr. John Griffiths \( ~ )7 The Teahouse of Experience MAILTO:[EMAIL PROTECTED] http://www.frontier.net/~grifftoe/ O, call back yesterday. Richard II, act 3, sc. 2. *** If it's working, the diagnostics say it's fine. If it's not working, the diagnostics say it's fine. -- A proposed addition to rules for realtime programming -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
