1

Getting wol to work after a shutdown, wol after suspend IS working

view story
linux-howto

https://bbs.archlinux.org – My solution to make WoL work after shutdown and suspend/hibernate was to create a script in /usr/lib/systemd/system-sleep/wol.sh:#!/bin/sh # Setting WOL to Active /usr/sbin/ethtool -s eth0 wol gDon't forget to make it executable!Since man 8 systemd-sleep considers this kind of solutions as hack, I also tried the following alternative code in /etc/systemd/system/wol@.service, however it didn't work:[Unit] Description=Wake-on-LAN for %i Requires=network.target After=network.target After=sleep.target Before=halt.target Before=poweroff.target Before=kexec.target Before=shutdown.target [ (HowTos)

missing's picture
Submitted by missing on 12/02/2012

Stories similar to Getting wol to work after a shutdown, wol after suspend IS working

Hey there,I need a little help with a service file I want to use for unmounting truecrypt containers and devices on shutdown, poweroff & reboot.

NIC failed? 10 weeks 4 days ago

I don't know if this has anything to do with it, but pmutils is old and crufty and not really necessary anymore.  It is probably better to use systemctl suspend and the directory /usr/lib/systemd/system-sleep as you can drop scripts to be run during suspend and hibernate there.  Or else you could go full native systemd and create service files that are WantedBy=sleep.target and Befo

default.target is just a link to either /usr/lib/systemd/system/multi-user.target or /usr/lib/systemd/system/graphical.target or another target.It should do no harm and is probably not the cause of the problem.graphical.target wants display-manager.service which is an alias for kdm.service if it is enabled.

berbae https://bbs.archlinux.org/profile.php?id=9555

2013-03-07T16:10:18Z

I wrote a script that suspend all my virtualbox machines, and put a line in /etc/rc.local.shutdown, but it doesn't seem to work,

su - XX -c /XX

When I'm booted next time, virtualbox tells me the machine was Aborted, so the script wasn't executed. (Launching that script manually works for me)

P.S I already enabled shutdown.target

Unable to start Apache 22 weeks 2 days ago

@dxxvi I have also been having issues with apache since I moved to systemd at the weekend.

systemd/User - autologin 2 weeks 4 days ago

I have nearly fresh Arch on computer and I wanted to have autologin. To make this work, I used this solution. I don't know what I did wrong, but after this my system couldn't start (I don't remember what Bash said, because it was some weeks ago). I think I could badly link mystuff.target to default.target.

HelloAlthough I'm not a fan of dzillions of config files I decided to try systemd.

This works for me, YMMV:/etc/systemd/system/screen.service[Unit] Description=Detached screen session After=network.target

[Service] Type=oneshot RemainAfterExit=yes User=tomk ExecStart=/usr/bin/screen -dm

[Install] Wants=network.target WantedBy=multi-user.target ~/.screenrc... screen -t rtorrent 5 /usr/bin/rtorrent ...

tomk https://bbs.archlinux.org/profile.php?id=1822

2013-03-

i3lock and systemd suspend 33 weeks 9 hours ago

please use code tags.you may want to use this service file instead:[Unit] Description=i3lock Before=sleep.target

[Service] User=<user> Type=forking Environment=DISPLAY=:0 ExecStart=/usr/bin/i3lock -c 000000

[Install] WantedBy=sleep.targetsystemctl enable i3lock.service

65kid https://bbs.archlinux.org/profile.php?id=45818

2012-10-04T13:58:35Z