On Thu, Feb 21, 2019 at 10:26:36PM +0100, Gabor Gombas wrote:
> On Wed, Feb 20, 2019 at 02:44:37PM -0800, Josh Triplett wrote:
>
> > Both syslog and journald support multi-line log messages; I'd *love* to
> > see /var/log/aptitude and /var/log/apt/history.log end up in syslog or
> > journald.
>
>
On Wed, Feb 20, 2019 at 02:44:37PM -0800, Josh Triplett wrote:
> Both syslog and journald support multi-line log messages; I'd *love* to
> see /var/log/aptitude and /var/log/apt/history.log end up in syslog or
> journald.
Both journald and syslog have problems with retention policies, or
rather t
]] Josh Triplett
For the normal and easy cases of line-oriented logs, I think something
in the direction of your proposal makes sense, but I think we need to
have exceptions for all the weird and wonderful exceptions out there,
such as the example below.
> - If the software has a well-establishe
Josh, I support the idea of doing work to unify logging more in Debian.
To the extent that you're looking for the initial consensus to start
putting together specific proposals and patches, yeah, doing that
per-package analysis and work seems useful.
I'd even support an eventual SHOULD in the rea
On Wed, Feb 20, 2019 at 03:38:41PM -0800, Russ Allbery wrote:
> Josh Triplett writes:
> > Both syslog and journald support multi-line log messages
>
> syslog does not support multi-line log messages in any reasonable way. It
> just escapes the newline (if you're lucky) and jams all the lines
> t
On Wed, Feb 20, 2019 at 02:03:08PM -0800, Josh Triplett wrote:
> While there are *absolutely* configurations in which system
> administrators want to log to arbitrary locations and files, I would
> like to propose that for consistency we should configure software to
> unify logging into syslog and/
Josh Triplett writes:
> Both syslog and journald support multi-line log messages
syslog does not support multi-line log messages in any reasonable way. It
just escapes the newline (if you're lucky) and jams all the lines
together, and is rather likely to break whatever log parser you have on
th
On Wed, Feb 20, 2019 at 11:53:24PM +0100, Guillem Jover wrote:
> * The log data is "chroot" specific. This applies to all of the package
> management logs. Logging into syslog would by default not do the right
> thing and would be extremely confusing. I could see adding options
> for dpkg and
On Wed, 2019-02-20 at 14:19:02 -0800, Russ Allbery wrote:
> Josh Triplett writes:
> > While there are *absolutely* configurations in which system
> > administrators want to log to arbitrary locations and files, I would
> > like to propose that for consistency we should configure software to
> > un
On Wed, Feb 20, 2019 at 02:19:02PM -0800, Russ Allbery wrote:
> Josh Triplett writes:
> > While there are *absolutely* configurations in which system
> > administrators want to log to arbitrary locations and files, I would
> > like to propose that for consistency we should configure software to
>
Josh Triplett writes:
> While there are *absolutely* configurations in which system
> administrators want to log to arbitrary locations and files, I would
> like to propose that for consistency we should configure software to
> unify logging into syslog and/or journald by default. In particular,
[Followups to debian-devel with CC to me, please, as I'm not
subscribed.]
Currently, while the majority of daemons support logging to syslog
and/or journald, a small handful of software ships configured to use its
own logfiles by default. For instance, update-alternatives logs to
/var/log/alternat
12 matches
Mail list logo
