On Wed, Nov 24, 2010 at 09:30:03PM +0100, Michał Piotrowski wrote:
2010/11/24 Paul Wouters <paul(a)xelerance.com>:
> 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)
Uhm, you meant path type unit, described in systemd.path surely. Listen*
directives are for sockets.
>> 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
And Paul surely meant OpenS/WAN ;)
Tomasz Torcz "God, root, what's the difference?"
xmpp: zdzichubg(a)chrome.pl "God is more forgiving."