| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
Remove the GCC requirement by adding -lpthread and removing the
nullification of CFLAGS and LDFLAGS in the M4 script that verifies
we have a working libltdl.
|
| |
|
|
|
|
|
|
| |
Add missing then.
PR: 269497
Reported by: <vvd@unislabs.com>
Fixes: 6558c2506990
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The nut file ownership fixups due to the UID/GID change from uucp/uucp
to nut/nut may not be desireable for all users. Some users with custom
file ownership may wish ownership to remain untouched. This revision
to the nut family of ports/packages allows users to optionally disable
automatic fixup of nut file ownership.
While at it, rather than use a hardcoded string for user/group ownerships,
use the set parameters in Makefile.
PR: 269497
suggested by: dvl
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Preexisting nut files will have uucp group permissions, which will no
longer be available to nut because it runs under its own GID. For the
time being add code to nut_prestart() adjusting the ownership of the
files to UID nut and GID nut.
This code should be removed approximately a year from now as it is
expected that most if not all nut installations will have correct file
ownership by then.
While here, also fix nut.newsyslog to refer to the new nut UID/GID.
Reported by: avg, Mathieu <sigsys@gmail.com>
Fixes: 02c038c8cc15
|
| |
|
|
|
|
|
|
|
|
| |
In some cases nut may start before devd causing it to fail because it
lacks permissions to USB attached UPS devices. The nut supplied
devd.conf ensures that nut has read/write access to the UPS.
PR: 267144
Reported by: ml@netfence.it
MFH 2022Q4
|
| |
|
|
|
|
| |
Now that muliple UPS support has been accepted and merged into our
upstream's mainline, revert the nut-devl part of 2c6ac43b0d95 and
9c4a120c36bf, and pull in the latest nut commit on GH.
|
| |
|
|
|
| |
Remove headers used in the first attempt. Removing them reduces some
namespace pollution and has no nother effect on the resulting package.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
upslog is a utility that logs UPS status at regular intervals, specified
by the -i option. Unfortunately upslog supports only on UPS. For sites
that need to monitor multiple UPSs the options are to cobble an rc script
for each or doctor up the nut_upslog.in script to support cloning of the
script. Unfortunately an rc script capable of being cloned would become
the source of more PRs and would require significanly more tehcnical
documentation that by itself might become confusing for the average
system administrator.
Therefore a new -m option is added to support multiple UPSs using the
same invocation of upslog. The patch parses a new -m option and using a
single connection to upsd, queries it for stats about multiple UPSs.
An rc.conf exemple of how to use this new feature:
nut_upslog_flags="-p /var/db/nut/upslog.pid -m ups1@localhost,/var/log/nut\
/ups1.log -m ups2@localhost,/var/log/nut/ups2.log"
PR: 265963
Reported by: vvd@unislabs.com
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
upslog is failing to make multiple connections to upsd resulting
in some UPSs logging and others not. This is likely some bug
in upsd's socket handling.
Even though this patch worked for me locally it did not for the
person reporting the problem.
A better approach would be to use select() instead.
PR: 265963
This reverts commit dec4ecc3afecab035a4d4fa59c35093d9f53ffd5.
|
| |
|
|
|
| |
The nut daemons are consumer of syslogd services. Start after syslogd
has started.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Add sample rc script to allow a user to copy a sample rc script to
rc.d, allowing the user to use multiple instances of upslog(8) with
multiple instances of the rc script to log multiple UPSs on the same
system.
The sample rc script was provided by vvd@unislabs.com.
PR: 265963
Reported by: vvd@unislabs.com
Submitted by: vvd@unislabs.com
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
upslog is a utility that logs UPS status at regular intervals, specified
by the -i option. Unfortunately upslog supports only on UPS. For sites
that need to monitor multiple UPSs the options are to cobble an rc script
for each or doctor up the nut_upslog.in script to support cloning of the
script. Unfortunately an rc script capable of being cloned would become
the source of more PRs and would require significanly more tehcnical
documentation that by itself might become confusing for the average
system administrator.
Therefore a new -m option is added to support multiple UPSs using the
same invocation of upslog. The patch parses a -m option and forks
almost immediately following the getopt(3) invokation to monitor each
individual UPS using a separate upslog process. This is not ideal but
better than scripting. Lightweight threads might be a better solution.
An rc.conf exemple of how to use this new feature:
nut_upslog_flags="-p /var/db/nut/upslog.pid -m ups1@localhost,/var/log/nut\
/ups1.log,/var/db/nut/ups1.pid -m ups1@localhost,/var/log/nut/ups2.log,/var\
/db/nut/ups2.pid"
Sending a TERM signal to the parent PID, kill `cat /var/db/nut/upslog.pid`,
will terminate the entire process tree.
This patch submitted upstream, is in the process of being refined and
accepted.
PR: 265963
Reported by: vvd@unislabs.com
|
| |
|
|
|
|
|
|
|
|
|
| |
At the moment this new feature, a GUI to monitor nut, inconsistently
builds and installs itself. It fails to build when built under
poudriere or when using an unprivileged account. However it will
build and install when built by hand by root. Even though ./configure
(configure.ac) is supposed to support enabling and disabling the
option, this does not work. The option remains "auto" and nut_monitor
will install or not install based on some unknown at the moment
criteria.
|
| | |
|
| |
|
|
|
|
|
| |
FreeBSD has no libusb-1.0.so, even though pkgconf identifies it as such.
The ABI is the same but the name is different.
Reported by: Paul Arakelyan <paul.arakelyan@gmail.com>
|
| |
|
|
|
|
|
| |
Poweroff instead of halt when signaling shutdown.
PR: 263855
Reported by: clear.screen@orange.fr
|
| | |
|
| |
|
|
|
|
|
|
|
| |
devfs does not always win the race with nut causing nut to fail to
start in some installations.
PR: 258190
Submitted by: hsakamt@tsnr.com
Reported by: hsakamt@tsnr.com
|
| | |
|
| |
|
|
| |
Notes:
svn path=/head/; revision=555091
|
| |
|
|
| |
Notes:
svn path=/head/; revision=553149
|
| |
|
|
|
|
|
| |
Upstream issue: https://github.com/networkupstools/nut/issues/835
Notes:
svn path=/head/; revision=552928
|
| |
|
|
|
|
|
|
|
|
| |
Changes: https://github.com/asciidoc/asciidoc-py3/releases
https://github.com/asciidoc/asciidoc-py3/blob/master/CHANGELOG.txt
PR: 245723
Submitted by: antoine
Notes:
svn path=/head/; revision=532404
|
|
|
the networkupstools/nut github repo.
Notes:
svn path=/head/; revision=529220
|
