From: Leo Famulari <leo@famulari.name>
To: Andreas Enge <andreas@enge.fr>
Cc: myglc2 <myglc2@gmail.com>, 22695@debbugs.gnu.org
Subject: bug#22695: Binary Installation bugs and suggestions
Date: Tue, 16 Feb 2016 14:53:07 -0500 [thread overview]
Message-ID: <20160216195307.GA19703@jasmine> (raw)
In-Reply-To: <20160216195048.GA19487@jasmine>
On Tue, Feb 16, 2016 at 02:50:48PM -0500, Leo Famulari wrote:
> On Tue, Feb 16, 2016 at 05:51:37PM +0100, Andreas Enge wrote:
> > On Tue, Feb 16, 2016 at 11:19:34AM -0500, myglc2 wrote:
> > > "Thompson, David" <dthompson2@worcester.edu> writes:
> > > > What didn't work, exactly? I've personally done this on systemd
> > > > setups and it works fine.
> > > When I reboot my Debian 8 server, guix-daemon is not running.
> >
> > I had the same experience on my arm machines. So this might be a real bug.
> > Or does one need to do more than copy the file and reboot?
>
> Standard systemd service installation:
>
> $ cp foo.service where-you-want-it && systemctl daemon-reload && systemctl start foo.service
>
> No reboot is necessary.
I forgot a step:
$ cp foo.service where-you-want it && systemctl daemon-reload \
&& systemctl enable foo && systemctl start foo
You can start foo without enabling, but enabling is what makes it start
automatically.
>
> >
> > Andreas
> >
> >
> >
> >
>
>
>
next prev parent reply other threads:[~2016-02-16 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 13:41 bug#22695: Binary Installation bugs and suggestions myglc2
2016-02-16 14:00 ` Thompson, David
2016-02-16 14:19 ` Ricardo Wurmus
2016-02-16 16:19 ` myglc2
2016-02-16 16:51 ` Andreas Enge
2016-02-16 17:13 ` Jookia
2016-02-16 19:09 ` myglc2
2016-02-16 20:25 ` Mathieu Lirzin
2016-02-16 19:50 ` Leo Famulari
2016-02-16 19:53 ` Leo Famulari [this message]
2016-02-16 21:34 ` Jookia
2016-02-16 17:06 ` Jookia
2016-02-16 17:32 ` Ricardo Wurmus
2016-02-16 19:04 ` myglc2
2016-02-29 14:26 ` Ludovic Courtès
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=20160216195307.GA19703@jasmine \
--to=leo@famulari.name \
--cc=22695@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=myglc2@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).