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) ?

> Btw, it's written "systemd", not "SystemD". I even added a section about
> the spelling now to the systemd homepage ;-)

At Openswan, we never wrote OpenSWAN and we're still telling people every week
to not use that. It's a lost battle :P

Paul
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to