[systemd-devel] systemd automounts

[Mirco Tischler]

2011/8/2 Steve Dickson <SteveD at redhat.com>:
>
>
> On 08/01/2011 09:10 PM, Mirco Tischler wrote:
>> Hi
>> 2011/8/2 Steve Dickson <SteveD at redhat.com>:
>>>>
>>>> Yes, this looks like a good usecase.
>>>>
>>>> Hmm, does the automount point work after boot?
>>> It seems so, because if I restart nfs-idmap.service the
>>> service comes up.
>>>
>>>>
>>>> How does the output of "systemctl list-units" look like for the
>>>> automount and mount unit?
>>>>
>>> attached.
>>>
>>> steved.
>>>
>> The attached output indicates that your automount unit isn't started,
>> and I can't see anything causing it to start in your unit files
>> either. You can verify this with systemctl status
>> var-lib-nfs-rpc_pipefs.automount.
> It appears you are correct. systemctl status var-lib-nfs-rpc_pipefs.automount
> show the status not being started.
>
>> Note that After= is only an ordering information and doesn't cause the
>> unit to be started. Only if the automount is started anyway through
>> some other path, the After= line causes the service to wait until the
>> automount point is started.You may need to add a line
>> Wants=var-lib-nfs-rpc_pipefs.automount to your service file.
>>
>> Does that help you?
> Adding that wants does start var-lib-nfs-rpc_pipefs.automount but
> now I'm getting two mounts...
>
> # mount | grep rpc
> systemd-1 on /var/lib/nfs/rpc_pipefs type autofs (rw,relatime,fd=16,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
>
> or is that normal for automounts?
>
> steved.
>
Yup that's normal. the systemd-1 is the automount point.