<div dir="auto">Hi, sorry for missing this in my mailbox.<div dir="auto"><br></div><div dir="auto">The short answer is that a port=<a href="http://file.xyz">file.xyz</a> would now loop like before (which was the only mode then). </div><div dir="auto"><br></div><div dir="auto">Since 2.8.0 there are 3 modes in setting as well as reports in `upsc` etc.: 2 for explicit behavior (dummy-once as default for *.dev and dummy-loop as default for *.seq) and one implicit "dummy" that goes for legacy default and least surprise in general, so looping. But over eons this one might change or not.</div><div dir="auto"><br></div><div dir="auto">Jim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 5, 2022, 14:34 Roger Price <<a href="mailto:roger@rogerprice.org">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">I am trying to understand the new 2.8.0 dummy-ups man page. I see that the old <br>
2.7.4 behaviour of looping on the operations specified in the file named by port <br>
= <a href="http://file.dev" rel="noreferrer noreferrer" target="_blank">file.dev</a> in ups.conf has changed. The ".dev" in "<a href="http://file.dev" rel="noreferrer noreferrer" target="_blank">file.dev</a>" now means <br>
once-only. The user may specify the old looping behaviour by either<br>
<br>
1. Specifying port = file.seq<br>
2. Specifying mode = dummy-loop in ups.conf<br>
<br>
However the man page does not say what happens if port = <a href="http://file.xyz" rel="noreferrer noreferrer" target="_blank">file.xyz</a> and there is <br>
no mode declaration in ups.conf. All it says is "dummy is assigned by default <br>
to files with other naming patterns that the driver could not classify".<br>
<br>
Which dummy behaviour should I expect: dummy-once or dummy-loop ?<br>
<br>
For reference I attach the Dummy Mode part of the man page.<br>
<br>
Roger<br>
<br>
###############################################################################<br>
<br>
Dummy Mode<br>
<br>
In this context, port in the ups.conf block defines a file name for the <br>
dummy-ups to read data from. This can either be an absolute or a relative path <br>
name. In the latter case the NUT sysconfig directory (i.e. /etc/nut, <br>
/usr/local/ups/etc, …) is prepended.<br>
<br>
Since NUT v2.8.0 two aspects of this mode are differentiated:<br>
<br>
dummy-once reads the specified file once to the end (interrupting for TIMER <br>
lines, etc.) and does not re-process it until the filesystem timestamp of the <br>
data file is changed; this reduces run-time stress if you test with a lot of <br>
dummy devices, and allows use/test cases to upsrw variables into the driver <br>
instance — and they remain in memory until the driver is restarted (or the file <br>
is touched or modified);<br>
<br>
Since NUT v2.8.0 dummy-once is assigned by default to files with a *.dev <br>
naming pattern.<br>
<br>
dummy-loop reads the specified file again and again, with a short sleep <br>
between the processing cycles; for sequence files using a TIMER keyword (see <br>
below), or for use/test cases which modify file contents with external means, <br>
this allows an impression of a device whose state changes over time.<br>
<br>
Before NUT v2.8.0 this was the only aspect, so a simple dummy mode value <br>
maps to this behavior for backwards compatibility.<br>
<br>
Since NUT v2.8.0 dummy-loop is assigned by default to files with a *.seq <br>
naming pattern, and dummy is assigned by default to files with other naming <br>
patterns that the driver could not classify.<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>