You are not logged in.
I have activated successfully wake on lan with systemd, following these guidelines :
https://wiki.archlinux.org/index.php/Wol#With_systemd
My wol@.service is:
[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/bin/ethtool -s %i wol g
Type=oneshot
[Install]
WantedBy=multi-user.target
It worked nicely until I recently had to reinstall my server (following a disk replacement). Since then systemd fails to activate wake on lan.
Output from systemctl status wol@enp0s4 :
● wol@enp0s4.service - Wake-on-LAN for enp0s4
Loaded: loaded (/etc/systemd/system/wol@.service; enabled)
Active: inactive (dead) since ven. 2014-07-25 11:21:28 CEST; 23min ago
Process: 181 ExecStart=/usr/bin/ethtool -s %i wol g (code=exited, status=0/SUCCESS)
Main PID: 181 (code=exited, status=0/SUCCESS)
Output from ethtool enp0s4|grep "Wake" :
Supports Wake-on: pg
Wake-on: d
If I explicitly start the service with systemctl start wol@enp0s4, then ethtool enp0s4|grep "Wake" shows:
Supports Wake-on: pg
Wake-on: g
My guess is that the service does not start at the correct timing at boot.
I have also tried wol-systemd package from the AUR without success.
Last edited by elb (2014-07-25 15:02:21)
Offline
After a fiew tries and reading docs, I found that replacing network.target with multi-user.target in wol@.service seems to work for me.
Offline