This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VAS - /etc/init.d/vasd - vasd.service - xdm - systemd - wait initial network connection

Hi,

i've no idea if this is considered a problem or is an issue in other OS versions or configuration types.
Just some tips if someone has had the same problem.

On our enterprise Suse SLED12 clients i've noticed that vasd daemon is getting started before initial network connection is finished.
That's why vasd starts in offline mode and is using cached credentials.
To change this behavior and start vasd in online mode, i changed "/etc/init.d/vasd" lines from:

# Required-Start: $local_fs $remote_fs $syslog
# Required-Stop: $local_fs $remote_fs $syslog

to:

# Required-Start: $local_fs $remote_fs $syslog $network
# Required-Stop: $local_fs $remote_fs $syslog $network

This way, systemd will translate LSB service file $network to "network-online.target". And we have enabled "NetworkManager-wait-online.service" because NetworkManger is our default. (Otherwise you should enable  systemd-networkd-wait-online.service)

----------

I also added network-online.target to our xdm.service, so that gnome login prompt is getting started after initial network connection is finished:

/etc/systemd/system/xdm.service

Added "network-online.target" to "Wants=" and "After="