<div dir="ltr">Would this help?<br><br><div><a href="https://github.com/networkupstools/nut/pull/2136">https://github.com/networkupstools/nut/pull/2136</a></div><div><br></div><div>Jim<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Oct 29, 2023 at 5:04 PM Vojtěch Hurčík <<a href="mailto:vojhu87@proton.me">vojhu87@proton.me</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:Arial,sans-serif;font-size:14px">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 is... looking forward to the stable release & thanks for everything!</div><div style="font-family:Arial,sans-serif;font-size:14px"><br></div><div style="font-family:Arial,sans-serif;font-size:14px">VH</div>
<div style="font-family:Arial,sans-serif;font-size:14px"><br></div><div>
------- Original Message -------<br>
On Sunday, October 29th, 2023 at 16:22, Jim Klimov <<a href="mailto:jimklimov%2Bnut@gmail.com" target="_blank">jimklimov+nut@gmail.com</a>> wrote:<br><br>
<blockquote type="cite">
<div dir="ltr"><div>Thanks for your concern.</div><div><br></div><div>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 started and e.g. dependencies can begin starting, with better precision than "we have forked off an init script and assume that this instant its service is fully ready".</div><div><br></div><div>One bit that worries me in your report is "I am repeatedly getting these messages in my <i>syslog</i>" - does it mean you get them more often than once per uptime of each daemon (upsd, upsmon, driver)? Or that you reboot so often that the "noise" gets your eyes sore? :)</div><div><br></div><div>I did initially have the opposite feedback in the beginning, about not having those notifications working and services set up for notification-based integration getting restarted by their OS framework because their
startup
allegedly timed out.</div><div><br></div><div>I think this sort of behaviors with OS-dependent variations was supposed to become managed by envvars (e.g. offering a toggle to not make noise easy to set in packaged init-scripts etc.) but it seems that for this particular case one was not merged. Something similar was discussed about NUT daemon banner and a few other lines emitted at startup, which some people see as important post-mortem tool when inspecting logs or console dumps, and others treat as noise ("unless there's an error, I want to see nothing") - and frankly both stances have their merits for different audiences.<br></div><div><br></div><div>Jim Klimov<br></div><div><br></div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Sun, Oct 29, 2023 at 2:45 PM Vojtěch Hurčík via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net" rel="noreferrer nofollow noopener" target="_blank">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div>Hello friends!</div><div style="font-family:Arial,sans-serif;font-size:14px;color:rgb(0,0,0);background-color:rgb(255,255,255)"><br></div><div style="font-family:Arial,sans-serif;font-size:14px;color:rgb(0,0,0);background-color:rgb(255,255,255)">With the upcoming NUT release there is one thing I would like to ask:</div><div style="font-family:Arial,sans-serif;font-size:14px;color:rgb(0,0,0);background-color:rgb(255,255,255)"><ul><li style="list-style-type:disc"><pre><span>no notification tech defined, will not spam more about</span></pre></li></ul><div>I am repeatedly getting these messages in my <i>syslog</i> more recently because I do not have <i>systemd</i> available to me on my distribution and also do not want to use it.<br></div><div><br></div><div>Maybe the debug level for such messages could be raised to 1 instead, as they still seem a bit too spammy for something us, who don't use the <i>systemd</i>, already know. At least then we would have a way to suppress them...<br></div><div><br></div><div><span>Vojtěch </span><br></div></div>_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" rel="noreferrer nofollow noopener" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a rel="noreferrer nofollow noopener" href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>
</blockquote><br>
</div></blockquote></div>