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