Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

2015-06-04 Thread nusenu
>> systemd version is on both (fresh and upgraded) systems 215-17, what >> else should I check? > > Eg. diff the list if installed packages you get via dpkg > --get-selections and look for suspicouos diffs. The upgraded system has sysvinit installed, the fresh one doesn't. Both have systemd-sysv.

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

2015-06-04 Thread nusenu
> Anything else which is cgroup related? if 'dpkg -l |grep cgroup' should reveal that, no (no results) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-s

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

2015-06-04 Thread nusenu
> Do you maybe have anything installed on your upgraded system which might > interfere with systemd, like cgmanager, lxc, cgroup-bin etc. upgraded-system# dpkg -l cgmanager lxc cgroup-bin dpkg-query: no packages found matching cgmanager dpkg-query: no packages found matching lxc dpkg-query: no p

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

2015-06-04 Thread nusenu
> Can you find out what is different between the upgraded and fresh Debian > installation? systemd version is on both (fresh and upgraded) systems 215-17, what else should I check? > Can you post the complete service file you are using, please? working service file (to make it fail on upgraded s

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

2015-06-04 Thread nusenu
b.com/nusenu/ansible-relayor/commit/4f6283e6d993e6f81a632007c823797253feee38 Note in upstream bugtracker: https://bugs.freedesktop.org/show_bug.cgi?id=89875#c2 [2] http://lists.freedesktop.org/archives/systemd-devel/2015-April/031377.html http://lists.freedesktop.org/archives/systemd-devel/2015-May/0

Bug#751638: "systemctl is-enabled" fails for SysV init scripts

2015-04-13 Thread Nusenu
Control: affects -1 ansible > I am also annoyed by this bug because this makes Puppet thinks > that the service is not enabled as it should. same with ansible ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org htt

Bug#782496: Acknowledgement (is-enabled fails for legacy sysv services)

2015-04-13 Thread Nusenu
duplicate Sorry I just saw: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751638 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainer

Bug#782496: is-enabled fails for legacy sysv services

2015-04-13 Thread Nusenu
ing /sbin/chkconfig tor --level=5 enabled echo $? 0 references: http://lists.freedesktop.org/archives/systemd-devel/2015-April/030652.html http://lists.freedesktop.org/archives/systemd-devel/2015-April/030671.html https://github.com/nusenu/ansible-relayor/issues/20

Bug#782479: systemd fails to merge CapabilityBoundingSet config lines

2015-04-12 Thread Nusenu
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=89997 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#782479: systemd fails to merge CapabilityBoundingSet config lines

2015-04-12 Thread Nusenu
cap1 CapabilityBoundingSet = cap2 but that is not the case. Merging multiple lines manually fixed the issue for me: https://github.com/nusenu/ansible-relayor/commit/48df0a4738654ff6b0897493cf2811961550a7d6 https://github.com/nusenu/ansible-relayor/issues/19 __