Bug#851143: systemd: doesn't use all the mount options from /etc/fstab when mounting on boot

On Tue, 23 May 2017 02:49:21 AM Michael Biebl wrote: > > Sorry for the delay in responding. I've attached those files. > > The configuration you attached doesn't seem to match up. > E.g. the original fstab didn't have x-systemd.automount. I've set the system to not use automount, rebooted it, an

Bug#717388: [Pkg-systemd-maintainers] Bug#717388: Please enable persistent journal

Having read through the discussion in this bug report, I understand why persistent journald logging isn't enabled in Jessie or Stretch (both of which I've started using recently), but it would perhaps be helpful to users coming from other distros (in my case, Fedora) if there was more readily avail

Bug#851143: systemd: doesn't use all the mount options from /etc/fstab when mounting on boot

Am 22.05.2017 um 18:49 schrieb Michael Biebl: > The ExecMount shows that mount has apparently been called as > /bin/mount 10.10.10.1:/mailstore /mail -t nfs -o > context=system_u:object_r:mail_spool_t:s0,x-systemd.automount What happens, if you run umount /mail mount 10.10.10.1:/mailstore /mail -

Bug#851143: systemd: doesn't use all the mount options from /etc/fstab when mounting on boot

Am 22.05.2017 um 16:35 schrieb Russell Coker: > reopen 851143 > thanks > >>> Could you attach the output of >>> systemctl status mail.mount >>> systemctl show mail.mount >> >> Since I don't have a selinux enabled system so I could try and reproduce >> this and no further information was provided,

Bug#851143: systemd: doesn't use all the mount options from /etc/fstab when mounting on boot

reopen 851143 thanks > > Could you attach the output of > > systemctl status mail.mount > > systemctl show mail.mount > > Since I don't have a selinux enabled system so I could try and reproduce > this and no further information was provided, I'm closing this bug report. > > Please reopen if you

Processed: Re: Bug#851143: systemd: doesn't use all the mount options from /etc/fstab when mounting on boot

Processing commands for cont...@bugs.debian.org: > reopen 851143 Bug #851143 {Done: Michael Biebl } [systemd] systemd: doesn't use all the mount options from /etc/fstab when mounting on boot Bug reopened Ignoring request to alter fixed versions of bug #851143 to the same values previously set >

Processed: tagging 861889

Processing commands for cont...@bugs.debian.org: > tags 861889 + wontfix Bug #861889 {Done: Michael Biebl } [systemd] systemd: network-online.target remains active after resume Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 861889: http://b

Bug#816876: marked as done (systemd: bootsched fails after systemd is installed resumes working after systemd is removed)

Your message dated Mon, 22 May 2017 16:01:13 +0200 with message-id <52211841-a259-e819-6062-dd7316e70...@debian.org> and subject line Re: systemd: bootsched fails after systemd is installed resumes working after systemd is removed has caused the Debian Bug report #816876, regarding systemd: bootsc

Bug#841712: marked as done (systemd: Display black on resume from hibernate)

Your message dated Mon, 22 May 2017 15:57:15 +0200 with message-id <6b37dca1-655f-96e5-ebc8-076873d9a...@debian.org> and subject line Re: Bug#841712: systemd: Display black on resume from suspend has caused the Debian Bug report #841712, regarding systemd: Display black on resume from hibernate to

Bug#851143: marked as done (systemd: doesn't use all the mount options from /etc/fstab when mounting on boot)

Your message dated Mon, 22 May 2017 15:54:21 +0200 with message-id <4a0bb442-34af-ac3e-d230-0fe592a6b...@debian.org> and subject line Re: Bug#851143: systemd: doesn't use all the mount options from /etc/fstab when mounting on boot has caused the Debian Bug report #851143, regarding systemd: doesn'

Processed: tagging 861171

Processing commands for cont...@bugs.debian.org: > tags 861171 + pending Bug #861171 [systemd] #warning "Consider adding the right clone() syscall definitions here!" Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 861171: http://bugs.debian.

Bug#861889: marked as done (systemd: network-online.target remains active after resume)

Your message dated Mon, 22 May 2017 15:44:27 +0200 with message-id <5063199d-3972-76f7-1324-793dc47bc...@debian.org> and subject line Re: Bug#861889: apt: apt.systemd.daily runs before network comes up has caused the Debian Bug report #861889, regarding systemd: network-online.target remains activ

Processed: tagging 861157

Processing commands for cont...@bugs.debian.org: > tags 861157 + pending Bug #861157 [systemd] Doesn't run all commands in Exec* if daemon is reloaded Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 861157: http://bugs.debian.org/cgi-bin/bugr

Processed: tagging 862292

Processing commands for cont...@bugs.debian.org: > tags 862292 + pending Bug #862292 [systemd] systemd: missing dependency on procps - user/systemd-exit.service calls /bin/kill Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 862292: http://b

Processed: tagging 863111

Processing commands for cont...@bugs.debian.org: > tags 863111 + pending Bug #863111 [systemd] systemd: Unable to open file: /etc/ima/ima-policy (-2) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 863111: http://bugs.debian.org/cgi-bin/bugre

Processed: tagging 863111

Processing commands for cont...@bugs.debian.org: > tags 863111 + fixed-upstream Bug #863111 [systemd] systemd: Unable to open file: /etc/ima/ima-policy (-2) Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 863111: http://bugs.debian.org