Am 23.09.2014 um 19:41 schrieb Jóhann B. Guðmundsson:
> On 09/23/2014 04:15 PM, Przemek Klosowski wrote:
>> On 09/22/2014 12:53 PM, DJ Delorie wrote:
For the journal you always keep all log history in it's original
state
>>> On low-bandwidth systems, like laptops or diskless nodes, it's
On 09/23/2014 04:15 PM, Przemek Klosowski wrote:
On 09/22/2014 12:53 PM, DJ Delorie wrote:
For the journal you always keep all log history in it's original
state
On low-bandwidth systems, like laptops or diskless nodes, it's a
performance hit to generate the log entry in the first place. It's
On 09/22/2014 12:53 PM, DJ Delorie wrote:
For the journal you always keep all log history in it's original
state
On low-bandwidth systems, like laptops or diskless nodes, it's a
performance hit to generate the log entry in the first place. It's
really important to be able to configure the syste
Seriously, both of you: this back and forth (and particularly the personal
squabbling!) do not help us with Fedora development, which is what this list
is for. If there's a problem somewhere here which we can address, let's talk
about technical problems and solutions. Or if there are upstream issue
what
you quote or at least read it before strip, not that nobody
can read the whole post but your quoting style is abusive
BTW. you still refuse to understand that produce that lot
of messages *is wrong* in *non-debugging* mode
Weitergeleitete Nachricht
Betreff: Re: [systemd-dev
Am 22.09.2014 um 21:00 schrieb Jóhann B. Guðmundsson:
> On 09/22/2014 06:17 PM, Reindl Harald wrote:
>> # Log systemd-logind to /var/log/secure
>> :programname, isequal, "systemd-logind" -/var/log/secure
>> :programname, isequal, "systemd-logind" stop
>> :msg, contains, "Starting Sessi
On 09/22/2014 06:17 PM, Reindl Harald wrote:
# Log systemd-logind to /var/log/secure
:programname, isequal, "systemd-logind" -/var/log/secure
:programname, isequal, "systemd-logind" stop
:msg, contains, "Starting Session" stop
:msg, contains, "Started Session" stop
:msg, contains, "S
On 09/22/2014 04:53 PM, DJ Delorie wrote:
For the journal you always keep all log history in it's original
state
On low-bandwidth systems, like laptops or diskless nodes, it's a
performance hit to generate the log entry in the first place. It's
really important to be able to configure the syst
Am 22.09.2014 um 19:51 schrieb Reindl Harald:
> Am 22.09.2014 um 19:37 schrieb Jóhann B. Guðmundsson:
>>
>> On 09/22/2014 04:35 PM, Miloslav Trmač wrote:
> For example if you want to see just error messages in the journal you
> use "journalctl -p 3" or "journalctl -b -p 3" if you want it
Am 22.09.2014 um 19:37 schrieb Jóhann B. Guðmundsson:
>
> On 09/22/2014 04:35 PM, Miloslav Trmač wrote:
>>> >For example if you want to see just error messages in the journal you
>>> >use "journalctl -p 3" or "journalctl -b -p 3" if you want it only from
>>> >last boot ( add boot id if you want
On 09/22/2014 04:35 PM, Miloslav Trmač wrote:
>For example if you want to see just error messages in the journal you
>use "journalctl -p 3" or "journalctl -b -p 3" if you want it only from
>last boot ( add boot id if you want to from specific boot ) or you add
>"journalctl -b -p 3 -u httpd.ser
Please avoid cross-posting in the middle of a thread without contextualization.
Regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> For the journal you always keep all log history in it's original
> state
On low-bandwidth systems, like laptops or diskless nodes, it's a
performance hit to generate the log entry in the first place. It's
really important to be able to configure the system to *generate* a
minimal amount of com
Am 22.09.2014 um 18:35 schrieb Miloslav Trmač:
> - Original Message -
>> For example if you want to see just error messages in the journal you
>> use "journalctl -p 3" or "journalctl -b -p 3" if you want it only from
>> last boot ( add boot id if you want to from specific boot ) or you ad
- Original Message -
> For example if you want to see just error messages in the journal you
> use "journalctl -p 3" or "journalctl -b -p 3" if you want it only from
> last boot ( add boot id if you want to from specific boot ) or you add
> "journalctl -b -p 3 -u httpd.service" if you wan
On 09/22/2014 02:25 PM, Miloslav Trmač wrote:
(stripping systemd-devel)
- Original Message -
>Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson:
> >This is simply untrue as "journalctl -o export" will show you.
>
>where is it in the message?
>the process is "systemd"
>
>how to dis
Am 22.09.2014 um 17:18 schrieb Sérgio Basto:
> On Seg, 2014-09-22 at 17:00 +0200, Reindl Harald wrote:
>>
>> Am 22.09.2014 um 16:48 schrieb Sérgio Basto:
>>> On Seg, 2014-09-22 at 16:08 +0200, Reindl Harald wrote:
no you refuse to understand that *nobody* wants to split
out *all* syste
On Seg, 2014-09-22 at 17:00 +0200, Reindl Harald wrote:
>
> Am 22.09.2014 um 16:48 schrieb Sérgio Basto:
> > On Seg, 2014-09-22 at 16:08 +0200, Reindl Harald wrote:
> >> no you refuse to understand that *nobody* wants to split
> >> out *all* systemd logs because just the excessive *user
> >> sess
Am 22.09.2014 um 16:48 schrieb Sérgio Basto:
> On Seg, 2014-09-22 at 16:08 +0200, Reindl Harald wrote:
>> no you refuse to understand that *nobody* wants to split
>> out *all* systemd logs because just the excessive *user
>> session* logging and that this messages should not exist
>> at all in a
On Seg, 2014-09-22 at 16:08 +0200, Reindl Harald wrote:
> no you refuse to understand that *nobody* wants to split
> out *all* systemd logs because just the excessive *user
> session* logging and that this messages should not exist
> at all in a non-debugging environment
IIUC , this messages doesn
Am 22.09.2014 um 16:25 schrieb Miloslav Trmač:
> (stripping systemd-devel)
>
> - Original Message -
>> Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson:
>>> This is simply untrue as "journalctl -o export" will show you.
>>
>> where is it in the message?
>> the process is "systemd"
>>
(stripping systemd-devel)
- Original Message -
> Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson:
> > This is simply untrue as "journalctl -o export" will show you.
>
> where is it in the message?
> the process is "systemd"
>
> how to distinct between user sessions and systemn boot?
Am 22.09.2014 um 15:55 schrieb Jóhann B. Guðmundsson:
> On 09/22/2014 12:58 PM, Reindl Harald wrote:
>> i suggest you get rid of that arrogance and some other developers
>> too because it's the reason for the subject and proves that you
>> *do not* care about users as long you have not the same o
On 09/22/2014 12:58 PM, Reindl Harald wrote:
i suggest you get rid of that arrogance and some other developers
too because it's the reason for the subject and proves that you
*do not* care about users as long you have not the same opinion
you are the one demanding a friendly tone from me, well
Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson:
>>> > Then file a bug report against rsyslog and provide a patch which fixes
>>> > the default log filtering in Fedora to your expectation but leave
>>> > systemd out of it.
>> wow - in any other case the systemd developers saying that
>> the
25 matches
Mail list logo
