GNU bug report logs - #68476
Shepherd stops responding if you set the time less than the current one

Previous Next

To reply to this bug, email your comments to 68476 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Aleksandr Vityazev <avityazev <at> disroot.org>
To: bug-guix <at> gnu.org
Subject: Shepherd stops responding if you set the time less than the current
 one
Date: Mon, 15 Jan 2024 18:45:33 +0300

Hi,

I have running shepherd version 0.10.3 for the system and the user.  My
current time is Mon Jan 15 06:30:52 PM MSK 2024, if I set the time
less than the current one, both shepherds stop responding.

I set the time like this:
sudo date --set='20240115 18:00'

-- 
Best regards,
Aleksandr Vityazev

Message #8 received at 68476 <at> debbugs.gnu.org (full text, mbox):

From: Sergey Trofimov <sarg <at> sarg.org.ru>
To: Aleksandr Vityazev <avityazev <at> disroot.org>
Cc: 68476 <at> debbugs.gnu.org
Subject: Re: bug#68476: Shepherd stops responding if you set the time less
 than the current one
Date: Tue, 16 Jan 2024 07:44:06 +0100

Aleksandr Vityazev <avityazev <at> disroot.org> writes:

> Hi,
>
> I have running shepherd version 0.10.3 for the system and the 
> user.  My
> current time is Mon Jan 15 06:30:52 PM MSK 2024, if I set the 
> time
> less than the current one, both shepherds stop responding.
>
> I set the time like this:
> sudo date --set='20240115 18:00'

It's a known problem, see https://issues.guix.gnu.org/66684

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.