Re: [systemd-devel] Issue on Ordering of systemd services during boot

2019-12-10 Thread Jérémy ROSEN
You probably have another problem lurking behind... A.service is of Type=Simple. That means that systemd doesn't know when A.service is ready and will lauch B.socket as soon as A has been launched. B being a socket, it has no delay so will be ready instantly. You probably want to change Type to s

Re: [systemd-devel] Issue on Ordering of systemd services during boot

2019-12-10 Thread Colin Guthrie
I presume B.socket is some kind of network socket rather than filesystem path? Either that or A.service provides the filesystem for the socket path? That being the case, you've got an ordering cycle here as B.socket has WantedBy=sockets.target which is order before multi-user.target which is neede

[systemd-devel] Issue on Ordering of systemd services during boot

2019-12-09 Thread TARANA, YASHASHVI
Hi, I have a systemd service A.service and socket B.socket and its corresponding service B.service with the following content: A.service [Unit] Description=A.service [Service]