emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#29707: closed ("guix system search" doesn't show h


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#29707: closed ("guix system search" doesn't show how to start/stop service)
Date: Mon, 30 Apr 2018 12:54:02 +0000

Your message dated Mon, 30 Apr 2018 14:53:21 +0200
with message-id <address@hidden>
and subject line Re: bug#29707: "guix system search" doesn't show how to 
start/stop service
has caused the debbugs.gnu.org bug report #29707,
regarding "guix system search" doesn't show how to start/stop service
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
29707: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29707
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: "guix system search" doesn't show how to start/stop service Date: Thu, 14 Dec 2017 11:30:14 +0100 User-agent: mu4e 0.9.18; emacs 25.3.1
The "guix system search" command doesn't show how we are supposed to
start/stop the searched service.

For example, I think it would be useful to know that "herd stop
xmpp-daemon" stops the XMPP server and "herd stop xorg-server" stops the
Xorg server.

Neither "guix system search xorg" nor "guix system search slim" says
anything about "xorg-server".



--- End Message ---
--- Begin Message --- Subject: Re: bug#29707: "guix system search" doesn't show how to start/stop service Date: Mon, 30 Apr 2018 14:53:21 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Hi Clément,

Clément Lassieur <address@hidden> skribis:

> The "guix system search" command doesn't show how we are supposed to
> start/stop the searched service.
>
> For example, I think it would be useful to know that "herd stop
> xmpp-daemon" stops the XMPP server and "herd stop xorg-server" stops the
> Xorg server.
>
> Neither "guix system search xorg" nor "guix system search slim" says
> anything about "xorg-server".

Commit 6ac8b7359a1ac80e558f41dd37004ffa727dd3c6 does roughly what you
suggested:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix system search slim
name: slim
location: gnu/services/xorg.scm:510:2
extends: shepherd-root pam profile
shepherdnames: xorg-server
relevance: 3
--8<---------------cut here---------------end--------------->8---

Note that there are limitations: here ‘shepherdnames’ is just the list
of names of the _default_ Shepherd services for that service type.  But
due to the way service extensions work, actual Shepherd service names
can very well depend on the configuration of the service.  For example,
‘console-font-service-type’ generates a Shepherd service whose name
depends on its configuration: ‘console-font-tty1’, etc.

Besides, ‘guix system search xmpp’ currently returns nothing, but it
will return something as soon as you’ve added a ‘description’ to
‘prosody-service-type’.  If you add a ‘default-value’, you’ll get
‘shepherdnames’ as well.  Hint hint.  ;-)

Cheers,
Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]