<feed xmlns='http://www.w3.org/2005/Atom'>
<title>packages/net/nut/files/nut_server, branch master</title>
<subtitle>Mirror of packages feed</subtitle>
<id>https://git.openwrt.org/feed/packages/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/feed/packages/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/'/>
<updated>2026-04-27T08:42:36Z</updated>
<entry>
<title>nut: ensure correct upsmon settings names</title>
<updated>2026-04-27T08:42:36Z</updated>
<author>
<name>Daniel F. Dickinson</name>
</author>
<published>2026-03-17T02:54:39Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=0c88118ad4bb303b811975925641357e69f6736b'/>
<id>urn:sha1:0c88118ad4bb303b811975925641357e69f6736b</id>
<content type='text'>
Prompted by
https://github.com/openwrt/luci/pull/8420#issuecomment-4071252681
we update upsmon configs to ensure they are correct according to
upstream. We reorder the options so that they match upstream
documentation at
&lt;https://networkupstools.org/docs/man/upsmon.conf.html&gt; to be sure
we have not missed any items.
While at it, we add configuration options from the upstream
documentation that are not currently present in the UCI configs.

Some years ago upstream changed the names the primary/secondary
UPS system/monitor from master/slave to primary/secondary. It
is uncertain how much longer these deprecated names will be
accepted by NUT.
Therefore update naming to match upstream documentation and
configuration. See
&lt;https://networkupstools.org/docs/man/upsmon.html&gt;,
&lt;https://networkupstools.org/docs/man/upsmon.conf.html&gt;, and
&lt;https://networkupstools.org/docs/man/upsd.users.html&gt;.

At the same time, prompted by
https://github.com/openwrt/packages/pull/28875#issuecomment-4079307540
we simplify the configuration and add checks to avoid bad configs
due to misspellings/typos of configuation options by users.

A sample config

config upsmon 'upsmon'
       option notifycmd '/usr/bin/logger -t nut-monitor-exec '

config monitor
        option type primary
        option upsname upsname
        option hostname localhost
        option username upsuser
        option password upspassword

config notifications 'ONLINE'
        option message "UPS %s is on line power"
        option flag "SYSLOG"

config notifications 'ONBATT'
        option message "UPS %s is on battery power"
        option flag "SYSLOG+EXEC"

In order to iterate through the notifications, we use named
'notifications' sections and compare the section name to list of
notification events defined by NUT. If they don't match, warn
during initscript startup.

Signed-off-by: Daniel F. Dickinson &lt;dfdpublic@wildtechgarden.ca&gt;
</content>
</entry>
<entry>
<title>nut: initscripts hotplug: Fix many small semantic issues</title>
<updated>2019-01-20T17:16:28Z</updated>
<author>
<name>Daniel F. Dickinson</name>
</author>
<published>2019-01-16T12:09:13Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=d7db15459f222ef1b5878c543a01a78fb55a73a7'/>
<id>urn:sha1:d7db15459f222ef1b5878c543a01a78fb55a73a7</id>
<content type='text'>
Small but important tweaks to fix the operation of the nut initscripts
and hotplug scripts.  All hail shellcheck and proofreading and
dogfooding.

Signed-off-by: Daniel F. Dickinson &lt;cshored@thecshore.com&gt;
</content>
</entry>
<entry>
<title>nut: Update server config comment 'docs'</title>
<updated>2018-12-23T05:24:37Z</updated>
<author>
<name>Daniel F. Dickinson</name>
</author>
<published>2018-12-23T02:47:34Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=f916a7e0ebf413a5d60c9d271766121d4ddb0ffd'/>
<id>urn:sha1:f916a7e0ebf413a5d60c9d271766121d4ddb0ffd</id>
<content type='text'>
Update the commented out settings in /etc/config/nut_server that
shows the available sections with their default settings.

Signed-off-by: Daniel F. Dickinson &lt;cshored@thecshore.com&gt;
</content>
</entry>
<entry>
<title>nut: Reorganize nut-server to clarify nut-driver</title>
<updated>2018-08-29T04:12:53Z</updated>
<author>
<name>Daniel F. Dickinson</name>
</author>
<published>2018-08-27T13:50:34Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=ceff68837d4b8d5a9bd8bf1962e913b5203d95e5'/>
<id>urn:sha1:ceff68837d4b8d5a9bd8bf1962e913b5203d95e5</id>
<content type='text'>
Clarify the different between the common nut-driver portions of
nut-server and the nut-server (upsd) proper.  nut-driver can't
be used without nut-server so there is no compelling reason
to split into a separate package, but the reorganization makes
such a move easier and makes it clear what each bit is for.

While we continue to use a single initscript, it's a properly
procdified one which handles the upsd daemon as a different
instance than the driver instances.  This resolves a race
condition in which upsd and drivers fail to start do to
a degree of interdepedence.

Also properly 'procd'ifies the nut-server initscript.

Signed-off-by: Daniel F. Dickinson &lt;cshored@thecshore.com&gt;
</content>
</entry>
<entry>
<title>net/nut: Build optional separate packages and ucify</title>
<updated>2017-01-11T23:53:58Z</updated>
<author>
<name>Daniel Dickinson</name>
</author>
<published>2017-01-11T23:53:58Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=a23c4e85c5f6c9f9dcf67743b93c492ba833e365'/>
<id>urn:sha1:a23c4e85c5f6c9f9dcf67743b93c492ba833e365</id>
<content type='text'>
With a LuCI app (of which I have one written) ucification makes
sense (and is in fact needed), so ucify the initscripts.

Also, rather than making selection of things to include an image
a matter of selecting compile-time config options, make optional
things into seperate packages that are built in default builds,
and leave selection of what to include or not up to the user
(e.g. using ImageBuilder, or adding packages via opkg).

Signed-off-by: Daniel Dickinson &lt;lede@cshore.thecshore.com&gt;
</content>
</entry>
</feed>
