On 5/21/2021 5:59 AM, Bagas Sanjaya wrote: > On 21/05/21 05.13, Lénaïc Huard wrote: >> The existing mechanism for scheduling background maintenance is done >> through cron. On Linux systems managed by systemd, systemd provides an >> alternative to schedule recurring tasks: systemd timers. >> >> The main motivations to implement systemd timers in addition to cron >> are: >> * cron is optional and Linux systems running systemd might not have it >> installed. >> * The execution of `crontab -l` can tell us if cron is installed but not >> if the daemon is actually running. >> * With systemd, each service is run in its own cgroup and its logs are >> tagged by the service inside journald. With cron, all scheduled tasks >> are running in the cron daemon cgroup and all the logs of the >> user-scheduled tasks are pretended to belong to the system cron >> service. >> Concretely, a user that doesn’t have access to the system logs won’t >> have access to the log of its own tasks scheduled by cron whereas he >> will have access to the log of its own tasks scheduled by systemd >> timer. > > For gender neutrality, we can use he/she instead. Singular "they" is better. Fully accurate and less awkward. Thanks, -Stolee
