From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
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: Thu, 23 May 2024 11:26:03 +0200 [thread overview]
Message-ID: <87y180anh0.fsf@gnu.org> (raw)
In-Reply-To: <871q5t4v96.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 22 May 2024 13:22:13 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> 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
[...]
>> +@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}.
>
> Is it not a bit counter-intuitive, to have a 'log-file' field that users
> can set, but debug logs not going there?
Yeah, I had to check the code of nscd in libc, and it’s this weird.
> Perhaps we should get rid of it entirely instead?
I’d rather keep it to avoid gratuitous breakage and also because it’s
occasionally useful when one needs to debug NSS/nscd issues.
Ludo’.
next prev parent reply other threads:[~2024-05-23 9:27 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 [this message]
2024-05-24 12:45 ` Maxim Cournoyer
2024-05-22 17:25 ` Maxim Cournoyer
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=87y180anh0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=71118@debbugs.gnu.org \
--cc=matt@excalamus.com \
--cc=maxim.cournoyer@gmail.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).