Have you done anything with user-level cron jobs, or user-level LaunchAgents? For network NIS users we find that cron jobs don’t run after reboot, presumably because cron did it’s initial checks before ypbind ran. And since our users are on NFS-mounted homes, I can’t imagine that user-level launch agents would work at all after a reboot, although I admit I haven’t tried it yet. Not that I would find that a suitable replacement for users anyway…

I’m trying to come up with a fix (like a system launch agent that waits for NIS, and then nudges cron), but was wondering if you’d already dealt with this.

tom

So now I should change your script to look in the file you listed up to find the right log-file to observe.

By default, the periodic logs are in /var/log/: daily.out, weekly.out, and monthly.out, but many things, including the logfile names can be modified by editing the .conf files list above. In fact, since /usr/sbin/periodic itself is just a shell script, it’s pretty trivial to modify its behavior by modifying the shell script itself…

-Greg

I tried your script and called it via launchd at every startup (which often happens twice a day). Every single periodic script ran every time, until I found out, that my periodic scripts log to
/var/log/daily.log
/var/log/weekly.log
/var/log/monthly.log
but I have daily.out ect. too.

I changed your script and now it looks better. But what are the differences between both files and how can I change the log files?

I’ll probably file it anyway…