Re: [DSE-Dev] Bug#796693: selinux-basics: Has init script in runlevel S but no matching service file

Am 14.09.2015 um 14:53 schrieb Michael Biebl: > Hi Russell, > > thanks for contacting us! > > Am 14.09.2015 um 14:46 schrieb Felipe Sateler: >> I could not find what the fedora people are doing, but they likely >> already faced this problem, it is probably worth checking what they >> did. > > A

Re: [DSE-Dev] Bug#796693: selinux-basics: Has init script in runlevel S but no matching service file

Hi Russell, thanks for contacting us! Am 14.09.2015 um 14:46 schrieb Felipe Sateler: > I could not find what the fedora people are doing, but they likely > already faced this problem, it is probably worth checking what they > did. A quick grep in a fedora f22 vm shows this: > # grep relabel -R

Re: [DSE-Dev] Bug#796693: selinux-basics: Has init script in runlevel S but no matching service file

Hi Russell, On 14 September 2015 at 06:29, Russell Coker wrote: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796693 > > What do you suggest that we do in regard to this bug? The problem we have is > that this isn't like your typical service script (most of which

Bug#798965: systemd: Unit mnt.mount entered failed state

Package: systemd Version: 215-17+deb8u2 Severity: important The following happened to me, as far as I can recollect after the fact: - While booting I had an entry in /etc/fstab like /dev/sdc1 /mnt ... noauto - Later, I changed the entry to "/dev/sdb1 ..." and mounted it manually. - Later

Bug#798965: marked as done (systemd: Unit mnt.mount entered failed state)

Your message dated Mon, 14 Sep 2015 17:28:14 +0200 with message-id <55f6e78e.9000...@debian.org> and subject line Re: Bug#798965: systemd: Unit mnt.mount entered failed state has caused the Debian Bug report #798965, regarding systemd: Unit mnt.mount entered failed state to be marked as done.

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #798391 (http://bugs.debian.org/798391) # Bug title: systemd: RuntimeDirectory=

Bug#792882: /bin/machinectl: machinectl fails to login to container

How exactly did you start the containers? Does it work, if you copy them to /var/lib/machines/ and start them via systemctl start systemd-nspawn@.service ? At least this works for me. signature.asc Description: OpenPGP digital signature ___

Bug#798965: closed by Michael Biebl <bi...@debian.org> (Re: Bug#798965: systemd: Unit mnt.mount entered failed state)

> > - Remembering what little I know about systemd, I did > > "systemctl daemon-reload", and indeed this seemed to fix the > > problem. > > Correct, you need to run daemon-reload after changes to /etc/fstab. > Using inotify on configuration files was rejected upstream since you > don't know,

Re: [DSE-Dev] Bug#796693: selinux-basics: Has init script in runlevel S but no matching service file

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796693 What do you suggest that we do in regard to this bug? The problem we have is that this isn't like your typical service script (most of which start daemons etc). It has more in common with a fsck than any other operation on a non-SE