On 10/02/2022 13:05, Graeme Gemmill wrote:
On 10/02/2022 12:00, dorset-requ...@mailman.lug.org.uk wrote:
Send dorset mailing list submissions to
dorset@mailman.lug.org.uk
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/dorset
or,
On 10/02/2022 12:00, dorset-requ...@mailman.lug.org.uk wrote:
Send dorset mailing list submissions to
dorset@mailman.lug.org.uk
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/dorset
or, via email, send a message with subject
On 10/02/2022 11:07, Tim Waugh wrote:
On Thu, 10 Feb 2022 at 11:05, Hamish McIntyre-Bhatty
wrote:
The second command says it was "Passed" three days ago, but I
don't know
if that means it ran. There are no other timers in the output from
that
command.
We only asked for
On Thu, 10 Feb 2022 at 11:05, Hamish McIntyre-Bhatty
wrote:
> The second command says it was "Passed" three days ago, but I don't know
> if that means it ran. There are no other timers in the output from that
> command.
>
We only asked for the fstrim timer. 'systemctl list-timers' will show you
On 10/02/2022 10:06, Tim Waugh wrote:
On Wed, 9 Feb 2022 at 17:57, Hamish McIntyre-Bhatty
wrote:
I finally got around to that, only to find that it was already enabled,
and apparently not doing anything. As I don't leave my systems on 24/7,
is it safe to assume that the timer isn't firing
On Wed, 9 Feb 2022 at 17:57, Hamish McIntyre-Bhatty
wrote:
> I finally got around to that, only to find that it was already enabled,
> and apparently not doing anything. As I don't leave my systems on 24/7,
> is it safe to assume that the timer isn't firing when the system is
> booted up later,
6 matches
Mail list logo
