Next: How ezmlm-make works, Previous: How the global ezmlm list address works, Up: Overview of ezmlm function
If you are a user and have crond(8) access, if you do not need to get digests at specific times, or if you are a system administrator setting up lists, there is no reason for you to use ezmlm-cron(1). If you are a system administrator not allowing users crond(8) access or a user that needs digests at specific times, but without crond(8) access, read on.
ezmlm-cron(1) is a very restrictive interface to crond(8). ezmlm-cron(1) can be used to create digest trigger messages. If a list is set up with a digest code (see ezmlm-make(1) and ezmlm-get(1)) ezmlm will generate a digest from the list ‘joe-sos@host’ sent to to subscribers of ‘joe-sos-digest@dighost’ when receiving a message to ‘joe-sos-dig-code@host’ where ‘code’ is the digest code. ezmlm-cron(1) can be used to generate such messages at regular intervals. The file ezcronrc is set up by the sysadmin and controls what trigger messages specific users may set up via ezmlm-cron(1).
Usually, the ezcronrc of that use will have an entry like ‘user:user-:host:10’ allowing ‘user’ to create trigger messages for up to 10 lists with names starting with ‘user-’ and on the host ‘host’.
To list the ezcronrc line controlling your use of ezmlm-cron(1):
% ezmlm-cron -c
To list all entries that you've created:
% ezmlm-cron -l
To add an entry to trigger digests from ‘list@host’ every morning at 0230:
% ezmlm-cron -t 02:30 -i24 list@host code
A new entry for the same list overwrites an old entry.
To delete the entry above:
% ezmlm-cron -d list@host
or use ezmlm-cron to trigger messages at a different time:
% ezmlm-cron -t 16:16 -i24 list@host code