all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix shepherd user services
Date: Sat, 04 May 2019 13:45:07 +0200	[thread overview]
Message-ID: <87d0kysat8.fsf@nckx> (raw)
In-Reply-To: <20190504070718.xdt6i5475xydvh7i@melmoth>

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

Tanguy,

My apologies for not replying sooner.  I fail at managing the 
scarce free time I have these days.

Tanguy Le Carrour wrote:
>> Cooooool! :-)
>> Did you write the "much more snipped" by yourself?

I snipped some definitions for other services, like ibus-daemon 
and gpg-agent, because I haven't used them in a long time (didn't 
want to risk confusing anyone with code that might've bitrotted), 
and they don't add any new concepts to the emacs example.  It's 
more of the same.  You're not missing anything.

>> If yes, is it available somewhere? Else, is it documented 
>> somewhere?
>> Did you copy/paste it from another Guix file?

Only in my home directory :-)  No on-line dotfiles like the other 
cool kids.

I figured this much out on my own, but my use of the Shepherd's 
probably pretty basic.

Its manual isn't as far along as Guix's and, to be honest, didn't 
make much sense to me until *after* learning what I know from 
reading the code & good old trial and error.

> I've been playing with shepherd and service configurations and 
> it's
> actually easier than I thought it would be, at least for 
> "simple"
> services. Thanks for showing me the way! :-)
>
> I love it so much that I started/stopped the emacs service 
> (defined with
> the snippet above) a few times.

Hours of fun!  Happy to have helped.

> It works as expected, except for the `defunct` processes that 
> hang
> around.  Each time I run `herd stop emacs`, I get a new one, as 
> if
> shepherd could not forget about the dead process.  This doesn't
> prevent me from re-starting the process and using the service, 
> but
> it looks… messy!
>
> Am I doing something wrong?!

No, you're right, I'd simply never checked this before.  Stopping 
emacs gives me… Zombie emacs.  And mu.

Kind regards,

T G-R


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

  reply	other threads:[~2019-05-04 11:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29 19:57 Guix shepherd user services Tanguy Le Carrour
2019-04-29 20:10 ` Tobias Geerinckx-Rice
2019-05-01  9:00   ` Tanguy Le Carrour
2019-05-04  7:07     ` Tanguy Le Carrour
2019-05-04 11:45       ` Tobias Geerinckx-Rice [this message]
2019-05-08  7:30         ` Tanguy Le Carrour
  -- strict thread matches above, loose matches on Subject: below --
2019-02-10 15:02 Pierre Neidhardt
2019-02-10 17:21 ` Gábor Boskovits
2019-02-10 18:22   ` Pierre Neidhardt

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=87d0kysat8.fsf@nckx \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=tanguy@bioneland.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.