unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Sockets in Shepherd, and Emacs, oh my!
Date: Mon, 18 Apr 2022 23:14:25 +0200	[thread overview]
Message-ID: <bab9adddcab220b8b82592cf66486272f12db6a5.camel@gmail.com> (raw)
In-Reply-To: <874k2qxjmr.fsf@gnu.org>

Am Montag, dem 18.04.2022 um 21:43 +0200 schrieb Ludovic Courtès:
> Hi,
> 
> Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
> 
> > Am Sonntag, dem 10.04.2022 um 22:40 +0200 schrieb Ludovic Courtès:
> 
> [...]
> 
> > 
> > > What do you mean by “claiming the socket”?  Do you have a log
> > > file showing this, or at (better yet) a small reproducer?  You
> > > can use ‘tests/systemd.sh’ as a starting point.
> > Emacs without systemd support simply exits, because Shepherd owns
> > the socket.  I think a rather simple command that exits immediately
> > or after sleep 5 ought to do the trick.
> 
> Hmm could you share such a reproducer?  I’m not sure I understand.
Hmm, this test indeed works as intended on master, and when I try to
invoke bad behaviour deliberately in the way I pointed out, it seems to
restart the service cleanly.  I haven't checked the release commit, but
the emacs reproducer would be the following:

A.1 Build Emacs without systemd support.
A.2 Start my emacs service.
A.3 Launch emacsclient (due to emacs dying, emacsclient should either
die or loop forever/until a timeout, can't remember)
A.4 Launch emacsclient again.

B.1 Build Emacs with systemd support
B.2 Start my emacs service
B.3 Launch emacsclient (due to emacs supporting systemd, emacsclient
should run)
B.4 Use M-x kill-emacs to kill the emacs service.
B.5 Launch emacsclient again (it should fail to launch)

Thinking about it some more, I am probably dumb and forgot #:respawn?
#t.  Looking at my mail, it most definitely seems as though I did. 
Well, that's a lesson learned, #:respawn? is #f normally.

Cheers


  reply	other threads:[~2022-04-18 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 18:40 Sockets in Shepherd, and Emacs, oh my! Liliana Marie Prikler
2022-04-10 20:40 ` Ludovic Courtès
2022-04-11  4:23   ` Liliana Marie Prikler
2022-04-18 19:43     ` Ludovic Courtès
2022-04-18 21:14       ` Liliana Marie Prikler [this message]
2022-04-20  9:50         ` 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=bab9adddcab220b8b82592cf66486272f12db6a5.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=guix-devel@gnu.org \
    --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).