Hi Didier,
Didier Kryn writes:
> Le 24/10/2018 à 13:34, Olaf Meeuwissen a écrit:
>> Of these, rsyslog is installed by default, at least on ascii. If you
>> could assume rsyslog is always installed, binding the daemon's stdout
>> and stderr to /dev/log would work fine too.
>
> Not that simple.
On Wed, 24 Oct 2018 11:42:36 +0200
Didier Kryn wrote:
> I can't see how to do better than logger. The only limitation is
> inherent to the very principle of redirecting stderr: the level is
> the same for all messages because it is passed in the logger command
> line. Instead, a daemon
Le 24/10/2018 à 13:34, Olaf Meeuwissen a écrit :
Of these, rsyslog is installed by default, at least on ascii. If you
could assume rsyslog is always installed, binding the daemon's stdout
and stderr to /dev/log would work fine too.
Not that simple. There's the risk of several processes
On Wed, Oct 24, 2018 at 08:34:19PM +0900, Olaf Meeuwissen wrote:
[cut]
> >
> > If a daemon is not doing its syslog proper calls, redirecting the
> > stdout and stderr to logger could make sense (but a deamon is normally
> > expected to close stdout and stderr as soon as it is spawned, and use
>
Hi,
KatolaZ writes:
> On Tue, Oct 23, 2018 at 12:32:54PM -0400, Steve Litt wrote:
>
> [cut]
>
>> Ahh, the preceding explains why G. Pape says runit level logs are
>> required on *some* daemons, but not others. If the daemon already
>> performs meaningful syslog() calls, there's no reason for
Le 23/10/2018 à 18:32, Steve Litt a écrit :
On Tue, 23 Oct 2018 11:06:52 +0200
Didier Kryn wrote:
Logger is a way to redirect to syslog one of the output paths of
an application, by the mean of a pipe, or for a script to send such
messages. Logger reads messages and sends them by
On Tue, Oct 23, 2018 at 12:32:54PM -0400, Steve Litt wrote:
[cut]
>
> Ahh, the preceding explains why G. Pape says runit level logs are
> required on *some* daemons, but not others. If the daemon already
> performs meaningful syslog() calls, there's no reason for further
> logging. The logger
On Tue, 23 Oct 2018 11:06:52 +0200
Didier Kryn wrote:
> Logger is a way to redirect to syslog one of the output paths of
> an application, by the mean of a pipe, or for a script to send such
> messages. Logger reads messages and sends them by invoking the
> syslog() function. If you force
On 2018年10月23日 18:44:25 JST, Didier Kryn wrote:
>Le 23/10/2018 à 11:21, Stephan Seitz a écrit :
>> On Di, Okt 23, 2018 at 11:06:52 +0200, Didier Kryn wrote:
>>> syslog() is a member of the C library which allows any
>>> application to send messages to the system logging facility, through
>
Le 23/10/2018 à 11:21, Stephan Seitz a écrit :
On Di, Okt 23, 2018 at 11:06:52 +0200, Didier Kryn wrote:
syslog() is a member of the C library which allows any
application to send messages to the system logging facility, through
the socket /var/log/syslog and some lock mechanism (probably
Le 23/10/2018 à 05:58, mett a écrit :
Hi,
by the way, what do u think about
what is written on that page regarding
logging?
http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.html
The fan-in/fan-out argument is an issue if you send massive amounts
of data to syslog(). In this
On Di, Okt 23, 2018 at 11:06:52 +0200, Didier Kryn wrote:
syslog() is a member of the C library which allows any application
to send messages to the system logging facility, through the socket
/var/log/syslog and some lock mechanism (probably using a semaphore) to
I think you mean
Quoting Didier Kryn (k...@in2p3.fr):
> syslog() is a member of the C library which allows any
> application to send messages to the system logging facility, through
> the socket /var/log/syslog and some lock mechanism (probably using a
> semaphore) to prevent two applications to write in the
Le 23/10/2018 à 09:23, Steve Litt a écrit :
Just to be simple and clear:
syslog() is a member of the C library which allows any application
to send messages to the system logging facility, through the socket
/var/log/syslog and some lock mechanism (probably using a semaphore) to
On Tue, 23 Oct 2018 06:49:56 +0200
KatolaZ wrote:
> On Mon, Oct 22, 2018 at 04:59:16PM -0400, Steve Litt wrote:
>
> [cut]
>
> >
> > Hi Daniel,
> >
> > You were so thorough giving facts that I didn't understand your
> > answer: Would you recommend using logger to transfer daemon stderr
> >
Quoting mett (m...@pmars.jp):
> by the way, what do u think about
> what is written on that page regarding
> logging?
>
> http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.html
>
> I was thinking if there is a better
> way of logging, might be worth to try it.
You asked the above of
On Mon, Oct 22, 2018 at 04:59:16PM -0400, Steve Litt wrote:
[cut]
>
> Hi Daniel,
>
> You were so thorough giving facts that I didn't understand your answer:
> Would you recommend using logger to transfer daemon stderr (and
> configurationally stdout) to the log files?
>
> You appeared (to me)
On 2018年10月23日 9:10:59 JST, wirelessd...@gmail.com wrote:
>On Tue, 23 Oct 2018 at 07:37, Rick Moen wrote:
>> The mainstream choices (disregarding journald) in 2018 are rsyslog
>and
>> syslog-ng, period. A case could be made for either. I _think_
>> rsyslog remains more common. I've personally
On Tue, 23 Oct 2018 at 07:37, Rick Moen wrote:
> The mainstream choices (disregarding journald) in 2018 are rsyslog and
> syslog-ng, period. A case could be made for either. I _think_
> rsyslog remains more common. I've personally only encountered
> syslog-ng in embedded logging appliances
On 22/10/2018 21:59, Steve Litt wrote:
> On Mon, 22 Oct 2018 20:08:57 +
> Daniel Abrecht wrote:
>
>> On 22/10/2018 19.38, Steve Litt wrote:
>>> Is logger just another sister of syslog-ng and rsyslog?
>>
Snip [Edited for brevity]
>
> Hi Daniel,
>
> You were so thorough giving facts that I
On Mon, 22 Oct 2018 20:08:57 +
Daniel Abrecht wrote:
> On 22/10/2018 19.38, Steve Litt wrote:
> > Is logger just another sister of syslog-ng and rsyslog?
>
>
> logger does per default log to the system logger. That can be
> rsyslog, syslog-ng, or any other system syslog daemon, really
Quoting Steve Litt (sl...@troubleshooters.com):
> Is logger just another sister of syslog-ng and rsyslog?
If we're talking about the same 'logger' tool, then no:
The Linux logger command provides an easy way to add log files to
/var/log/syslog — from the command line, from scripts, or
On 22/10/2018 19.38, Steve Litt wrote:
Is logger just another sister of syslog-ng and rsyslog?
logger does per default log to the system logger. That can be rsyslog,
syslog-ng, or any other system syslog daemon, really (with the exception
of journald, which does it's own thing.). This is
On Mon, 22 Oct 2018 11:23:09 +0200
KatolaZ wrote:
> On Mon, Oct 22, 2018 at 11:16:30AM +0200, Didier Kryn wrote:
> > Le 21/10/2018 à 20:18, Steve Litt a écrit :
> > > Hi all,
> > >
> > > With runit, you can either use the "runit way" of recording log
> > > files, in which one looks in the
You can use runit's own svlogd [1] and redirect everything to syslogd.
__
[1] http://smarden.org/runit/svlogd.8.html
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
On Mon, Oct 22, 2018 at 11:16:30AM +0200, Didier Kryn wrote:
> Le 21/10/2018 à 20:18, Steve Litt a écrit :
> > Hi all,
> >
> > With runit, you can either use the "runit way" of recording log files,
> > in which one looks in the daemon's run directory for something
> > called .main, or you can use
Le 21/10/2018 à 20:18, Steve Litt a écrit :
Hi all,
With runit, you can either use the "runit way" of recording log files,
in which one looks in the daemon's run directory for something
called .main, or you can use one of several logging programs. I'm using
logger, and a Devuan ASCII VM guest I
Hi all,
With runit, you can either use the "runit way" of recording log files,
in which one looks in the daemon's run directory for something
called .main, or you can use one of several logging programs. I'm using
logger, and a Devuan ASCII VM guest I downloaded has the logger program
and I
28 matches
Mail list logo
