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: Wed, 22 May 2024 13:28:10 -0400 [thread overview]
Message-ID: <87sey93get.fsf@gmail.com> (raw)
In-Reply-To: <e1fe5dcf2571fcf24a2187ea0d2809db5ff32c8c.1716386553.git.ludo@gnu.org> ("Ludovic Courtès"'s message of "Wed, 22 May 2024 16:53:37 +0200")
Hi Ludovic,
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
> ---
> gnu/services/networking.scm | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/gnu/services/networking.scm b/gnu/services/networking.scm
> index 8e64e529abf..378e117a869 100644
> --- a/gnu/services/networking.scm
> +++ b/gnu/services/networking.scm
> @@ -1001,7 +1001,7 @@ (define (tor-configuration->torrc config)
> (display "\
> ### These lines were generated from your system configuration:
> DataDirectory /var/lib/tor
> -Log notice syslog\n" port)
> +Log notice stderr\n" port)
> (when (eq? 'unix '#$socks-socket-type)
> (display "\
> SocksPort unix:/var/run/tor/socks-sock
> @@ -1046,9 +1046,6 @@ (define (tor-shepherd-service config)
> (source "/var/lib/tor")
> (target source)
> (writable? #t))
> - (file-system-mapping
> - (source "/dev/log") ;for syslog
> - (target source))
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?
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-05-22 17:30 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sey93get.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 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.