Bug#766757: Generated services should start After=systemd-user-sessions.service

2014-10-26 Thread Alexandre Detiste
control: tags -1 + fixed-upstream Ok, I've added After=systemd-user-sessions.service & RequiresMountsFor=/home/folder for user crontabs + /var/spool/cron/crontabs/root . https://github.com/systemd-cron/systemd-cron/commit/98ae11e0341f5c955c9de08778de9de3bafd459b -- To UNSUBSCRIBE, email to

Bug#766757: Generated services should start After=systemd-user-sessions.service

2014-10-25 Thread Yuri D'Elia
On 10/25/2014 05:01 PM, Alexandre Detiste wrote: > Hi, > >> The generated service template should include: >> >> After=systemd-user-sessions.service > > Should this be for everyone, or only user != 'root' ? I would say also for root. >> to actually ensure the user directory is available/ready

Bug#766757: Generated services should start After=systemd-user-sessions.service

2014-10-25 Thread Alexandre Detiste
Hi, > The generated service template should include: > > After=systemd-user-sessions.service Should this be for everyone, or only user != 'root' ? > to actually ensure the user directory is available/ready before starting the > job. Isn't "DefaultDependencies=true" enough ? -- To UNSUBSC

Bug#766757: Generated services should start After=systemd-user-sessions.service

2014-10-25 Thread Yuri D'Elia
Package: systemd-cron Version: 1.3.1+ds1-1 Severity: normal The generated service template should include: After=systemd-user-sessions.service to actually ensure the user directory is available/ready before starting the job. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.o