unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 58485@debbugs.gnu.org
Subject: bug#58485: [shepherd] Restarting guix-publish fails
Date: Fri, 14 Oct 2022 08:57:10 +0200	[thread overview]
Message-ID: <44ef002a53713d84cb57dbc7bc5f3eb9f8422290.camel@ist.tugraz.at> (raw)
In-Reply-To: <Y0j/J2ARzOYa2YUM@noor.fritz.box>

Am Freitag, dem 14.10.2022 um 08:18 +0200 schrieb Lars-Dominik Braun:
> Hi,
> 
> > Ahh, so the issue is that shepherd waits neither for the process to
> > be
> > actually killed nor for the socket to become available, isn't it?
> I would argue it’s the former, but having either of them would solve
> the problem, I think.
I think you need both: if the process is killed, but the socket
remains, you need to clean it up.  As far as I'm aware, that does not
happen automatically.

Cheers




  reply	other threads:[~2022-10-14  6:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13  7:51 bug#58485: [shepherd] Restarting guix-publish fails Lars-Dominik Braun
2022-10-13  9:28 ` Liliana Marie Prikler
2022-10-13 11:35   ` Lars-Dominik Braun
2022-10-13 13:38     ` Liliana Marie Prikler
2022-10-14  6:18       ` Lars-Dominik Braun
2022-10-14  6:57         ` Liliana Marie Prikler [this message]
2022-11-17  8:24 ` Ludovic Courtès
2022-11-17 10:19   ` Ludovic Courtès
2023-02-07  8:39   ` Lars-Dominik Braun
     [not found]   ` <Y+IM4IrO4V05o3V9@zpidnb93>
2023-02-20 10:20     ` Ludovic Courtès
2023-02-20 13:25       ` Lars-Dominik Braun
2023-04-27 21:23         ` Ludovic Courtès
2023-04-28 12:31           ` Lars-Dominik Braun
2023-04-28 13:09           ` bug#58485: [shepherd] EADDRINUSE while restarting ssh-daemon Ludovic Courtès
2023-06-11 14:20             ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44ef002a53713d84cb57dbc7bc5f3eb9f8422290.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=58485@debbugs.gnu.org \
    --cc=lars@6xq.net \
    --cc=ludo@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).