On Wed, 24.11.10 21:30, MichaÅ Piotrowski (mkkp4x4@xxxxxxxxx) wrote: > > 2010/11/24 Paul Wouters <paul@xxxxxxxxxxxxx>: > > On Wed, 24 Nov 2010, Lennart Poettering wrote: > > > >> BTW, regarding at and cron: what I was thinking of but never check > >> ehwther it is feasible is to make cron/at autostart a soon as some job > >> is scheduled. I.e. use .path trigger to check whether /etc/crontab and > >> user jobs exist, and start cron only then. Similarly for at. That way we > >> could support cron and at just fine, and wouldn't even have to run it by > >> default. I haven't looked into this in detail however, to see if the > >> file triggers systemd offers in .path units are already sufficient to > >> make this work. > > > > What if no jobs are there and a non-root user adds a crontab later on? Who > > will start cron (as root) ? > > I guess ListenStream=/var/spool/cron/* (if it will work - I'm not sure > how systemd interprets wildcards and multiple ListenStream) Almost. This is a .path unit, the syntax is: DirectoryNotEmpty=/var/spool/cron Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
