Bug#750360: systemd-sysv: breaks NFS root systems

2014-06-02 Thread Dominik George
Control: reassign -1 initramfs-tools 0.115 Control: retitle -1 initramfs-tools: nfs mount script check for /sbin/init incomplete https://www.debian.org/doc/debian-policy/ch-files.html#fr91 Ok, the explanation here changes things a bit. I do not think that /sbin will be a symlink on any system so

Processed: Re: Bug#750360: systemd-sysv: breaks NFS root systems

2014-06-02 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 initramfs-tools 0.115 Bug #750360 [systemd-sysv] systemd-sysv: breaks NFS root systems Bug reassigned from package 'systemd-sysv' to 'initramfs-tools'. No longer marked as found in versions systemd/204-10. Ignoring request to alter fixed versions of bug #

Processed: Re: Bug#750360: systemd-sysv: /sbin/init should be a relative symlink

2014-06-02 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #750360 {Done: Michael Biebl } [systemd-sysv] systemd-sysv: /sbin/init should be a relative symlink Bug reopened Ignoring request to alter fixed versions of bug #750360 to the same values previously set > retitle -1 systemd-sysv: breaks NFS root syste

Bug#750360: systemd-sysv: /sbin/init should be a relative symlink

2014-06-02 Thread Dominik George
Control: reopen -1 Control: retitle -1 systemd-sysv: breaks NFS root systems Hi Michael, > > This is nothing which can be fixed in the systemd package, thus closing > > the bug report. sorry, I think you oversimplify the issue. While fixing policy or debhelper might be none of your business, as

Re: Bug#744753: anacron: Anacron not triggered when system resumes under systemd

2014-06-02 Thread Michael Biebl
Am 03.06.2014 05:56, schrieb Michael Biebl: > Am 03.06.2014 05:43, schrieb Michael Biebl: > >> I would simplify the first solution a bit though, and simply run a >> try-restart on post, i.e. something like this >> >> #!/bin/bash >> [ "$1" = "post" ] && systemctl try-restart anacron.service > > Ac

Re: Bug#744753: anacron: Anacron not triggered when system resumes under systemd

2014-06-02 Thread Michael Biebl
Am 03.06.2014 05:43, schrieb Michael Biebl: > I would simplify the first solution a bit though, and simply run a > try-restart on post, i.e. something like this > > #!/bin/bash > [ "$1" = "post" ] && systemctl try-restart anacron.service Actually, better make that restart instead of try-restart,

Re: Bug#744753: anacron: Anacron not triggered when system resumes under systemd

2014-06-02 Thread Michael Biebl
On Mon, Apr 14, 2014 at 11:42:52AM +, Sam Morris wrote: > Package: anacron > Version: 2.3-19 > Severity: normal > Tags: patch > > Anacron currently ships a pm-utils hook script that starts the service > when the system is resumed. pm-utils hooks are not executed when the > system resumes, havi

Bug#750360: marked as done (systemd-sysv: /sbin/init should be a relative symlink)

2014-06-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Jun 2014 23:58:02 +0200 with message-id <538cf36a.4020...@debian.org> and subject line Re: Bug#750360: systemd-sysv: /sbin/init should be a relative symlink has caused the Debian Bug report #750360, regarding systemd-sysv: /sbin/init should be a relative symlink to be ma

Bug#750360: systemd-sysv: /sbin/init should be a relative symlink

2014-06-02 Thread Dominik George
Package: systemd-sysv Version: 204-10 Severity: important /sbin/init is installed as a symbolic link to the absolute path //lib/systemd/systemd. This breaks in environments where the root filesystem is not mounted at /, for example, when inspecting a chroot from outside or, which is worse, when b

service file docs?

2014-06-02 Thread Michael Meskes
Hi again, is there any documentation about how a service file should look? Yes, this is about quota again, which seems to have the rare situation that it is started in level S, but needs to be called when shutting down to stop. I found that hwclock is in a similar situation, but apparently my sys

Bug#734848: [Pkg-systemd-maintainers] Bug#734848: systemd: LSB initscript wrappers should also handle sockets on start/stop

2014-06-02 Thread Michael Stapelberg
Hi Apollon, Apollon Oikonomopoulos writes: > was loaded but not enabled. Unfortunately the semantics of TriggeredBy > seem to be poorly documented. Anyway, I will submit a more elegant > version :) Cool. Also note that patches with documentation updates/clarifications are appreciated on the sys

Bug#734848: [Pkg-systemd-maintainers] Bug#734848: systemd: LSB initscript wrappers should also handle sockets on start/stop

2014-06-02 Thread Apollon Oikonomopoulos
Hi Michael, On 15:43 Sat 31 May , Michael Stapelberg wrote: > > +# We also start/stop the associated sockets (if any), so that > > +# "/etc/init.d/foo stop" permanently stops the service. > > +if [ "$command" = start -o "$command" = stop ]; then > > +for socket in $(systemc