Bug 16694 - Shorewall on a systemd
Summary: Shorewall on a systemd
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-03 15:54 CEST by Meg Skywalker
Modified: 2016-11-03 11:39 CET (History)
1 user (show)

See Also:
Source RPM: shorewall-4.6.3.4-2.mga5.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Meg Skywalker 2015-09-03 15:54:58 CEST 
Description of problem:
Using the administration tool for shorewall seems not working proper on a systemd system.
It tried to read /var/log/messages, which isn't existing/used anymore.
So every (tested) command only produce the following output:
   ERROR: LOGFILE (/var/log/messages) does not exist!



Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2015-09-03 20:28:48 CEST 
You need to install rsyslog to have a /var/log/messages file, it's not installed by default anymore.  It would be nice if shorewall could read the systemd journal instead.  Maybe support for this has been added in a newer version, or is available but we haven't enabled it?  It'd be nice if someone could look into that.
Comment 2 Marja Van Waes 2016-11-03 11:39:58 CET 
(In reply to David Walser from comment #1)
> It would be nice if shorewall could read the
> systemd journal instead.  Maybe support for this has been added in a newer
> version, or is available but we haven't enabled it?  It'd be nice if someone
> could look into that.

Assigning to all packagers collectively, since shorewall has no registered maintainer.

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs
Note You need to log in before you can comment on or make changes to this bug.