Bug 483142

Summary:	app-admin/syslog-ng - init script should set absolute path to syslog-ng binary
Product:	Gentoo Linux	Reporter:	Stefano Takekawa <s.takekawa>
Component:	[OLD] Server	Assignee:	Mr. Bones. (RETIRED) <mr_bones_>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Stefano Takekawa 2013-08-31 12:34:36 UTC

When the PATH variable in specified in /etc/security/pam_env.con and it does not contain the path /usr/sbin/, the init script which starts syslog-ng fails:

# /etc/init.d/syslog-ng restart
 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...                                              [ ok ]
 * Starting syslog-ng ...
 * start-stop-daemon: failed to exec `syslog-ng': No such file or directory
 * start-stop-daemon: failed to start `syslog-ng'
 * Failed to start yslog-ng                                                                                 [ !! ]
 * ERROR: syslog-ng failed to start

That happens because the variable command is set to "syslog-ng" in the init script. With command="/usr/sbin/syslog-ng", the script starts correctly. app-admin/syslog-ng is version 3.4.2 (stable).


Reproducible: Always

Steps to Reproduce:
1. emerge =app-admin/syslog-ng-3.4.2
2. uncomment PATH variable in /etc/security/pam_env.conf
3. /etc/init.d/syslog-ng restart
Actual Results:  
/etc/init.d/syslog-ng does not start

Expected Results:  
/etc/init.d/syslog-ng should start

Only syslog-ng init script seems to be affected, all the others scripts/packages work well.

Comment 1 Mr. Bones. (RETIRED) gentoo-dev

2013-08-31 17:44:29 UTC

ok, updated the init script.  re-emerge syslog-ng if you're affected by this.