11–20 of 230 posts
Earlier quoted context omitted.
I've never had any issues with stand-by on Windows.
Windows in particular is notorious as of late for brutally draining the battery while Sleeping[1]. [1]: https://www.youtube.com/watch?v=OHKKcd3sx2c
>Why isn't this build into every major operating system by now? Because no desktop OS besides MacOS can handle Sleep with any semblance of competency. >Why isn't this the default See above.
Earlier quoted context omitted.
Windows in particular is notorious as of late for brutally draining the battery while Sleeping[1]. [1]: https://www.youtube.com/watch?v=OHKKcd3sx2c
I thought we were talking about just supporting going to stand-by , not about how much power the device draws while on stand-by.
And even before then Sleep was very hit-or-miss anyway. I've never used Sleep because it's just far too inconsistent and thus unreliable, compared to just shutting the thing down when I don't need it for a while.
>Why isn't this build into every major operating system by now? Because no desktop OS besides MacOS can handle Sleep with any semblance of competency. >Why isn't this the default See above.
>Why isn't this the default (or at least a configuration option)? Because 1) you still need a second machine to wait for incoming requests, 2) in a server there's no general way to check if the server is serving requests or not. Plex happened to provide an API that specifically does what you needed, but you had to resort to a bit of a hack for Time Machine. This is unlike a desktop context, where you can check if the…
Maybe he has different ideas, and that's perfectly fine, but personally I value reliability and uptime far more than 2 cents.
EDIT: I failed at math. See below comments. :V
>Why isn't this build into every major operating system by now? Because no desktop OS besides MacOS can handle Sleep with any semblance of competency. >Why isn't this the default See above.
I've spent the last 5 years trying to figure out how to get Macs to remember which display goes on the left when waking from sleep. No luck yet, maybe it's fixed in Ventura or with M2s?
https://github.com/jakehilborn/displayplacer
Later I chained the displays differently and moved the adapters around so it stopped being an issue.
Interesting solution. I wonder if you could make the 'wake up' a bit more advanced. Run tcpdump or something similar on the Pi, with a filter set for inbound packets to the media server on ports that Plex or Time Machine uses. If it sees those packets, send the WoL magic packet. This might not work if your switch does proper port isolation - but you could perhaps add port mirroring or something like that.
I'm a little out of my wheelhouse though. Maybe that would only work for HTTP which will not cover Time Machine?
Does Time Machine run on a schedule? Add a cron job (whatever the Mac equivalent is) to send a WoL ~1min beforehand?
Earlier quoted context omitted.
I thought we were talking about just supporting going to stand-by , not about how much power the device draws while on stand-by.
Brutally draining the battery while aSleep should never be called "supporting Sleep". And even before then Sleep was very hit-or-miss anyway. I've never used Sleep because it's just far too inconsistent and thus unreliable, compared to just shutting the thing down when I don't need it for a while.
A Python script that automatically suspends the server, when it is not used, and another script to wake the server up again, in case there is work to do. To my surprise I could not find any out-of-the-box solution, so I thought, it is a worthwhile effort to write about it. Currently, the server is primarily used for two things: - Plex Media Streaming (remotely) - Time Machine Backups (locally) To monitor Plex activit…