On Fri, 2024-12-13 at 17:44 +0100, Jan Claeys wrote:
> Assuming this backup is started by an automated system under control of
> the sysadmins, and not by the users themselves, it's probably easiest
> to use some sort of "lock" that is set by the backup process itself (or
> that you wrap around it)
On Sat, 2024-12-07 at 20:27 +0100, Felix Natter wrote:
> - there is no significant load during the last hour (in order to
> account for backup jobs)
Assuming this backup is started by an automated system under control of
the sysadmins, and not by the users themselves, it's probably easiest
to use
On 09/12/2024 19:53, Anssi Saari wrote:
I think every desktop environment has this. Even X has this. 'This'
being a timer since last mouse or keyboard event and the ability to
trigger a command on the timer. I looked recently but didn't really find
a way to do the Windows like thing, turn off scr
Felix Natter writes:
> Dear Debian users,
>
> I am looking for an automatic suspend-to-ram (I know "sudo systemctl
> suspend" ;-)) solution for workstations: I would like the system to
> suspend if and only if:
>
> - there is no gui interaction from any user (especially with VNC
> sessions) AND
* Felix Natter [24-12/07=Sa 20:27 +0100]:
> [...] no significant load during the last hour [...]
The system doesn't keep track of load for a
full hour, but it does for fifteen minutes.
uptime|awk '{print $NF}'
is load average for the past 15 minutes.
> [...] no gui interaction [...] (especiall
5 matches
Mail list logo
