From: nly <nly@disroot.org>
To: 34407@debbugs.gnu.org
Subject: bug#34407: Acknowledgement (Shepherd won't close socket on exit)
Date: Sun, 10 Feb 2019 01:51:47 +0530 [thread overview]
Message-ID: <87zhr44sro.fsf@disroot.org> (raw)
In-Reply-To: GNU bug Tracking System's message of "Sat\, 09 Feb 2019 19\:58\:02 +0000 \(12 minutes\, 20 seconds ago\)"
Looks like I pasted something wrong in the previous message. I realized
after I saw it on the mail.
This time I've checked it twice. Left the shepherd in a weird limbo
where connection is refused to the old socket and cannot create new
connection.
Ofcourse, i can `rm /run/user/1000/shepherd/socket`
--------------------------------------------------------------------------------
nly@uf ~$ herd status
error: connect: /run/user/1000/shepherd/socket: No such file or directory
nly@uf ~$ shepherd
Service root has been started.
nly@uf ~$ herd status
Started:
+ root
Stopped:
- icecat
- jack
- mpv
- mpv-jack
- tor
- transmission
nly@uf ~$ herd stop root
nly@uf ~$ herd status
error: connect: /run/user/1000/shepherd/socket: Connection refused
nly@uf ~$ shepherd
Service root has been started.
nly@uf ~$ Backtrace:
3 (primitive-load "/run/current-system/profile/bin/shepherd")
In shepherd.scm:
250:24 2 (main . _)
48:6 1 (open-server-socket _)
In unknown file:
0 (bind #<input-output: socket 13> #(1 "/run/user/1000/shepherd/socket") #)
ERROR: In procedure bind:
In procedure bind: Address already in use
C-c C-c
nly@uf ~$ herd status
error: connect: /run/user/1000/shepherd/socket: Connection refused
next prev parent reply other threads:[~2019-02-09 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 19:56 bug#34407: Shepherd won't close socket on exit nly
2019-02-09 20:21 ` nly [this message]
2019-02-13 23:05 ` bug#34407: Acknowledgement (Shepherd won't close socket on exit) Maxim Cournoyer
2019-02-17 3:38 ` bug#34407: [PATCH] shepherd: Delete the socket file upon exit 宋文武
2019-02-17 3:38 ` 宋文武
2019-02-19 19:08 ` bug#34407: " Danny Milosavljevic
2019-02-19 19:08 ` Danny Milosavljevic
2019-02-23 8:53 ` 宋文武
2019-02-23 8:53 ` bug#34407: " 宋文武
2019-04-08 8:58 ` Ludovic Courtès
2019-04-08 8:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhr44sro.fsf@disroot.org \
--to=nly@disroot.org \
--cc=34407@debbugs.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 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.