<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 4/10/22 20:45, Jim Klimov via
Nut-upsuser wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJYg8v+pHtciNsBQ-p2bbXQj3K4At+M2b_ck4pTdB5Qa21w9Xw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">I believe the code only deals with '\n' character
for line-breaks, in protocol and probably configs.
<div dir="auto"><br>
</div>
</div>
</blockquote>
<p>I've just thrown in a quick test: I converted upsmon.conf to dos
format and restarted upsmon. No complains AFAICS so I guess at
least upsmon ( and I guess the parser is the same for the other
apps ) accepts configs in CRLF format:<br>
</p>
<p><br>
</p>
<p>[wolfy@wolfy ~]$ sudo file /etc/ups/upsmon.conf <br>
/etc/ups/upsmon.conf: ASCII text, with CRLF line terminators<br>
</p>
<p>[wolfy@wolfy ~]$ sudo systemctl start nut-monitor<br>
Apr 10 21:33:45 wolfy systemd: Started Network UPS Tools - power
devices information server.<br>
Apr 10 21:33:45 wolfy systemd: Started Network UPS Tools - power
device monitor and shutdown controller.<br>
Apr 10 21:33:45 wolfy nut-server: fopen /var/run/nut/upsd.pid: No
such file or directory<br>
Apr 10 21:33:45 wolfy nut-server: Could not find PID file
'/var/run/nut/upsd.pid' to see if previous upsd instance is
already running!<br>
Apr 10 21:33:45 wolfy upsd[18311]: listening on 127.0.0.1 port
3493<br>
Apr 10 21:33:45 wolfy nut-server: listening on 127.0.0.1 port 3493<br>
Apr 10 21:33:45 wolfy nut-server: listening on ::1 port 3493<br>
Apr 10 21:33:45 wolfy upsd[18311]: listening on ::1 port 3493<br>
Apr 10 21:33:45 wolfy nut-server: Can't chdir to /var/run/nut: No
such file or directory<br>
Apr 10 21:33:45 wolfy nut-server: Network UPS Tools upsd 2.7.4.1<br>
Apr 10 21:33:45 wolfy upsd[18311]: Can't chdir to /var/run/nut: No
such file or directory<br>
Apr 10 21:33:45 wolfy nut-monitor: fopen /var/run/nut/upsmon.pid:
No such file or directory<br>
Apr 10 21:33:45 wolfy nut-monitor: Could not find PID file to see
if previous upsmon instance is already running!<br>
Apr 10 21:33:45 wolfy nut-monitor: UPS: ablerex@dell3 (primary)
(power value 1)<br>
Apr 10 21:33:45 wolfy nut-monitor: Using power down flag file
/etc/killpower</p>
<p><br>
</p>
<p><br>
</p>
<p>Please ignore the errors above, I am still fiddling with
packaging 2.8.0 and some things are not yet right. </p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAJYg8v+pHtciNsBQ-p2bbXQj3K4At+M2b_ck4pTdB5Qa21w9Xw@mail.gmail.com">
<div dir="auto">
<div dir="auto">Jim</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Apr 10, 2022, 19:26
Roger Price <<a href="mailto:roger@rogerprice.org"
moz-do-not-send="true" class="moz-txt-link-freetext">roger@rogerprice.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">The IETF
requires that the I-D contain an ABNF (Augmented Backus-Naur
Form) <br>
grammar of the NUT commands and responses. At the end of each
command, there is <br>
a NEWLINE character sequence. The IETF in RFC 5234 say that
NEWLINE is CRLF, <br>
carriage return + line feed, hex 0D0A.<br>
<br>
Is this true for NUT? The ISE editor requires me to document
what NUT does, not <br>
what the IETF propose. Does upsd accept all forms of NEWLINE
or only hex 0A?<br>
<br>
Roger</blockquote>
</div>
</blockquote>
<br>
</body>
</html>