On 12/05/2013 01:48, Pablo Neira Ayuso wrote: > On Sat, May 11, 2013 at 09:27:31PM +0100, Chris Boot wrote: > [...] >> Hi Pablo, >> >> I'd argue exactly the opposite point: that when you want multiple >> instances a PID file can help you work out which is which. > That new option may break existing setups with multiple instances. My patch explicitly doesn't change the behaviour of existing configurations. If you don't pass '--pidfile /path/to/file.pid', no pid file is written and there is no change in how ulogd works. >> My patch adds an option that takes a filename argument, so two >> instances can write to two different PID files; grepping ps won't >> easily tell you which instance is the correct one (without resorting >> to grepping for command-line arguments). > You can use pidof. Many other debian init scripts use it to obtain the > process PID. /usr/sbin/ulogd -d -c /etc/ulog/instance1.conf pidof ulogd > /run/ulog/instance1.pid # => 1234 /usr/sbin/ulogd -d -c /etc/ulog/instance2.conf pidof ulogd > /run/ulog/instance2.pid # => 1234 2345 The second pidof will list the pids of both instances of ulogd on the system. Without looking at all of the other pid files for other instances, how does it know which one was the one it just started? Chris -- Chris Boot bootc@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
