Hi David,
I understand what you're saying and you are right that there can be a
lot of problems (e.g. hangs) due logging. Some comments below.
On Sat, Mar 11 2017, David Lang wrote:
> On Sat, 11 Mar 2017, Michal Sojka wrote:
>
>> On Sat, Mar 11 2017, John Crispin wrote:
>>> On 11/03/17 01:48, Mic
On Sat, Mar 11 2017, Michal Sojka wrote:
> On Sat, Mar 11 2017, John Crispin wrote:
>> On 11/03/17 01:48, Michal Sojka wrote:
>>> When procd starts a rcS script, it captures its stdout and stderr and
>>> logs them to syslog. It could happen (and I don't know exactly why),
>>> that a rcS scripts pro
On Sat, 11 Mar 2017, Michal Sojka wrote:
On Sat, Mar 11 2017, John Crispin wrote:
On 11/03/17 01:48, Michal Sojka wrote:
When procd starts a rcS script, it captures its stdout and stderr and
logs them to syslog. It could happen (and I don't know exactly why),
that a rcS scripts produces some o
On Sat, Mar 11 2017, John Crispin wrote:
> On 11/03/17 01:48, Michal Sojka wrote:
>> When procd starts a rcS script, it captures its stdout and stderr and
>> logs them to syslog. It could happen (and I don't know exactly why),
>> that a rcS scripts produces some output before openlog() is called in
On 11/03/17 01:48, Michal Sojka wrote:
When procd starts a rcS script, it captures its stdout and stderr and
logs them to syslog. It could happen (and I don't know exactly why),
that a rcS scripts produces some output before openlog() is called in
procd. The result is that all subsequent logs f
When procd starts a rcS script, it captures its stdout and stderr and
logs them to syslog. It could happen (and I don't know exactly why),
that a rcS scripts produces some output before openlog() is called in
procd. The result is that all subsequent logs from procd are logged
with ident and PID of
