On Sun, 2015-12-20 at 18:21 -0500, Robert Ames wrote: > In 10.2-RELEASE running "calendar -a" as root fails when user > calendar files have a #include line. This worked in 10.0-RELEASE > (and before). From my limited testing I think it's looking for the > included files relative to root's home directory and not the user's > home directory. The svn repository shows some changes in this area > in recent releases. Not sure if this new behavior is intentional. > > $ uname -a > FreeBSD freebsd.example.com 10.2-RELEASE FreeBSD 10.2-RELEASE #0: Sun > Dec 20 10:00:14 CST 2015 [email protected]:/usr/obj/usr/sr > c/sys/GENERIC i386 > $ id > uid=1000(robert) gid=20(staff) groups=20(staff),0(wheel),5(operator) > $ date > Sun Dec 20 16:47:44 CST 2015 > $ cat ~/.calendar/calendar > #include <moredates> > $ cat ~/.calendar/moredates > 12/20 Today is December 20 > $ calendar > Dec 20 Today is December 20 > > root@freebsd# id > uid=0(root) gid=0(wheel) groups=0(wheel),5(operator) > root@freebsd# calendar -a > calendar: can't open calendar file "moredates"
I can confirm the above behavior on my 10.2R system. And since it is documented as a working option `calendar -a` should probably be fixed. But for the record: $ cat /etc/periodic/daily/300.calendar ... # `calendar -a' needs to die. Why? Because it's a bad idea, particular # with networked home directories, but also in general. If you want the # output of `calendar' mailed to you, set up a cron job to do it, # or run it from your ~/.profile or ~/.login. ...
smime.p7s
Description: S/MIME cryptographic signature
