Guillaume Thouvenin f0ba5e5077 Avoid forks when starting hekad ... We must avoid to fork process when starting the Heka daemon because if we kill the wrapper, the Heka daemon is detached and re-attach to the init process. This can create several Heka daemon. To avoid this we need to use exec and avoid the usage of sudo. Fixes-bug: #1561109 Change-Id: Idbfab2de92b993d1e5124de5bff44c4b09a88bb4		2016-03-24 09:52:12 +01:00
..
decoder	Add a flag to messages received by the aggregator	2015-09-17 16:18:17 +02:00
encoder	Avoid indexing Uuid and EnvVersion fields	2016-01-04 14:46:29 +01:00
filter	Integrate collectd into the LMA collector	2015-03-13 12:01:47 +01:00
input	Add priority param to heka::input::logstreamer	2015-12-29 10:36:06 +01:00
output	Enable buffering for HTTP output plugins	2015-12-23 14:18:50 +01:00
splitter	Initial import of the LMA collector plugin	2015-02-27 14:16:49 +01:00
global.toml.erb	Add Heka params to set maximum message injection	2015-07-03 17:40:24 +02:00
hekad.initd.erb	Wait for rabbitmq before starting lma_collector	2015-04-22 14:36:51 +00:00
hekad.upstart.conf.erb	Avoid forks when starting hekad	2016-03-24 09:52:12 +01:00
hekad_wrapper.erb	Avoid forks when starting hekad	2016-03-24 09:52:12 +01:00
logrotate.conf.erb	Use copytruncate option for Heka log rotation	2015-04-08 11:48:47 +02:00