[PATCH 3/3] zcip: add an option to force logging to syslog even if running -f

Stam, Michel [FINT] M.Stam at fugro.nl
Thu Oct 30 15:34:56 UTC 2014


Hey Isaac,

No, technically there's no reason why that would not work, although i
suddenly have 2 processes to do the work of one process.

I could rework my patch to send logging to both stderr and syslog, if
that works better? 

Kind regards,
Fugro Intersite B.V.

Michel Stam
Embedded System Engineer
-----Original Message-----
From: Isaac Dunham [mailto:ibid.ag at gmail.com] 
Sent: Thursday, October 30, 2014 16:30 PM
To: Stam, Michel [FINT]
Cc: Denys Vlasenko; busybox
Subject: Re: [PATCH 3/3] zcip: add an option to force logging to syslog
even if running -f

On Thu, Oct 30, 2014 at 04:15:13PM +0100, Stam, Michel [FINT] wrote:
> Hello Denys,
> 
> I'm not sure what you mean with every daemon?
> 
> In this particular case, I did not see much from zcip, as it was being
executed from OpenWRT procd. This init program expects programs to run
in the foreground, and when they exit, it automatically restarts them.
Sortof a watchdog, if you will.
> 
> Unfortunately, if zcip runs in the foreground, it will not log
anything to syslog anymore, instead sending everything to stderr. This
patch allows to change that behaviour.

Is there a reason that this sort of command line wouldn't work:

 zcip -f -r $RANGE 2>&1 |logger -t zcip

?
> 
> Best regards, 
> 
> Michel Stam
> Embedded System Engineer

Thanks,
Isaac Dunham


More information about the busybox mailing list