Re: [systemd-devel] automount fails with generic "resources" error

2018-01-27 Thread Olaf Hering
On Tue, Jan 23, Lennart Poettering wrote: > On Mo, 15.01.18 15:13, Olaf Hering (o...@aepfle.de) wrote: > > > 'journalctl -b' does not indicate any related failure. > > > > Does anyone happen to know what limits a mount point or an automount > > point might have? These systems have plenty of

Re: [systemd-devel] automount fails with generic "resources" error

2018-01-23 Thread Lennart Poettering
On Mo, 15.01.18 15:13, Olaf Hering (o...@aepfle.de) wrote: > 'journalctl -b' does not indicate any related failure. > > Does anyone happen to know what limits a mount point or an automount > point might have? These systems have plenty of cpus, have plenty of > memory, likely enough to handle

[systemd-devel] automount fails with generic "resources" error

2018-01-15 Thread Olaf Hering
Since I discovered the automount feature I started to add it to fstab, as shown below, on several systems with various versions of systemd. Most of the time it works fine. But sometimes units fail to start. Google does not give much hints about that, nor a pointer what limits must be raised to