unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: help-guix@gnu.org
Subject: Why does stopping user shepherd kill my Emacs and how I make it to stop?
Date: Fri, 22 Nov 2024 20:03:35 +0100	[thread overview]
Message-ID: <87y11bf5vc.fsf@wolfsden.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]


Hi,

today I noticed that when I stop my user shepherd (`herd stop root'), it
kills my Emacs instance.  I would like to point out that the Emacs
daemon is *not* managed by the Shepherd, I just start it using the
following in the `init.el':

--8<---------------cut here---------------start------------->8---
(require 'server)

(or (server-running-p)
    (server-start))
--8<---------------cut here---------------end--------------->8---

I do not have many user shepherd services:

--8<---------------cut here---------------start------------->8---
Started:
 + dbus
 + pulseaudio
 + root
 + ssh-agent
--8<---------------cut here---------------end--------------->8---

Emacs does not log anything into the terminal regarding the termination
cause, and shepherd does not mention anything at all.  Here is full log
from shepherd start to termination:

--8<---------------cut here---------------start------------->8---
Starting service root...
Service root started.
Service root running with value #t.
Service root has been started.
WARNING: Use of `load' in declarative module (#{ g107}#).  Add #:declarative? #f to your define-module invocation.
Daemonizing...
Restarting signal handler.
Now running as process 17602.
Starting services...
Configuration successfully loaded from '/home/wolf/.config/shepherd/init.scm'.
Starting service ssh-agent...
Starting service pulseaudio...
Starting service dbus...
Service ssh-agent has been started.
Service pulseaudio has been started.
Service dbus has been started.
Service ssh-agent started.
Successfully started 3 services in the background.
Service pulseaudio started.
Service dbus started.
Service ssh-agent running with value 17603.
Service pulseaudio running with value 17604.
Service dbus running with value 17605.
Stopping service root...
Stopping service ssh-agent...
Service ssh-agent stopped.
Service ssh-agent is now stopped.
Stopping service pulseaudio...
Service pulseaudio stopped.
Service pulseaudio is now stopped.
Stopping service dbus...
Service dbus stopped.
Service dbus is now stopped.
Exiting.
--8<---------------cut here---------------end--------------->8---

Would anyone be able to advice why this is happening (or at least how to
find out)?  And, more importantly, how do I prevent this?  I do *not*
want my Emacs coupled to my user shepherd.

Thanks a lot,
Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

             reply	other threads:[~2024-11-22 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22 19:03 Tomas Volf [this message]
2024-11-24  9:04 ` Why does stopping user shepherd kill my Emacs and how I make it to stop? Nils Landt

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=87y11bf5vc.fsf@wolfsden.cz \
    --to=~@wolfsden.cz \
    --cc=help-guix@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.
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).