From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 71118@debbugs.gnu.org, Matthew Trzcinski <matt@excalamus.com>,
Florian Pelz <pelzflorian@pelzflorian.de>
Subject: [bug#71118] [PATCH 1/5] services: nscd: ‘log-file’ defaults to #f.
Date: Wed, 22 May 2024 13:25:51 -0400 [thread overview]
Message-ID: <87wmnl3gio.fsf@gmail.com> (raw)
In-Reply-To: <91683e6a6059df7816833d4e4d1e3bfc43aa74e7.1716386553.git.ludo@gnu.org> ("Ludovic Courtès"'s message of "Wed, 22 May 2024 16:53:36 +0200")
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> * gnu/services/base.scm (<nscd-configuration>)[log-file]: Default to #f.
> * doc/guix.texi (Base Services): Clarify documentation.
>
> Change-Id: Ia75914fc2665db13bef688d53659083a615ebef4
> ---
> doc/guix.texi | 8 +++++---
> gnu/services/base.scm | 2 +-
> 2 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 8073e3f6d49..0055724e658 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -19446,9 +19446,11 @@ Base Services
> Package object denoting the GNU C Library providing the @command{nscd}
> command.
>
> -@item @code{log-file} (default: @code{"/var/log/nscd.log"})
> -Name of the nscd log file. This is where debugging output goes when
> -@code{debug-level} is strictly positive.
> +@item @code{log-file} (default: @code{#f})
> +Name of the nscd log file. Debugging output goes to that file when
> +@code{debug-level} is strictly positive, or to standard error if it is
> +@code{#f}. Regular messages are written to syslog when
> +@code{debug-level} is zero, regardless of the value of @code{log-file}.
My initial reading of the above was wrong. I guess it's fine, though I
find the special case logging to /dev/error when debug-level == 0
despite log-file being set a bit surprising still.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-05-22 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 14:04 [bug#71118] [PATCH 0/5] More service logging to stderr Ludovic Courtès
2024-05-22 14:53 ` [bug#71118] [PATCH 1/5] services: nscd: ‘log-file’ defaults to #f Ludovic Courtès
2024-05-22 17:22 ` Maxim Cournoyer
2024-05-23 9:26 ` Ludovic Courtès
2024-05-24 12:45 ` Maxim Cournoyer
2024-05-22 17:25 ` Maxim Cournoyer [this message]
2024-05-22 14:53 ` [bug#71118] [PATCH 2/5] services: tor: Log to stderr rather than syslog Ludovic Courtès
2024-05-22 17:28 ` Maxim Cournoyer
2024-05-23 9:24 ` Ludovic Courtès
2024-05-24 12:44 ` Maxim Cournoyer
2024-05-22 14:53 ` [bug#71118] [PATCH 3/5] services: dbus: " Ludovic Courtès
2024-05-22 17:30 ` Maxim Cournoyer
2024-05-22 14:53 ` [bug#71118] [PATCH 4/5] services: avahi: Use socket activation and log to stderr Ludovic Courtès
2024-05-22 14:53 ` [bug#71118] [PATCH 5/5] services: darkstat: Depend on ‘user-processes’ Ludovic Courtès
2024-05-22 17:30 ` Maxim Cournoyer
2024-05-24 12:46 ` [bug#71118] [PATCH 0/5] More service logging to stderr Maxim Cournoyer
2024-06-02 18:57 ` bug#71118: " 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=87wmnl3gio.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=71118@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=matt@excalamus.com \
--cc=pelzflorian@pelzflorian.de \
/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).