[zeromq-dev] zyre log is /var/log/syslog
Juergen Gnoss
jgnoss at hotmail.com
Fri Jan 1 16:49:58 CET 2021
that was a very quick response for the first question of 2021
Thanks Luca,
does exact what I wanted.
And a happy new Year to all of you guys.
You did a really great job and I really enjoy using zmq.
ju
________________________________
From: zeromq-dev <zeromq-dev-bounces at lists.zeromq.org> on behalf of Luca Boccassi <luca.boccassi at gmail.com>
Sent: Friday, January 1, 2021 10:28 AM
To: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
Subject: Re: [zeromq-dev] zyre log is /var/log/syslog
On Fri, 1 Jan 2021 at 15:22, Juergen Gnoss <jgnoss at hotmail.com> wrote:
>
> I'm writing software for a mobile datalogger.
> The device collects data and occasionally passes "WIFI stations" where the data get downloaded.
> I'm using zyre for service discovery.
> The program gets started on boot by systemd
>
> The system works great so far, if it gets a wifi connection, zyre discovers the service on the server
> and the program starts downloading data.
>
> What bothers me, is zyres log messages to syslog and daemon log while not having a wifi connction.
> Since system runs from a SD-Card I would like to get rid of that obvious log messages.
>
> if not connected by wifi, every second a
>
> Jan 1 15:02:59 loc rpi_zHB[6685]: D: 21-01-01 15:02:59 zbeacon: failed to transmit, attempting reconnection. reason=invalid socket
>
> in syslog and in daemon log
>
> I've tried to silence it by putting
>
> StandardError=/dev/null
> StandardOutput=/dev/null
>
> in systemd's unit file for the service, but it didn't help
>
> Any suggestions?
>
> Ju
zsys_set_logstream(NULL);
zsys_set_logsystem(false);
The former for stdout/stderr, the latter for syslog
_______________________________________________
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20210101/ded26791/attachment.htm>
More information about the zeromq-dev
mailing list