Greg Beaver wrote: [snip] Does your crontab script use file locking to make sure that it isn't accessing a script at the same time as the webserver or another process? [/snip]
Yes, I create a lock file when the script is called, but the only time I've ever seen a conflict there is when these parse errors occur and the lock file is therefore not removed at the end of the script. In this case what happens is the next time the script is called, it sees that a previous lock file exists, deletes said file, and waits for the script to be called next time. Any other time the scripts encounter internal errors (pages scheduled for publishing which are not found, etc.) the script exits gracefully, recording the error and removing the lock file such that the script can run the next time it's called. Can you give me an idea of why you think this might raise the parse errors if the script were accessing a script at the same time as the server or another process? Reason I ask is that the scripts accessed by the crontab script are not accessed by anything but that crontab script. Cheers and TIA, Pablo -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
