Files
meta-openembedded/meta-oe
Jagadeesh Krishnanjanappa 00d1d63e4f syslog-ng: provide correct PID directory location to restart/stop syslog-ng daemon
If "--with-pidfile-dir" configure option is not specified, then the syslog-ng
configure script assigns PID directory to /var/lib/syslog-ng; which is
where the PID file of syslog-ng process is created. But the syslog-ng
initscript (/etc/init.d/syslog-ng) uses /var/lib/syslog-ng/
as PID directory, this results in not stopping/restarting syslog-ng daemons
when it was requested to do so.

For example:
-- snip --
root@qemux86:~# /etc/init.d/syslog status
/usr/sbin/syslog-ng (pid 345 344) is running...
root@qemux86:~# /etc/init.d/syslog stop
Stopping syslog-ng:.
root@qemux86:~# /etc/init.d/syslog status
/usr/sbin/syslog-ng (pid 345 344) is running...
root@qemux86:~#
-- snip --

Hence set --with-pidfile-dir to "/var/run/syslog-ng", so that syslog-ng daemon
can be stopped/restarted via initscript.

Signed-off-by: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-08-13 13:19:00 +02:00
..
2017-08-13 13:16:18 +02:00
2017-07-24 18:58:54 +02:00
2017-07-14 23:44:33 +02:00

This layer depends on:

URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][PATCH'

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainer: Koen Kooi <koen@dominion.thruhere.net>
                       Martin Jansa <martin.jansa@gmail.com>