From: Alex Kost <alezost@gmail.com>
To: Dick Middleton <dick@fouter.net>
Cc: help-guix@gnu.org
Subject: Re: Starting ssh service
Date: Mon, 11 Apr 2016 20:15:45 +0300 [thread overview]
Message-ID: <87vb3ohxry.fsf@gmail.com> (raw)
In-Reply-To: <570B72EA.40109@fouter.net> (Dick Middleton's message of "Mon, 11 Apr 2016 10:48:26 +0100")
Dick Middleton (2016-04-11 12:48 +0300) wrote:
> Placing lsh-service in %desktop-services allows guix to complete reconfigure
> but it doesn't start the service.
Do you mean that when you use:
(services (cons* (lsh-service #:port-number 22
#:daemonic? #t
#:root-login? #t)
%base-services))
the server is started, but with:
(services (cons*
(xfce-desktop-service)
(lsh-service #:port-number 22
#:daemonic? #t
#:root-login? #t)
%desktop-services))
it is not, right?
If so, I have no idea how this could happen.
> If instead I order assigning %base-services and %desktop-services so
> %base-services comes first (that was perhaps my mistake) then the build
> proceeds. However now lshd starts at boot time but the desktop GUI doesn't.
[...]
> (services (cons* (lsh-service #:port-number 22
> #:daemonic? #t
> #:root-login? #t)
> %base-services))
>
> ;; Add GNOME and/or Xfce---we can choose at the log-in
> ;; screen with F1. Use the "desktop" services, which
> ;; include the X11 log-in service, networking with Wicd,
> ;; and more.
> (services (cons*
> (xfce-desktop-service)
> ;; (gnome-desktop-service)
> %desktop-services))
'services' (and any other field) should be specified only once.
Apparently the first one (with %base-services) has a preference, so ssh
server is started and desktop services are not.
--
Alex
next prev parent reply other threads:[~2016-04-11 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 10:24 Starting ssh service Dick Middleton
2016-04-08 15:16 ` 宋文武
2016-04-11 9:48 ` Dick Middleton
2016-04-11 17:15 ` Alex Kost [this message]
2016-04-12 13:50 ` Dick Middleton
2016-04-11 18:48 ` myglc2
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=87vb3ohxry.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=dick@fouter.net \
--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).