On 11/1/25 11:47, Ben Koenig wrote:
On Saturday, November 1st, 2025 at 11:41 AM, Russell Senior
<[email protected]> wrote:
Dear lazyweb (as they say on the anti-social media),
As hard as this is to believe, I only recently started playing with
wake-on-lan. A few of my home lab computers don't need to run all the
time, and so I have discovered that I can just "systemctl suspend" them
and then, later, send them a wake-on-lan packet and have them spring
back to life without the annoying exercise associated with walking down
some stairs to physically interact with them.
One remaining annoyance is that some of the computers or, perhaps,
network cards boot up in the wrong wake-on-lan mode and I have to
reconfigure wake-on-lan with "ethtool". I don't want to have to remember
that every time, so I'm looking for some convenient systemd method for
running the ethtool command line every time it boots.
Anyone happen to have a favorite method, off hand?
These are mostly ubuntu boxes of some permutation or another.
Thanks!
--
Russell Senior
[email protected]
The classic way to do this would be to add whatever commands you want to
/et/rc.d/rc.local. Given how much people love systemd I'm sure it provides an
equivalent function under a different name.
There might even be some sort of "legacy compatibility" implementation of
rc.local.
Out of curiosity, is there a specific time when this command would be run? Is
it something you can add as the last step init performs before you log in or
does it have to happen before something else? That would make a big difference
in where/how you add it.
For my purposes, it just has to run after the network interface has been
discovered (so, e.g. eth0 needs to exist) and before I get around to
logging in and manually running "systemctl suspend", so otherwise timing
isn't critical.
-Ben
