Section: User Commands (1)
Return to Main Contents
ezmlm-cron - Sets up digest request messages generation via crond
is a very restrictive interface to
It edits the effective user's ~/crontab (see crontab(5))
file. It then executes
to update crond(8) with the changes.
sets up the generation of trigger messages to the list
and the digest code
A optional digest format specifier
can be added to
is the home directory of the effective user. The first line of this file is the
host name, 'host', to which bounces should be sent. Any bounces for lists
set up by 'user' will go to 'user@host'. Subsequent lines are entries
for users made up of:
The ':'-separated parameters are:
the user name to which this line corresponds.
the list address must start with exactly these characters (case sensitive).
If this field is empty, any list local address is allowed.
the list host name must exactly match this parameter (case insensitive).
If this field is empty, any list host address is allowed. (Host names for
the list and the digest list must still match.)
the user is permitted a maximum of
- list1 [,list2...]
a set of complete list names separated by commas. The user may edit
entries for these lists, even if they do not match the criteria set
above. If these lists exist, they are counted in determining
No while space is allowed before or between list names. If no list names
are specified, the final ':' can be omitted.
The first line matching the executing user will be used.
is installed SUID
the configuration and crontab files from that user's home directory
will be used for all
actions. This way, users on a system can be given limited
and to the generation of digest trigger messages. This is especially
useful for users without shell access or access to
is usually 'ezmlm'.
# chown ezmlm /usr/local/bin/ezmlm/ezmlm-cron
# chmod 4555 /usr/local/bin/ezmlm/ezmlm-cron
refuses to run if installed SUID root.
when executed by 'root',
will still use the files in ~root.
access, you may need to list the effective user (all users allowed access
or ~ezmlm if
is installed SUID ezmlm) in
for further information.
switches are mutually exclusive.
List user entry from
Do not list user entry.
for an entry belonging to the executing user, permitted by
and matching the command line arguments supplied.
is ignored and may be omitted.
Do not delete entry.
- -i hrs
Generate trigger message with
hours interval. Accepted intervals are 0, 1 ,2, 3, 6, 12, 24, 48, and 72 hours.
Other numbers will be silently adjusted upwards to the nearest accepted
(intervals above 72 hours will result in weekly trigger messages).
List entries. If no other command line arguments are given,
lists the entries created in the name of the user. If
will list the entries for all the matching lists, even if the entries
were not set up by the current user. Arguments, if given, still have to
comply with the rules set in
lines are listed. These are taken from the ~/crontab file. Usually,
these are active entries, although if the last execution of
failed, they may not be.
Do not list entry.
- -t hh:mm
The time for the trigger message. Other trigger messages will be sent
hours before and after this time.
- -w dow
The days of the week on which trigger messages are sent. day 0 and 7 are
Sunday, 1 is Monday, etc (see crontab(5)). The string specified for
must consists of single comma-separated digits in the range '0'-'7'
only. The default is every day, except for
of 48 (default Monday, Wednesday, Friday), 72 (default Monday and Thursday),
or greater than 72 (default Monday).
can be specified. In this case, trigger messages are sent
on the day specified by
at the interval
is greater than 24 h, it is ignored and
trigger messages are generated daily or as specified by
The configuration file for
is the effective user id. This is the executing user, unless
is installed SUID
in which case it is
The file edited by
is the effective user.
The lock file used to assure that only one process at a time is editing the
is the effective user.
should use the output of 'crontab -l' to list crontab lines, rather than
parse the crontab file (and assume that the last execution of
- SEE ALSO
This document was created by
using the manual pages.
Time: 18:00:50 GMT, June 16, 2008