On Wed, Feb 05, 2003 at 05:57:30PM +0900, CHOI Junho wrote: [...] > ---------------------- > CVSUP=/usr/local/bin/cvsup -g -L2 -h localhost > CVSUPDIR=/b/FreeBSD/cvsup > > # source sync > 0 */1 * * * $CVSUP $CVSUPDIR/4_7-supfile > /dev/null > 20 */1 * * * $CVSUP $CVSUPDIR/5_0-supfile > /dev/null > 40 */1 * * * $CVSUP $CVSUPDIR/current-supfile > /dev/null > ---------------------- > > When I install this crontab: > > # crontab my-crontab > "my-crontab":0: bad minute > crontab: errors in crontab file, can't install > > "0" means line number. It means variable setting doesn't work... > > I used this crontab over years on 4.[4567]-RELEASE happily. What > happen to cron? I suspected updating procedure(/usr/src/UPDATING) > because my -current desktop(starting from -current snapshot a year > ago) doesn't have such problem.
Since revision 1.11 of src/usr.sbin/cron/lib/env.c, you need to put the value of the environment variable inside quotes if it contains any spaces. I suspect that this change of behaviour was unintentional given that the implementation differs from the manual page. I'll investigate and fix it if it's a bug. In the mean time, use something like this instead: CVSUP="/usr/local/bin/cvsup -g -L2 -h localhost" Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
