I was poking around to see if I could find a reasonable way to set the UNAME_r environment variable for an instance of cron(8) running in a jail (so that cron-initiated tasks could automagically inherit the value, without requiring that every crontab instance within the jail specify it), and I started to think about ways to coerce the cron_program variable from /etc/defaults/rc.conf:
d134(8.3-S)[2] grep cron defaults/rc.conf cron_enable="YES" # Run the periodic job daemon. cron_program="/usr/sbin/cron" # Which cron executable to run (if enabled). cron_dst="YES" # Handle DST transitions intelligently (YES/NO) cron_flags="" # Which options to pass to the cron daemon. entropy_dir="/var/db/entropy" # Set to NO to disable caching entropy via cron. d134(8.3-S)[3] to set the environment variable. But inspection of rc.d/cron shows: d134(8.3-S)[6] grep cron_program rc.d/cron ; echo $? 1 d134(8.3-S)[7] Note: while the machine was running stable/8, I was looking at files on the "head" slice: d134(8.3-S)[7] grep '\$FreeBSD' rc.d/cron # $FreeBSD: head/etc/rc.d/cron 230099 2012-01-14 02:18:41Z dougb $ d134(8.3-S)[8] Does the observation make sense? (If anyone has insights on how I might address the issue that catalyzed my poking around, I'd be happy to receive them.) Please Cc: me on responses, as I am not currently subscribed to rc@. Thanks! Peace, david -- David H. Wolfskill [email protected] Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
pgpW9SQqHR3BY.pgp
Description: PGP signature
