|
|
1.1 root 1: .TH CALENDAR 1 "29 March 1982"
2: .UC 4.2 Provisional
3: .SH NAME
4: calendar \- reminder service
5: .SH SYNOPSIS
6: .B calendar
7: [ \- ]
8: .SH DESCRIPTION
9: .I Calendar
10: consults the file `calendar' in the current directory
11: and prints out lines that contain today's or
12: tomorrow's date anywhere in the line.
13: Most reasonable month-day dates such as `Dec. 7,'
14: `december 7,' `12/7,' etc., are recognized, but not
15: `7 December' or `7/12'.
16: If you give the month as ``*''
17: with a date, i.e. ``* 1'', that day in any month will do.
18: On weekends `tomorrow' extends through Monday.
19: .PP
20: When
21: an argument is present,
22: .I calendar
23: does its job for every user
24: who has a file `calendar' in his login directory
25: and sends him any positive results by
26: .IR mail (1).
27: Normally this is done daily in the wee hours under control of
28: .IR cron (8).
29: .PP
30: The file `calendar' is first run through the ``C'' preprocessor,
31: .IR /lib/cpp ,
32: to include any other calendar files
33: specified with the usual ``#include'' syntax.
34: Included calendars will usually be shared by all users,
35: maintained and documented by the local administration.
36: .SH FILES
37: calendar
38: .br
39: /usr/lib/calendar to figure out today's and tomorrow's dates
40: .br
41: /etc/passwd
42: .br
43: /tmp/cal*
44: .br
45: /lib/cpp, egrep, sed, mail as subprocesses
46: .SH "SEE ALSO"
47: at(1), cron(8), mail(1)
48: .SH BUGS
49: .I Calendar's
50: extended idea of `tomorrow' doesn't account for
51: holidays.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.