Re: [Nut-upsuser] NEWLINE

2022-04-10 Thread Roger Price
On Sun, 10 Apr 2022, Manuel Wolfshant wrote: On 4/10/22 20:45, Jim Klimov via Nut-upsuser wrote: I believe the code only deals with '\n' character for line-breaks, in protocol and probably configs.  I've just thrown in a quick test:  I converted upsmon.conf to dos format and restarted u

Re: [Nut-upsuser] NUT v2.8.0(-rc1)

2022-04-10 Thread Jim Klimov via Nut-upsuser
Note: There was an issue with original publication of the source tarball for rc2, so it was re-published on github releases and on nut website. On Sun, Apr 10, 2022, 16:40 Jim Klimov wrote: > Hello all, > > Having 10 days since an rc1 and a number of issues fixed and late-coming > features integ

Re: [Nut-upsuser] NEWLINE

2022-04-10 Thread Greg Troxel
Jim Klimov via Nut-upsuser writes: > I believe the code only deals with '\n' character for line-breaks, in > protocol and probably configs. Probably if nut started out as IETF-ish and was mimicking SMTP it would look for \r\n, but it seems obviously unix-ish (seems normal to me!) and is \n. S

Re: [Nut-upsuser] NEWLINE

2022-04-10 Thread Manuel Wolfshant
On 4/10/22 20:45, Jim Klimov via Nut-upsuser wrote: I believe the code only deals with '\n' character for line-breaks, in protocol and probably configs. 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

Re: [Nut-upsuser] NEWLINE

2022-04-10 Thread Jim Klimov via Nut-upsuser
I believe the code only deals with '\n' character for line-breaks, in protocol and probably configs. Jim On Sun, Apr 10, 2022, 19:26 Roger Price wrote: > The IETF requires that the I-D contain an ABNF (Augmented Backus-Naur > Form) > grammar of the NUT commands and responses. At the end of eac

[Nut-upsuser] NEWLINE

2022-04-10 Thread Roger Price
The IETF requires that the I-D contain an ABNF (Augmented Backus-Naur Form) grammar of the NUT commands and responses. At the end of each command, there is a NEWLINE character sequence. The IETF in RFC 5234 say that NEWLINE is CRLF, carriage return + line feed, hex 0D0A. Is this true for NUT

Re: [Nut-upsuser] NUT v2.8.0(-rc1)

2022-04-10 Thread Jim Klimov via Nut-upsuser
Hello all, Having 10 days since an rc1 and a number of issues fixed and late-coming features integrated, I'm rolling the dice again with NUT v2.8.0-rc2 Hope it brings no bad surprises either :) Jim Klimov On Fri, Apr 1, 2022, 02:01 Jim Klimov wrote: > Hello, fellow NUTs! > > It is with a [h