> > I have attached debug info both when PrivDropTo is enabled and > > disabled. > > Only difference I can see is the 5 minutes it takes for the > > PrivDropTo_enabled run to timeout (motherproccess dies and > > childproccess > > thereby gets owned by init)... > > Ah, it looks like you use auto-backgrounding (which is the default due > to > historical reasons). You can disable that via -n. I don't know if the > init > script expects auto-backgrounding or not...
I should add: if auto-backgrounding is used, the parent process is just a shim to start the actual instance (the child). It then waits some time on the child until it is sure it has started (I haven't visited that code for many years...). So it is expected that the parent terminates after a while (and I think-but do not know right now- that this may take some minutes). Suggest: try without auto-backgrouning so that we know if the problem is related to that Feature. rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/
