Actually, I may have expressed myself incorrectly. The issue is not with Wake-on-LAN itself, but rather with the cron task responsible for executing it.
Since the June 2 update, the cron job is no longer running according to its previous configuration.
Is there any known issue, bug report, or open ticket related to this behavior?
Since the June 2 update, the cron job is no longer running according to its previous configuration.
Is there any known issue, bug report, or open ticket related to this behavior?
"