> logcheck → needs to be checked
It will break by this change.
I was not able to make it work on two machines. My system is cursed and
containers does not have such logs at all. Going to check on fresh VM.
However I was able to dive in the code and check how it works. It is
basically big collect
> I think it’s the responsibility of the proponents of the change to come up
> with a plan; the Change process was pretty much instituted exactly so that
> there actually *is* *some* plan for seeing through breaking changes.
Agreed, the proponents of the change must identify areas (packages)
which
2017-06-13 13:54 GMT+02:00 Roman Pavelka :
> > It does not inspire confidence that the person(s) proposing this Change
> understand the potential fallout.
> ...
> > what packages in Fedora parse the rsyslog output and make sure that they
> are capable of handling the change.
>
> Everyone is free
On Tue, Jun 13, 2017 at 2:33 PM, Reindl Harald wrote:
> i call your infrastructure scattered around the globe the minority of setups
This can be the case for Fedora but it would be not for CentOS and RHEL,
where this change should head in too.
> "there is a simple way to change the format if you
On Tue, Jun 13, 2017 at 2:18 PM, Reindl Harald wrote:
>> When some package will break because someone adjusted format of
>> timestamps, the bug is in that package and not in the rsyslog's format
>
> there is a world outside packages called user scripts
That is true. But here there is simple way t
Thanks, Stephen, I will update the "Benefit to Fedora" section.
> It does not inspire confidence that the person(s) proposing this Change
> understand the potential fallout.
...
> what packages in Fedora parse the rsyslog output and make sure that they are
> capable of handling the change.
Ev
IMHO it is exactly as Björn replied to you. Between 2010 and 2014 I was working
in aerospace where the exact time of an event is of the highest importance. In
this field there is deep understanding (based on several
hundreds-millions-dollars screwups) how much compliance to standards is
importa
Michael Catanzaro wrote:
> The downside, of course, is that the new format is much harder for a
> human to eyeball.
That's not a matter of course, it's a matter of what one is used to.
Dates are difficult to read in general because there is such a plethora
of date formats in use everywhere, many
On Fri, Jun 9, 2017 at 11:49 AM, Stephen Gallagher
wrote:
Compliance to international standard," is not useful as a metric to
determine
whether the disruption involved is worth making the change. Consider
instead a
statement along the lines of " "Matching the behavior of popular
distros X, Y
a
On 05/29/2017 09:22 AM, Jan Kurik wrote:
> = Proposed System Wide Change: Rsyslog log format change proposal =
> https://fedoraproject.org/wiki/Changes/RsyslogLogFormat
>
> Change owner(s):
> * Radovan Sroka
> * Roman Pavelka
>
> Currently Fedora uses RSYSLOG_TraditionalFileFormat as a default
Done. Thank you, Zbyszek!
Roman
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
What was deciding factor for us was "Complex system wide changes involve
system-wide defaults" in Changes/Policy. Also I consider system logging
facility system-wide important. And as another Bjorn replies below, there may
be packages dependent on current format.
Best regards
Roman
___
On Thu, Jun 01, 2017 at 07:53:09PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jun 01, 2017 at 01:03:43PM -0500, Jason L Tibbitts III wrote:
> > ZJ> That should not be a problem, but maybe this is tickling some bug in
> > ZJ> the journal code?
> >
> > That's what it feels like. I might be
On Thu, Jun 01, 2017 at 01:03:43PM -0500, Jason L Tibbitts III wrote:
> ZJ> That should not be a problem, but maybe this is tickling some bug in
> ZJ> the journal code?
>
> That's what it feels like. I might be able to hack something up where I
> force a journal rotation. Rotation of the journal
[I trimmed the CC list and changed the subject.]
> "ZJ" == Zbigniew Jędrzejewski-Szmek writes:
ZJ> IIUC, the code does a sleep loop, and does not use polling. So it's
ZJ> not particularly efficient, but it should work.
You are probably right; I had forgotten how I'd written it but I thought
On Wed, May 31, 2017 at 06:55:31PM -0500, Jason L Tibbitts III wrote:
> > "ZJ" == Zbigniew Jędrzejewski-Szmek writes:
>
> ZJ> I you post the code somewhere, I could have a look.
>
> It's in the upstream "journal" branch of the denyhosts source:
>
> https://github.com/denyhosts/denyhosts/tre
> "ZJ" == Zbigniew Jędrzejewski-Szmek writes:
ZJ> I you post the code somewhere, I could have a look.
It's in the upstream "journal" branch of the denyhosts source:
https://github.com/denyhosts/denyhosts/tree/journal
https://github.com/denyhosts/denyhosts/commit/d0d66a2890d50a460ecd20ee0b1
On Wed, May 31, 2017 at 02:15:21PM -0500, Jason L Tibbitts III wrote:
> > "TT" == Tomasz Torcz writes:
>
> TT> fail2ban works with journal. BTW, sshguard (which is similar to
> TT> fail2ban) works woth journal, too.
>
> Denyhosts doesn't use the journal, though I have a branch which does.
>
> "TT" == Tomasz Torcz writes:
TT> fail2ban works with journal. BTW, sshguard (which is similar to
TT> fail2ban) works woth journal, too.
Denyhosts doesn't use the journal, though I have a branch which does.
Sadly I never could figure out why iterating over a journal.Reader()
object will so
On Tue, May 30, 2017 at 10:37:02PM +0200, Till Maas wrote:
> On Mon, May 29, 2017 at 07:21:07PM +0200, Björn 'besser82' Esser wrote:
>
> > Does this qualify to be a system-wide change? To me this looks like a
> > self-contained change, since I don't see any other packages or processes in
> > need
On Tuesday, 30 May 2017 at 11:18, David Sommerseth wrote:
> On 29/05/17 23:18, Björn Persson wrote:
> > Björn 'besser82' Esser wrote:
> >> Does this qualify to be a system-wide change? To me this looks like
> >> a self-contained change, since I don't see any other packages or
> >> processes in nee
On Mon, May 29, 2017 at 07:21:07PM +0200, Björn 'besser82' Esser wrote:
> Does this qualify to be a system-wide change? To me this looks like a
> self-contained change, since I don't see any other packages or processes in
> need for adjustment, but rsyslog itself.
>
> Please correct me, if I'm m
On 29/05/17 23:18, Björn Persson wrote:
> Björn 'besser82' Esser wrote:
>> Does this qualify to be a system-wide change? To me this looks like
>> a self-contained change, since I don't see any other packages or
>> processes in need for adjustment, but rsyslog itself.
>
> I'll be surprised if ther
On Mon, May 29, 2017 at 03:22:56PM +0200, Jan Kurik wrote:
> = Proposed System Wide Change: Rsyslog log format change proposal =
> https://fedoraproject.org/wiki/Changes/RsyslogLogFormat
>
> Change owner(s):
> * Radovan Sroka
> * Roman Pavelka
>
> Currently Fedora uses RSYSLOG_TraditionalFileFo
Björn 'besser82' Esser wrote:
> Does this qualify to be a system-wide change? To me this looks like
> a self-contained change, since I don't see any other packages or
> processes in need for adjustment, but rsyslog itself.
I'll be surprised if there aren't any programs that parse the system
log a
Am 29.05.2017 um 15:22 schrieb Jan Kurik:
= Proposed System Wide Change: Rsyslog log format change proposal =
https://fedoraproject.org/wiki/Changes/RsyslogLogFormat
Change owner(s):
* Radovan Sroka
* Roman Pavelka
Currently Fedora uses RSYSLOG_TraditionalFileFormat as a default
format for ti
= Proposed System Wide Change: Rsyslog log format change proposal =
https://fedoraproject.org/wiki/Changes/RsyslogLogFormat
Change owner(s):
* Radovan Sroka
* Roman Pavelka
Currently Fedora uses RSYSLOG_TraditionalFileFormat as a default
format for timestamps in its logs. There is missing year
27 matches
Mail list logo