L. V. Lammert wrote: > At 02:37 PM 1/26/2010 +0000, Helmut Schneider wrote: > >> I thought I had fat-fingered something with sysmerge, but I > >> re-extracted /etc/daily and compared, and there were no > differences. > > > > Same here, I upgraded from 4.5-stable and sysmerged a few times. > > I get one on a clean install, .. have not had time to troubleshoot. > Does this qualify as a bug <g>?
Seems sysmerge does not upgrade crontabs. Does *this* qualify a bug? :) Fresh install: 30 1 * * * /bin/sh /etc/daily 30 3 * * 6 /bin/sh /etc/weekly 30 5 1 * * /bin/sh /etc/monthly After upgrade from <4.6: # do daily/weekly/monthly maintenance 30 1 * * * umask 077; /bin/sh /etc/daily 2>&1 | tee /var/log/daily.out | mail -s "`/bin/hostname` daily output" root 30 3 * * 6 umask 077; /bin/sh /etc/weekly 2>&1 | tee /var/log/weekly.out | mail -s "`/bin/hostname` weekly output" root 30 5 1 * * umask 077; /bin/sh /etc/monthly 2>&1 | tee /var/log/monthly.out | mail -s "`/bin/hostname` monthly output" root Obviously since 4.6 daily/weekly/monthly bring their own mail routine with them. For me, "All four scripts now suppress section headers when there is no content to follow. When a script produces no output whatsoever, it does not send mail to root any more. This may require adjustment of your parser scripts."[1] was not clear enough. [1] http://www.openbsd.org/faq/upgrade46.html#newDWM -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn
