From: David Craven <david@craven.ch>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] service: Honor #:log-file in make-forkexec-constructor.
Date: Tue, 6 Sep 2016 22:02:00 +0200 [thread overview]
Message-ID: <CAL1_imkE82L3WR_qYm-PqGKR=XLv0DGth0NC6F++c0M=q9SjjQ@mail.gmail.com> (raw)
In-Reply-To: <20160906211332.46c690db@scratchpost.org>
>> Not syslog, but helps with debugging...
> That definitely helps - however, in the long run, I think that using syslog is better.
I agree, but someone has to write it...
> Syslog does the splitting up in different files (or not) and onto different machines
> (or not), filtering (or not), log rotation etc. So it makes sense to make services
> use syslog instead of rolling-your-own filtering, splitting, networking etcetc 267843
> times.
I don't intend to reimplement any of this. I just needed a way to dump
stuff to a file instead of a tty. It's intended for usage during
development of services, not for deployment. As Ludo mentioned it's
not quite as simple as just redirecting stdout/sderr and needs some
support in shepherd. Someone who actually runs services that require
high availability will have to contribute better logging support ;)
> That said the services should just use syslog on their own
Many services expect stdout/stderr to be handled. I don't think that
every service needs to reimplement basic logging functionality.
systemd allows to set a services stdout and stderr to either
journal/syslog/file/tty, so new services written for systemd expect
this to be taken care of.
> we could only guess when a new log message starts
New lines are a pretty good guess.
next prev parent reply other threads:[~2016-09-06 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 11:26 Shepherd redirect stdout/stderr to syslog David Craven
2016-09-05 13:44 ` David Craven
2016-09-05 21:14 ` Ludovic Courtès
2016-09-06 12:35 ` [PATCH] service: Honor #:log-file in make-forkexec-constructor David Craven
2016-09-06 12:36 ` David Craven
2016-09-06 19:13 ` Danny Milosavljevic
2016-09-06 20:02 ` David Craven [this message]
2016-09-11 13:34 ` 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='CAL1_imkE82L3WR_qYm-PqGKR=XLv0DGth0NC6F++c0M=q9SjjQ@mail.gmail.com' \
--to=david@craven.ch \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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.