1calendar(1)                      User Commands                     calendar(1)
2
3
4

NAME

6       calendar - reminder service
7

SYNOPSIS

9       calendar [-]
10
11

DESCRIPTION

13       The  calendar  utility consults the file calendar in the current direc‐
14       tory and writes lines that contain today's or tomorrow's date  anywhere
15       in the line to standard output. Most reasonable month-day dates such as
16       Aug. 24, august 24, 8/24, and so forth,  are  recognized,  but  not  24
17       August or 24/8. On Fridays and weekends "tomorrow" extends through Mon‐
18       day. calendar can be invoked regularly by using the crontab(1) or at(1)
19       commands.
20
21
22       When  the  optional  argument  -  is present, calendar does its job for
23       every user who has a file calendar in his or her  login  directory  and
24       sends them any positive results by mail(1). Normally this is done daily
25       by facilities in the UNIX operating system (seecron(1M)).
26
27
28       If the environment variable DATEMSK is set, calendar will use its value
29       as the full path name of a template file containing format strings. The
30       strings consist of conversion specifications and  text  characters  and
31       are used to provide a richer set of allowable date formats in different
32       languages by appropriate settings of the environment variable  LANG  or
33       LC_TIME; see environ(5). Seestrftime(3C) for the list of allowable con‐
34       version specifications.
35

EXAMPLES

37       Example 1 Possible contents of a template
38
39
40       The following example shows the possible contents of a template:
41
42
43         %B %eth of the year %Y
44
45
46
47
48       %B represents the full month name, %e the day of month and %Y the  year
49       (4 digits).
50
51
52
53       If  DATEMSK  is set to this template, the following calendar file would
54       be valid:
55
56
57         March 7th of the year 1989 <Reminder>
58
59
60

ENVIRONMENT VARIABLES

62       See environ(5) for descriptions of the following environment  variables
63       that  affect the execution of calendar: LC_CTYPE, LC_TIME, LC_MESSAGES,
64       NLSPATH, and TZ.
65

EXIT STATUS

67       0      Successful completion.
68
69
70       >0     An error occurred.
71
72

FILES

74       /etc/passwd          system password file
75
76
77       /tmp/cal*            temporary files used by calendar
78
79
80       /usr/lib/calprog     program used to  determine  dates  for  today  and
81                            tomorrow
82
83

ATTRIBUTES

85       See attributes(5) for descriptions of the following attributes:
86
87
88
89
90       ┌─────────────────────────────┬─────────────────────────────┐
91       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
92       ├─────────────────────────────┼─────────────────────────────┤
93       │Availability                 │SUNWesu                      │
94       └─────────────────────────────┴─────────────────────────────┘
95

SEE ALSO

97       at(1),   crontab(1),   mail(1),   cron(1M),  ypbind(1M),  strftime(3C),
98       attributes(5), environ(5)
99

NOTES

101       Appropriate lines beginning with white space will not be printed.
102
103
104       Your calendar must be public information for you to get  reminder  ser‐
105       vice.
106
107
108       calendar's extended idea of ``tomorrow'' does not account for holidays.
109
110
111       The  -  argument  works  only  on  calendar files that are local to the
112       machine; calendar is intended not to work on calendar  files  that  are
113       mounted  remotely  with  NFS.  Thus, `calendar -' should be run only on
114       diskful machines where home directories exist;  running it on  a  disk‐
115       less client has no effect.
116
117
118       calendar  is no longer in the default root crontab. Because of the net‐
119       work burden `calendar -' can induce, it is inadvisable in  an  environ‐
120       ment  running  ypbind(1M) with a large passwd.byname map.  If, however,
121       the usefulness of calendar outweighs the network impact, the super-user
122       may  run  `crontab  -e' to edit the root crontab. Otherwise, individual
123       users may wish to use `crontab -e' to edit their own crontabs  to  have
124       cron  invoke  calendar  without  the  - argument, piping output to mail
125       addressed to themselves.
126
127
128
129SunOS 5.11                        1 Feb 1995                       calendar(1)
Impressum