site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Hi, I can't think of anyplace else to ask for info... In panther I solved the problem of having cron run at the designated time ( 3:15 for daily stuff...) by enqueueing a "wakeup" request via the PM Queue Manager for a couple of minutes ahead of time time that cron was supposed to fire. (The cron job would also enqueue a wakeup for the next day). This has worked quite well in Panther for the last year. This last weekend I installed Tiger and of course found that "launchd" is the new one true way :) com.apple.periodic-daily.plist is now the "job" that does the periodic daily stuff that cron used to do. According to the plist it is supposed to trigger at 3:15 just as cron did. Regrettably it appears that launchd is *not* launching the job. The system log shows the system was awakened at 3:13:30. However none of the logs are rotated and there is nothing appended to daily.out the log file. I *can* manually invoke the job via launchctl and everything works like it ought to ( except that I can't mail anything to me...I get a message from csh that $home is not defined and I get empty mail. How does csh get involved?) Any suggestions as to why the job is "evidently" not getting launched at the appropriate time? If the system is put to sleep does launchd lose track of when the next job is supposed to run? My PMQueue manager stuff can be found at: http://homepage.mac.com/levanj/Cocoa Help... Jerry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com