Bug 790684 - rsyslog should be using portreserve
rsyslog should be using portreserve
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rsyslog (Show other bugs)
6.2
Unspecified Unspecified
high Severity medium
: rc
: ---
Assigned To: Tomas Heinrich
BaseOS QE Security Team
:
Depends On:
Blocks: 103401
  Show dependency treegraph
 
Reported: 2012-02-15 02:56 EST by Karel Srot
Modified: 2016-09-20 00:50 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-15 08:40:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Karel Srot 2012-02-15 02:56:16 EST
To avoid port conflicts with services such as CUPS or IMAP 
rsyslog
should be using portreserve for reserving respective ports
within range 600 - 1023.

rsyslog (with RFC3195 Input Module  601/tcp # Reliable Syslog Service)

Typical changes required:

Given a SysV service package that uses a particular port, (say, krb5_prop/tcp -
754):

1) Create a file named after the service, for example 'krb5_prop', which
contains:

krb5_prop/tcp

2) In the spec, install this file in /etc/portreserve, i.e.,
/etc/portreserve/krb5_prop

3) In the spec, add 'Requires: portreserve' to the package that provides the
server.

4) In the init script, in the start() stanza, add:

    [ -x /sbin/portrelease ] && /sbin/portrelease krb5_prop &>/dev/null || :

before starting the daemon.


Some background can be found in bug 103401.
Comment 2 Tomas Heinrich 2012-02-15 08:40:50 EST
The im3195 module is not included in the current package, so this is probably not needed.

Note You need to log in before you can comment on or make changes to this bug.