Package Details: wol-systemd 20210121-2

Git Clone URL: https://aur.archlinux.org/wol-systemd.git (read-only, click to copy)
Package Base: wol-systemd
Description: A systemd unit file for enabling Wake-On-LAN automatically
Upstream URL: https://wiki.archlinux.org/index.php/Wake-on-LAN
Licenses: FDL1.3
Submitter: phiresky
Maintainer: blackhole
Last Packager: blackhole
Votes: 16
Popularity: 0.003741
First Submitted: 2015-09-03 15:31 (UTC)
Last Updated: 2021-10-08 09:24 (UTC)

Dependencies (1)

Required by (0)

Sources (2)

Latest Comments

blackhole commented on 2021-10-08 09:26 (UTC)

Ok, done!

alerque commented on 2021-10-08 09:20 (UTC)

If the code originated as a contribution on the Arch Wiki, it is probably actually licensed under the FDL, use license=(FDL1.3) (and no license file required).

blackhole commented on 2021-10-08 09:09 (UTC)

This package was not originally mine. I don'y know why the license is MIT, this is only a systemd service.

Maybe I could change to GPL, for which it is not necessary a specific file.

From the wiki:

"If a package is licensed under one of these licenses, the value should be set to the directory name, e.g. license=('GPL')"

alerque commented on 2021-10-08 09:00 (UTC) (edited on 2021-10-08 09:01 (UTC) by alerque)

There are six exception license types that are considered "standard" for the license array but you still need to package the file, see Wiki docs on this issue. You can also get tipped off to mistakes like this by running namcap on a generated package. Note not all of it's lint warnings are always valid (for example it suggests ethtool might not be a dependency, which would be wrong) but it does get this license issue right:

$ namcap wol-systemd-20210121-1-any.pkg.tar.zst
wol-systemd E: Missing custom license directory (usr/share/licenses/wol-systemd)
wol-systemd W: Dependency included and not needed ('ethtool')

blackhole commented on 2021-10-08 07:00 (UTC)

I don't think that is necessary if the licence type is declared in the PKGBUILD:

license=('MIT')

alerque commented on 2021-10-07 21:59 (UTC)

This package is missing the required license directory.

matejdro commented on 2021-01-21 16:07 (UTC)

Awesome, thanks!

blackhole commented on 2021-01-21 15:31 (UTC)

Done!

matejdro commented on 2021-01-21 15:00 (UTC)

Any chance this package is updated with After set to:

After=network-online.target

On my machine it seems like network card (r8169) is initialized AFTER network.target is up, which means this script fails to enable WOL. Moving initialization to network-online.target fixes the issue.

phiresky commented on 2015-11-21 00:39 (UTC)

@bayone Updated with a warning in .install if network manager is present. Also disowning because I use NetworkManager.

bayone commented on 2015-11-20 07:11 (UTC)

@phiresky It is not conflicting in a classic sense. Maybe put in a message during installation to check if the NetworkManager is installed (it comes with most DEs, AFAIK) and if yes, to enable WOL using nmcli (https://wiki.archlinux.org/index.php/Wake-on-LAN).

phiresky commented on 2015-11-17 12:56 (UTC)

@bayone so should I add NetworkManager as a conflict?

bayone commented on 2015-11-17 06:16 (UTC) (edited on 2015-11-17 06:25 (UTC) by bayone)

This is pretty useless if NetworkManager >= 1.0.6 is installed on the system. "systemctl start wol@enp5s0.service" works for hibernation, but not for shutdown. "systemctl enable wol@enp5s0.service" does not give me any results after restart. The reason is that Network Manager disables WOL after systemctl runs this service at boot. The proper way is setting NM as described in https://wiki.archlinux.org/index.php/Wake-on-LAN

Stebs commented on 2015-09-13 17:53 (UTC)

Sorry, my fault, didn't see that "interface" in "Then activate this new service by starting wol@interface.service." Somehow believed that systemd would replace %i with active interface...

phiresky commented on 2015-09-13 12:05 (UTC)

did you enable/run it with systemctl start wol@enp5s0.service?

Stebs commented on 2015-09-12 15:02 (UTC)

Got some problem here: %i is not replaced correctly!?: systemd[1]: Starting Wake-on-LAN for .system... ethtool[2716]: Cannot get current wake-on-lan settings: No such device ethtool[2716]: not setting wol systemd[1]: Started Wake-on-LAN for .system. Workaround for my LAN (enp5s0): ExecStart=/usr/bin/ethtool -s enp5s0 wol g