Bug#763751: systemd: mounts automounts on boot even with option "noauto"

[Jakob Schürz]

Am 2014-10-02 14:46, schrieb Michael Biebl:
> Am 02.10.2014 um 13:08 schrieb Jakobus Schürz:

>> The manpage of systemd.mount from my system says,
>> "comment=systemd.automount" is to use. 
>>
>> In
>> http://www.freedesktop.org/software/systemd/man/systemd.mount.html
>> I found:
>>
>> "noauto, auto
>> With noauto, this mount will not be added as a dependency for
>> local-fs.target. This means that it will not be mounted automatically
>> during boot, unless it is pulled in by some other unit. Option auto has
>> the opposite meaning and is the default."
>>
>> In the man systemd.mount on my system, this missing.
>>
>> So do I have to wait, until a newer systemd is backportet (or i upgrade
>> to jessie)??
> 
> auto, noauto have an effect on .mount units afaics and not on .automount
> units, i.e. the automount unit is started irregardless of what you use.
> 
> That your mount point is mounted, is not due to systemd mounting it, but
> something accessing the directory triggering the automount.
> 

I get this message (debug systemd on boot, writing to dmesg)

[   29.064987] systemd[1]: Got direct mount request on
/var/cache/backup, triggered by 1771 (mountpoint)

But i have no idea, what process 1771 is...

Another guy in debianforum.de has the same effect. And i don't know,
which process wants access to the automount-ponts on bootup? How can i
find this out?

And the mounting of this automount-points on boottime only happens, when
systemd is involved... Try it on your own.

regards