[Top][All Lists]

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

Re: Several questions on Guix(SD)

From: Leo Famulari
Subject: Re: Several questions on Guix(SD)
Date: Fri, 26 Aug 2016 19:23:11 -0400
User-agent: Mutt/1.7.0 (2016-08-17)

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 <address@hidden> 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?

reply via email to

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