Vojtěch Hurčík via Nut-upsuser
writes:
> Thanks for the reply, it's only reported once per spawned process and
> what you say makes perfect sense in this light. A configuration toggle
> or environment variable also seems like a good idea, but I'm sure I or
> we can also live with the message
Thanks for the reply, it's only reported once per spawned process and what you
say makes perfect sense in this light. A configuration toggle or environment
variable also seems like a good idea, but I'm sure I or we can also live with
the message being reported once per process as it currently
Would this help?
https://github.com/networkupstools/nut/pull/2136
Jim
On Sun, Oct 29, 2023 at 5:04 PM Vojtěch Hurčík wrote:
> Thanks for the reply, it's only reported once per spawned process and what
> you say makes perfect sense in this light. A configuration toggle or
> environment
Thanks for your concern.
Technically, it is not about just systemd - other systems where launched
processes that have ways to interact with some OS framework (like SMF,
upstart, Windows services, docker/kubernetes, whatever) *and* such
framework offers ways for services to inform they have
Hello friends!
With the upcoming NUT release there is one thing I would like to ask:
-
no notification tech defined, will not spam more about
I am repeatedly getting these messages in my syslog more recently because I do
not have systemd available to me on my distribution and also do not want
