From: Maxime Devos <maximedevos@telenet.be>
To: Timothy Sample <samplet@ngyro.com>, Leo Famulari <leo@famulari.name>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 52051@debbugs.gnu.org
Subject: bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out)
Date: Tue, 21 Dec 2021 16:52:19 +0000 [thread overview]
Message-ID: <596551103b98265f46051b7898f5ca38744c7401.camel@telenet.be> (raw)
In-Reply-To: <87fsqlewzd.fsf@ngyro.com>
Timothy Sample schreef op di 21-12-2021 om 11:36 [-0500]:
> + (limit (@ (name "auth_timeout")) "60000")
Are there any good reasons for having a timeout at all?
(Except for the local-user denial of service, but local users can do
"guix build -f something-that-allocates-almost-all-memory-and-melts-
the-cpu.scm" anyway ...)
If not, can the timeout be disabled/set to infinity?
A comment like
> ;; Set timeout to a huge number (16.6 hours), because
> ;; upstream often sets timeouts low for spinning disks,
> ;; slow CPUs, etc.
> (limit [...] "60000")
could be useful (I'm assuming the timeout is in seconds here).
Greetings,
Maxime.
next prev parent reply other threads:[~2021-12-21 17:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 6:47 bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out) Maxim Cournoyer
2021-11-24 9:02 ` Josselin Poiret via Bug reports for GNU Guix
2021-11-25 3:03 ` Maxim Cournoyer
2021-11-25 22:13 ` Ludovic Courtès
2021-11-25 4:07 ` Maxim Cournoyer
2021-11-25 22:07 ` Maxim Cournoyer
2021-11-26 9:35 ` Josselin Poiret via Bug reports for GNU Guix
2021-12-07 21:23 ` Maxim Cournoyer
2021-12-07 22:15 ` Maxim Cournoyer
2021-12-08 22:18 ` Ludovic Courtès
2021-12-09 14:18 ` Maxim Cournoyer
2021-12-09 22:15 ` Ludovic Courtès
2021-12-10 5:09 ` Maxim Cournoyer
2021-12-10 10:17 ` Ludovic Courtès
2021-12-16 18:24 ` Josselin Poiret via Bug reports for GNU Guix
2021-12-21 9:31 ` Timothy Sample
2021-12-21 16:13 ` Leo Famulari
2021-12-21 16:36 ` Timothy Sample
2021-12-21 16:52 ` Maxime Devos [this message]
2021-12-21 17:32 ` Leo Famulari
2021-12-21 17:51 ` Maxime Devos
2021-12-21 18:11 ` Leo Famulari
2021-12-21 17:37 ` Leo Famulari
2021-12-21 17:44 ` Leo Famulari
2021-12-08 2:12 ` Maxim Cournoyer
2021-12-15 19:27 ` Michael Rohleder
2021-12-16 3:36 ` Abhiseck Paira via Bug reports for GNU Guix
2021-12-16 13:09 ` ison
2021-12-16 17:59 ` bug#52051: [core-updates-frozen] cannot login Guillaume Le Vaillant
2021-12-16 18:53 ` bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out) Michael Rohleder
2021-12-20 0:40 ` Caleb Herbert
2021-12-22 1:46 ` Luis Felipe via Bug reports for GNU Guix
2021-12-22 2:19 ` Leo Famulari
2021-12-22 21:16 ` Leo Famulari
2021-12-22 23:38 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=596551103b98265f46051b7898f5ca38744c7401.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52051@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=maxim.cournoyer@gmail.com \
--cc=samplet@ngyro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.