Nut upsuser - Apr 2022 - NEWLINE

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? The ISE editor requires me to document what NUT does, not 
what the IETF propose.  Does upsd accept all forms of NEWLINE or only hex 0A?

Roger

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 <roger at rogerprice.org> 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 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? The ISE editor requires me to document what NUT
> does, not
> what the IETF propose.  Does upsd accept all forms of NEWLINE or only hex
> 0A?
>
> Roger
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220410/33679dbd/attachment.htm>