3 ezmlm-cron \- Sets up digest request messages generation via crond
18 is a very restrictive interface to
20 It edits the effective user's ~/crontab (see crontab(5))
21 file. It then executes
23 to update crond(8) with the changes.
26 sets up the generation of trigger messages to the list
30 A optional digest format specifier
40 is the home directory of the effective user. The first line of this file is the
41 host name, 'host', to which bounces should be sent. Any bounces for lists
42 set up by 'user' will go to 'user@host'. Subsequent lines are entries
44 .IR user:local:host:num:[list1[,list2...]] .
45 The ':'-separated parameters are:
48 the user name to which this line corresponds.
51 the list address must start with exactly these characters (case sensitive).
52 If this field is empty, any list local address is allowed.
55 the list host name must exactly match this parameter (case insensitive).
56 If this field is empty, any list host address is allowed. (Host names for
57 the list and the digest list must still match.)
60 the user is permitted a maximum of
65 a set of complete list names separated by commas. The user may edit
66 entries for these lists, even if they do not match the criteria set
67 above. If these lists exist, they are counted in determining
69 No while space is allowed before or between list names. If no list names
70 are specified, the final ':' can be omitted.
72 The first line matching the executing user will be used.
78 the configuration and crontab files from that user's home directory
81 actions. This way, users on a system can be given limited
87 and to the generation of digest trigger messages. This is especially
88 useful for users without shell access or access to
97 # chown ezmlm /usr/local/bin/ezmlm/ezmlm-cron
98 # chmod 4555 /usr/local/bin/ezmlm/ezmlm-cron
102 refuses to run if installed SUID root.
104 when executed by 'root',
105 will still use the files in ~root.
109 access, you may need to list the effective user (all users allowed access
112 is installed SUID ezmlm) in
113 .BR /etc/cron.allow .
116 for further information.
123 switches are mutually exclusive.
132 Do not list user entry.
139 for an entry belonging to the executing user, permitted by
140 .I ~euser\fB/ezcronrc
141 and matching the command line arguments supplied.
143 is ignored and may be omitted.
150 Generate trigger message with
152 hours interval. Accepted intervals are 0, 1 ,2, 3, 6, 12, 24, 48, and 72 hours.
153 Other numbers will be silently adjusted upwards to the nearest accepted
155 (intervals above 72 hours will result in weekly trigger messages).
158 List entries. If no other command line arguments are given,
160 lists the entries created in the name of the user. If
164 will list the entries for all the matching lists, even if the entries
165 were not set up by the current user. Arguments, if given, still have to
166 comply with the rules set in
171 lines are listed. These are taken from the ~/crontab file. Usually,
172 these are active entries, although if the last execution of
174 failed, they may not be.
181 The time for the trigger message. Other trigger messages will be sent
183 hours before and after this time.
186 The days of the week on which trigger messages are sent. day 0 and 7 are
187 Sunday, 1 is Monday, etc (see crontab(5)). The string specified for
189 must consists of single comma-separated digits in the range '0'-'7'
190 only. The default is every day, except for
192 of 48 (default Monday, Wednesday, Friday), 72 (default Monday and Thursday),
193 or greater than 72 (default Monday).
198 can be specified. In this case, trigger messages are sent
199 on the day specified by
206 is greater than 24 h, it is ignored and
207 trigger messages are generated daily or as specified by
212 The configuration file for
215 is the effective user id. This is the executing user, unless
226 is the effective user.
229 The lock file used to assure that only one process at a time is editing the
233 is the effective user.
236 should use the output of 'crontab -l' to list crontab lines, rather than
237 parse the crontab file (and assume that the last execution of