Well, actually the timers are a nice benefit only. We want to control user- initiated background-services for a web application server with this and cron hasn't been our best friend for this in the past.
David Strauss <da...@davidstrauss.net> schrieb: > I don't recommend spawning user instances of systemd just for their > timer units to run. Each instance comes with a few MB of overhead, and > you'll have no fun trying to spawn sessions in a way isolated from > (but somehow integrated with) the PAM session initialization process. > > On Mon, May 6, 2013 at 3:14 PM, Kai Krakow <hurikha...@gmail.com> wrote: >> Jóhann B. Guðmundsson <johan...@gmail.com> schrieb: >> >>>> But now I want to (and need to) give some users cron-like abilities. I >>>> discovered that systemd supports user instances - perfect! >>> >>> Then install cronie... >> >> That's the obvious solution but a little bit counter-productive with >> respect to my question... >> >> Anyway, one has to take that route if everything else fails. >> >> Regards, >> Kai >> >> _______________________________________________ >> systemd-devel mailing list >> systemd-devel@lists.freedesktop.org >> http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel