Bug 1048010

Summary:	Bug 1010648 follow-up: make sure system logs are not spammed due to "journalctl has --system switch" internal-only check
Product:	[Fedora] Fedora	Reporter:	Jan Pokorný [poki] <jpokorny>
Component:	abrt	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	abrt-devel-list, dvlasenk, iprikryl, jfilak, mmilata, mtoman
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 19:49:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1010648
Bug Blocks:

Description Jan Pokorný [poki] 2014-01-02 21:34:00 UTC

... as, e.g., F19 apparently lacks "journalctl --system", with
a consequence of line like these being logged into /var/log/messages
(in my fairly default setup):

> abrt-server[11988]: journalctl: unrecognized option '--system

Looks like correct [*] solution is something like this:

--- ccpp_event.conf.orig	2014-01-02 22:22:51.942394535 +0100
+++ ccpp_event.conf	2014-01-02 22:23:09.056391580 +0100
@@ -30,7 +30,7 @@
             executable=`cat executable` &&
             base_executable=${executable##*/} &&
             # Test if the current version of journalctl has --system switch
-            journalctl --system -n1 >/dev/null
+            journalctl --system -n1 &>/dev/null
             if [ $? -ne 0 ];
             then
                 # It's not an error if /var/log/messages isn't readable:


[*] beside following "journalctl --version", help screen as suggested by
    [bug 1035359] reporter, or something like this

Comment 1 Jan Pokorný [poki] 2014-01-02 21:39:59 UTC

Real-world example:
https://bugzilla.redhat.com/show_bug.cgi?id=893724#c15

Comment 2 Fedora End Of Life 2015-01-09 20:59:40 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 19:49:41 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.