Richard Lynch <mailto:ceo@xxxxxxxxx> on Friday, January 28, 2005 11:36 AM said: > Chris W. Parker wrote: >> The two options I've come up with both involve adding a job(s) to >> crontab. >> >> 1. Individual jobs are added to the users crontab file. This could >> result in LOTS of entries in crontab, but less load on the server. > > Actually, probably MORE load, as you'll be firing off *WAY* too many > php processes, as soon as the schedule gets at all busy. Ahh yes. Very true. > Actually, you might even want to create a special user with limited > access/ability (or just use 'nobody') and have THAT user handle all > the scheduler notifications et al. > > Unless you *NEED* to have the scheduler doing things on that user can > do with the OS, it would be better to limit it to doing only what it > NEEDS to do. Actually it would just be sending out emails and updating the DB. Thanks for the ideas! Chris. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
