[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [PATCH 3/3] zcip: add an option to force logging to syslog even if running -f
From:       Xabier Oneca  --  xOneca <xoneca () gmail ! com>
Date:       2014-10-31 20:20:14
Message-ID: CACkgH70PpyH-XLjASgWJTQ+1bOroXbYsKDOxZKBgevs9za-_4A () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


El 30/10/2014 16:30, "Isaac Dunham" <ibid.ag@gmail.com> escribi=C3=B3:
>
> 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

I was thinking in the same approach! 'logger' should do the trick. For this
and other daemons.

If this patch is to be approved, as Denys said, other daemons should mirror
the same behaviour...

Cheers,

Xabier Oneca_,,_

[Attachment #5 (text/html)]

<p dir="ltr">El 30/10/2014 16:30, &quot;Isaac Dunham&quot; &lt;<a \
href="mailto:ibid.ag@gmail.com">ibid.ag@gmail.com</a>&gt; escribió:<br> &gt;<br>
&gt; On Thu, Oct 30, 2014 at 04:15:13PM +0100, Stam, Michel [FINT] wrote:<br>
&gt; &gt; Hello Denys,<br>
&gt; &gt;<br>
&gt; &gt; I&#39;m not sure what you mean with every daemon?<br>
&gt; &gt;<br>
&gt; &gt; 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.<br> &gt; &gt;<br>
&gt; &gt; 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.<br> &gt;<br>
&gt; Is there a reason that this sort of command line wouldn&#39;t work:<br>
&gt;<br>
&gt;   zcip -f -r $RANGE 2&gt;&amp;1 |logger -t zcip<br>
&gt;<br>
&gt; ?<br>
&gt; &gt;<br>
&gt; &gt; Best regards,<br>
&gt; &gt;<br>
&gt; &gt; Michel Stam<br>
&gt; &gt; Embedded System Engineer</p>
<p dir="ltr">I was thinking in the same approach! &#39;logger&#39; should do the \
trick. For this and other daemons.</p> <p dir="ltr">If this patch is to be approved, \
as Denys said, other daemons should mirror the same behaviour...</p> <p \
dir="ltr">Cheers,</p> <p dir="ltr">Xabier Oneca_,,_</p>



_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

[prev in list] [next in list] [prev in thread] [next in thread]