Ubuntu
syslog-ng package

No need to use $SYSLOGNG_OPTS in case of reload

Bug #678402 reported by Alexander Averyanov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
syslog-ng (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: syslog-ng

Ubuntu 10.04.1 LTS. syslog-ng version 3.1.2-1~lucid1 from backports.

I run syslog-ng in vps without 'capabilities' feature, so I uncomment $SYSLOGNG_OPTS in /etc/default/syslog-ng. And today got this report:
===
/etc/cron.daily/logrotate:
start-stop-daemon: unrecognized option '--no-caps'
Try 'start-stop-daemon --help' for more information.
invoke-rc.d: initscript syslog-ng, action "reload" failed.
error: error running non-shared postrotate script for /var/log/syslog of '/var/log/syslog '
run-parts: /etc/cron.daily/logrotate exited with return code 1
===

I removed $SYSLOGNG_OPTS from reload section of /etc/init.d/syslog-ng and now everything works fine.

Revision history for this message
Peter Czanik (pczanik) wrote :

Tested on Ubuntu 11.10 and it does not seem to be affected.

Gergely Nagy (algernon)
Changed in syslog-ng (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.