Louis Bouchard schreef op 18-01-2017 9:08:
Hello,
Le 17/01/2017 à 21:46, Bryan Quigley a écrit :
On Thu, Jan 12, 2017 at 11:20 AM, Jamie Strandboge
wrote:
...
> There are two things here:
> 1. make systemd journal persistent
> 2. avoid duplicate logs from rsyslog
>
> Why not just do '1' and
Hello,
Le 17/01/2017 à 21:46, Bryan Quigley a écrit :
> On Thu, Jan 12, 2017 at 11:20 AM, Jamie Strandboge
> wrote:
> ...
>> > There are two things here:
>> > 1. make systemd journal persistent
>> > 2. avoid duplicate logs from rsyslog
>> >
>> > Why not just do '1' and let rsyslog remain? The st
On Thu, Jan 12, 2017 at 11:20 AM, Jamie Strandboge wrote:
...
> There are two things here:
> 1. make systemd journal persistent
> 2. avoid duplicate logs from rsyslog
>
> Why not just do '1' and let rsyslog remain? The standard logs are rotated so
> this shouldn't be overly burdensome. Have you me
Jamie Strandboge schreef op 12-01-2017 17:20:
Why not just do '1' and let rsyslog remain? The standard logs are
rotated so
this shouldn't be overly burdensome. Have you measured how much the
duplicate
logs would take on a typical system?
Personally I think the suggestion to remove rsyslog is
Bryan Quigley schreef op 12-01-2017 16:50:
We could explicitly keep rsyslog supported in main for at least 18.04
for the for those who need it (or indefinitely if we find it's still
needed for remote enterprise logging). I was thinking that we might
have to keep it in main until 18.04 anyway fo
or make an option on an realy slow PC, to turn it off. Or automatic.
Measure boot time and decide...
On Thu, Jan 12, 2017 at 6:20 PM, Jamie Strandboge
wrote:
> On Thu, 2017-01-12 at 10:50 -0500, Bryan Quigley wrote:
> > We could explicitly keep rsyslog supported in main for at least 18.04
> > fo
On Thu, 2017-01-12 at 10:50 -0500, Bryan Quigley wrote:
> We could explicitly keep rsyslog supported in main for at least 18.04
> for the for those who need it (or indefinitely if we find it's still
> needed for remote enterprise logging). I was thinking that we might
> have to keep it in main un
On Tue, Jan 10, 2017 at 7:07 PM, Jeremy Bicha wrote:
> On 10 January 2017 at 17:04, Bryan Quigley
> wrote:
>> I'm sure I missed some positives/negatives. Thoughts on doing this for
>> Zesty?
>
> We would need to install gnome-logs instead of gnome-system-log on
> Ubuntu Desktop.
Indeed. Nic
We could explicitly keep rsyslog supported in main for at least 18.04
for the for those who need it (or indefinitely if we find it's still
needed for remote enterprise logging). I was thinking that we might
have to keep it in main until 18.04 anyway for upgrades.
Kind regards,
Bryan
On Wed, Ja
On Wed, 2017-01-11 at 08:29 +0100, Martin Pitt wrote:
> Jamie Strandboge [2017-01-10 16:27 -0600]:
> >
> > Remote logging. Rsyslog is far superior in this regard. Granted, remote
> > logging
> > is not enabled by default but it is a requirement in many environments.
> The systemd-journal-remote pa
Jamie Strandboge [2017-01-10 16:27 -0600]:
> Remote logging. Rsyslog is far superior in this regard. Granted, remote
> logging
> is not enabled by default but it is a requirement in many environments.
The systemd-journal-remote package does provide the necessary tools and is
reasonably flexible (
> From: ubuntu-devel-boun...@lists.ubuntu.com [mailto:ubuntu-devel-
>
> Jamie Strandboge [2017-01-10 16:27 -0600]:
> > Remote logging. Rsyslog is far superior in this regard. Granted,
> remote logging
> > is not enabled by default but it is a requirement in many
> environments.
>
> The systemd-jour
On Tue, 2017-01-10 at 17:04 -0500, Bryan Quigley wrote:
> Hi,
>
> In debugging a shutdown issue I came across a bug [1] that indicates
> for us to get better logs [2] during shutdown we really need to make
> the systemd journal persistent. We would also need to remove rsyslog
> by default so we
13 matches
Mail list logo
