GNU bug report logs - #29707
"guix system search" doesn't show how to start/stop service

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Clément Lassieur <clement <at> lassieur.org>
Subject: bug#29707: closed (Re: bug#29707: "guix system search" doesn't
 show how to start/stop service)
Date: Mon, 30 Apr 2018 12:54:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#29707: "guix system search" doesn't show how to start/stop service

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 29707 <at> debbugs.gnu.org.

-- 
29707: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29707
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: ludo <at> gnu.org (Ludovic Courtès)
To: Clément Lassieur <clement <at> lassieur.org>
Cc: 29707-done <at> debbugs.gnu.org
Subject: Re: bug#29707: "guix system search" doesn't show how to start/stop
 service
Date: Mon, 30 Apr 2018 14:53:21 +0200

Hi Clément,

Clément Lassieur <clement <at> lassieur.org> 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’.

[Message part 3 (message/rfc822, inline)]

From: Clément Lassieur <clement <at> lassieur.org>
To: bug-guix <at> gnu.org
Subject: "guix system search" doesn't show how to start/stop service
Date: Thu, 14 Dec 2017 11:30:14 +0100

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".

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.