Path: utzoo!attcan!uunet!cs.utexas.edu!rice!sun-spots-request
From: twinsun!dew!eggert@uunet.uu.net (Paul Eggert)
Newsgroups: comp.sys.sun
Subject: Re: Calendar
Keywords: Software
Message-ID: <9613@brazos.Rice.edu>
Date: 3 Jul 90 22:58:46 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n249
X-Sun-Spots-Digest: Volume 9, Issue 249, message 10

R. Hanscom asks:

	What determines if a machine sends out calendar mail?

It depends on which version of SunOS you're running.  Under SunOS 4.1, the
default is to not send out calendar mail.  To turn it on for just
yourself, run `crontab -e' and add a crontab entry like

	1 3 * * * calendar

It's best to do this while logged into the host that owns your calendar
file.

Older versions of SunOS attempt to send calendar mail for everybody using
heuristics that vary with the OS release.  Some releases look in the YP
passwd map; others look in just /etc/passwd.  Some check that the user's
calendar file is not NFS-mounted; others don't.  This is hard to do
efficiently and safely because of home directories mounted over the net,
so Sun eventually gave up.  If your users can't run `crontab -e' because
they're stuck on older SunOS releases, you can tailor the root crontab
entries that invoke /usr/bin/calendar to suit your local conventions.