On Fri, Jul 02, 2021 at 07:46:31PM +0200, Reiner Buehl wrote:
> I think I found a solution! For whatever reason, my network interface
> enp5s11 was not in the "auto" line in /etc/network/interfaces. After adding
> it there and a reboot, the filesystem is mounted correct without any of
> the x-syst
I think I found a solution! For whatever reason, my network interface
enp5s11 was not in the "auto" line in /etc/network/interfaces. After adding
it there and a reboot, the filesystem is mounted correct without any of
the x-systemd mount options.
Am Fr., 2. Juli 2021 um 19:30 Uhr schrieb Reiner B
Hello,
this is the full unit:
# /etc/systemd/system/vdr.service
[Unit]
Description=Video Disk Recorder
Wants=systemd-udev-settle.service
After=systemd-udev-settle.service
[Service]
Type=notify
ExecStartPre=/bin/sh /usr/lib/vdr/merge-commands.sh "commands"
ExecStartPre=/bin/sh /usr/lib/vdr/merge
Hi.
On Fri, Jul 02, 2021 at 06:12:58PM +0200, Reiner Buehl wrote:
> I have a directory that is mounted via NFS from a remote server.
Actually, you have an autofs mountpoint, because you set
x-systemd.automount option in fstab.
Only if something starts using that mountpoint an NFS filesyst
On Fri, Jul 02, 2021 at 06:12:58PM +0200, Reiner Buehl wrote:
> I have a directory that is mounted via NFS from a remote server. The mount
> is done via an /etc/fstab entry like this:
>
> 192.168.1.2:/video /video nfs
> defaults,x-systemd.automount,x-systemd.requires=network-online.target,x-
Hi all,
I have a directory that is mounted via NFS from a remote server. The mount
is done via an /etc/fstab entry like this:
192.168.1.2:/video /video nfs
defaults,x-systemd.automount,x-systemd.requires=network-online.target,x-systemd.device-timeout=10,rsize=8192,wsize=8192,soft,nolock,noa
6 matches
Mail list logo
