Re: [systemd-devel] BUG: Huge Problem: systemd does not mount all filesystems on Boot

Am Fri, 14 Oct 2016 19:58:13 +0300 schrieb Andrei Borzenkov : > 14.10.2016 12:11, Juergen Sauer пишет: > > Moin, > > > > Systemd 231, Archlinux current > > > > The concept is /home is to be mounted from nfs server. Works. > > For performance reasons (email thunderbird,

Re: [systemd-devel] BUG: Huge Problem: systemd does not mount all filesystems on Boot

14.10.2016 12:11, Juergen Sauer пишет: > Moin, > > Systemd 231, Archlinux current > > The concept is /home is to be mounted from nfs server. Works. > For performance reasons (email thunderbird, kde/plasma 5.8.x i.e odr > gnome are unusable if home is pure nfs) the user sub dirs .local, > .cache,

Re: [systemd-devel] systemd 210 - mount/umount/remount

I think there's been some recent discussion related to this on this mailing list. You might want to check the archives and/or look into the nofail and/or noauto options in your fstab entries. Seems like nofail at least will change the local-fs.target dependency into a Want instead of a Require,

Re: [systemd-devel] systemd 210 - mount/umount/remount

Hi again, [...] >nfsserver and postfix are depending on local-fs.target, which includes >var-backup.mount. >When stopping /var/backup with systemctl, systemd also stops nfsserver >and postfix. Therefore this is not a solution, because in fact both >don't need /var/backup. >How can I solve this?

Re: [systemd-devel] systemd 210 - mount/umount/remount

Hi, [...] >>systemd shouldn't generally start any unit on a whim ? if the corresponding >>.mount was started, then it likely was either by request, or as a >>dependency of some program, or via autofs (if you use systemd.automount). >I don't use systemd.automount. >No one requested it as far as I

Re: [systemd-devel] systemd 210 - mount/umount/remount

On Fri, 14 Oct 2016, Mantas Mikulėnas wrote: [...] And how would a remount command (for read only or read write) look like? There isn't any. Use `mount`. FWIW, I'm pretty sure "systemctl reload var-backup.mount" will remount the filesystem. You probably want to avoid "restart"

Re: [systemd-devel] systemd 210 - mount/umount/remount

Hi Michael, >On Fri, 14 Oct 2016, Mantas Mikul?nas wrote: >[...] >>>And how would a remount command (for read only or read write) look >>>like? >>> >> >> There isn't any. Use `mount`. >FWIW, I'm pretty sure "systemctl reload var-backup.mount" will remount the >filesystem. yes, but not

Re: [systemd-devel] systemd 210 - mount/umount/remount

Hi Mantas, thx for your answer. [...] >> 1. How can I prevent systemd from mounting a manually unmounted >>partition? The partiton should be mounted automatically during system >>start, though. >> >First, see if you can figure out *why* systemd mounted it. I tried to found that out,

Re: [systemd-devel] systemd 210 - mount/umount/remount

On Fri, Oct 14, 2016 at 1:06 PM, Michael Hirmke wrote: > Hi *, > > I've read the man pages and some more documentation about the mount > behaviour of systemd, but I couldn't find a definitive answer to my > questions. > I have a backup script, that copies all files to

[systemd-devel] systemd 210 - mount/umount/remount

Hi *, I've read the man pages and some more documentation about the mount behaviour of systemd, but I couldn't find a definitive answer to my questions. I have a backup script, that copies all files to backup to a hard disk partition, then duplicates the partition to one on a second disk, which

[systemd-devel] BUG: Huge Problem: systemd does not mount all filesystems on Boot

Moin, Systemd 231, Archlinux current The concept is /home is to be mounted from nfs server. Works. For performance reasons (email thunderbird, kde/plasma 5.8.x i.e odr gnome are unusable if home is pure nfs) the user sub dirs .local, .cache, .config, .thunderbird etc. are mounts from local fs