Why does your module need to spawn the threads instead of using the worker
approach that rsyslog uses?
Are you running into the problem only when rsyslog is daemonized by the system
tools? or also when it's backgrounding itself when you run it manually?
David Lang
On Thu, 24 Mar 2016, Kane Kim wrote:
Our module spawns some threads on initialization and it can't work with
damonized rsyslog (only with rsyslog in foreground).
On Thu, Mar 24, 2016 at 2:41 PM, David Lang <[email protected]> wrote:
I'm pretty sure after. It needs to read it's config file first, and it
can't finish doing that until modules are loaded.
why?
David Lang
On Thu, 24 Mar 2016, Kane Kim wrote:
Does rsyslog fork/daemonize before loading plugins or after?
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
DON'T LIKE THAT.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
