From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Guix-Help <help-guix@gnu.org>
Subject: Re: Several questions on Guix(SD)
Date: Mon, 29 Aug 2016 11:36:18 +0200 [thread overview]
Message-ID: <20160829113618.63e36824@alma-ubu> (raw)
In-Reply-To: <20160826232311.GB8782@jasmine>
Hi Leo,
On Fri, 26 Aug 2016 19:23:11 -0400
Leo Famulari <leo@famulari.name> wrote:
> On Thu, Aug 25, 2016 at 11:03:32PM +0200, Björn Höfling wrote:
> > Leo, thank you for your answers. I would like some more
> > clarifications:
> >
> > On Mon, 22 Aug 2016 17:49:21 -0400
> > Leo Famulari <leo@famulari.name> wrote:
> > > The log output of the daemon goes wherever your daemons normally
> > > log to. On most recent versions of the major distros, this is
> > > handled by systemd / journald.
> >
> > My distro in that case is GuixSD, using shepherd. So I found
> > information about guix-daemon start and stop events
> > in /var/log/shepherd.log. But I want some more information about
> > the daemon. Is guix-daemon so silent?
> >
> > I figured out that I can (modify-services %base-services ...) for
> > adding the "--debug" extra-options to guix-daemon. Still I see only
> > start/stop log entries in shepherd.log. What am I missing?
>
> Somebody else could answer this better than me, but I'll give it a
> shot. The guix-daemon is indeed laconic, even with --debug. Here, is
> what it prints when I start it manually and run `guix gc
> -d /gnu/store/...-hello`:
>
> ---
> # /root/.guix-profile/bin/guix-daemon --build-users-group=guixbuild
> --debug extra chroot directories: ''
> automatic deduplication set to 1
> listening on `/var/guix/daemon-socket/socket'
> accepted connection from pid 9343, user leo
> 1 operations
> ---
>
> On GuixSD, it seems that the daemon just prints to the console. I
> have a non-graphical system and the daemon's output is rather
> annoying in the rare case that I am sitting at the machine.
>
> If you are looking for logs of package building, you can do `guix
> build foo --log-file`. You will often need to add `--no-grafts` to
> see the "real" build log instead of the log of the grafting operation.
>
> Does that help answer your question at all?
I also noticed that it prints to the console. I hoped that it would
print a bit more output to some logfile. But that's fine for now, that
answers my question. Thank you.
Björn
next prev parent reply other threads:[~2016-08-29 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 20:53 Several questions on Guix(SD) Björn Höfling
2016-08-22 21:49 ` Leo Famulari
2016-08-25 21:03 ` Björn Höfling
2016-08-26 23:15 ` Leo Famulari
2016-08-26 23:23 ` Leo Famulari
2016-08-29 9:36 ` Björn Höfling [this message]
2016-08-30 12:24 ` Ludovic Courtès
2016-08-23 7:25 ` Florian Paul Schmidt
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=20160829113618.63e36824@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--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.
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.