Hi,
Thanks all for your comments. I will try to use option FreeBind. However
could anyone explain for me that I did not use FreeBind option in
systems-210 but all my services start well? I am still inclined to the
different of systemd-228 and systemd-210 causes the current issue.
Thanks again,
Br
On Fri, Nov 24, 2017 at 09:03:23PM +0100, Olaf Hering wrote:
> Is there a way to have stacked automounts?
Not really.
> In this example only /d is mounted when /d/l/1/ is accessed:
>
> LABEL=d/d xfs
> noatime,x-systemd.automount,x-systemd.idle-timeout=22 1 2
> /d/i/1.iso /d/l/1 iso9
On Sun, Nov 26, 2017 at 11:47 AM, Bao Nguyen wrote:
> Hi Uoti,
>
> Thanks a lot for your answer, I have checked the cycle. It is created by
> sockets.target
> -> asi-My-5101.socket -> My-sshd.target -> My-syncd.service ->
> My-nfs-client.service
> -> My-handling.service -> basic.target -> socke
Am 26.11.2017 um 10:47 schrieb Bao Nguyen:
Regard to your question, "asi-My-5101.socket" depends on
"My-sshd.target", I think that in my case it is expected as my socket
listens on a specific address IP:port so it should start after a network
service to configure and assign IP address before
Hi Uoti,
Thanks a lot for your answer, I have checked the cycle. It is created
by sockets.target
-> asi-My-5101.socket -> My-sshd.target -> My-syncd.service ->
My-nfs-client.service
-> My-handling.service -> basic.target -> sockets.target. I do not see the
same cycle in systemd-210 so I said that
