From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 71118@debbugs.gnu.org
Subject: [bug#71118] [PATCH 2/5] services: tor: Log to stderr rather than syslog.
Date: Fri, 24 May 2024 08:44:33 -0400 [thread overview]
Message-ID: <87zfsfidla.fsf@gmail.com> (raw)
In-Reply-To: <8734q8c23o.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 23 May 2024 11:24:43 +0200")
Hi Ludovic,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> * gnu/services/networking.scm (tor-configuration->torrc): Change ‘Log’
>>> directive to ‘stderr’.
>>> (tor-shepherd-service): Remove /dev/log file system mapping.
>>>
>>> Change-Id: I2e33ad8033f884ce59d929a4181172325331efe0
>
> [...]
>
>> I see no functional change here; do I understand that Shepherd 1.0 will
>> now log (by default?) to /dev/error (stderr) instead of /dev/log
>> (syslog)? What is the rationale for such change?
>
> Shepherd by itself doesn’t make any decision; it’s up to the service to
> choose whether to log to stdout/stderr or to syslog.
I see.
> As I wrote in the cover letter at <https://issues.guix.gnu.org/71118>,
> Shepherd 0.10 already does a good job at handling logs, which makes
> gives less of an incentive to use syslogd; on top of that, 1.0 (current
> ‘devel’ branch) can display messages logged to stderr/stdout directly at
> the command line:
>
> $ sudo /run/current-system/profile/bin/herd status guix-publish
> Status of guix-publish:
> It is running since Tue 21 May 2024 08:44:57 AM CEST (2 days ago).
> PID 518 running: /gnu/store/12jb83hlngklkymn52yzaw7kldr2qiwp-guix-1.4.0-20.37719d3/bin/guix publish -u guix-publish -p 8123 -C zstd:3 -C gzip:3 --nar-path=nar --listen=0.0.0.0 --advertise
> It is enabled.
> Provides (guix-publish).
> Requires (user-processes guix-daemon avahi-daemon).
> Will be respawned.
> Log file: /var/log/guix-publish.log.
>
> Recent messages:
> 2024-05-21 10:56:10 In web/request.scm:
> 2024-05-21 10:56:10 205:32 4 (read-request #<closed: file 7f5f48418af0> _)
> 2024-05-21 10:56:10 In web/http.scm:
> 2024-05-21 10:56:10 1158:12 3 (read-request-line _)
> 2024-05-21 10:56:10 1066:2 2 (parse-request-uri _ _ _)
> 2024-05-21 10:56:10 In ice-9/boot-9.scm:
> 2024-05-21 10:56:10 1685:16 1 (raise-exception _ #:continuable? _)
> 2024-05-21 10:56:10 1685:16 0 (raise-exception _ #:continuable? _)
> 2024-05-21 10:56:10 .Bad request: Invalid URI: 85.94.204.153:31204
> 2024-05-21 10:56:10
>
> It’s a slight quality-of-life improvement.
I agree that's more convenient than grepping /var/log/messages.
Thanks for explaining and for the Shepherd improvements!
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-05-24 12:47 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
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 [this message]
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=87zfsfidla.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=71118@debbugs.gnu.org \
--cc=ludo@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 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).