similar to: grep ID /etc/os-release

2015-03-26 9:03 GMT+01:00 Arnaud Quette <arnaud.quette at gmail.com>: > Hey mister M' > > A first huge thanks for taking care of this, and so late in the night. I > know that it's not easy... > > (sent from my S3... please excuse my brevity) > Le 25 mars 2015 18:49, "Emilien Kia" <kiae.dev at gmail.com> a ?crit : > > > > > >

On 11/19/20 4:09 PM, Roger Price wrote: > I would like to build a list of the user names and configuration file > locations for the most common distributions which include NUT.  So far > I have: > >  Distrib    User   Config directory >  debian     nut    /etc/nut/ >  opensuse   upsd   /etc/ups/ > > These will be used to produce more user-friendly tools and >

On 11/19/20 6:48 PM, Manuel Wolfshant wrote: > On 11/19/20 4:09 PM, Roger Price wrote: >> I would like to build a list of the user names and configuration file >> locations for the most common distributions which include NUT.  So >> far I have: >> >>  Distrib    User   Config directory >>  debian     nut    /etc/nut/ >>  opensuse   upsd   /etc/ups/

Hi Charles, I am using the same configs as I have in Linux Mint. What do I need to change here? ups.conf [defender] ??? driver = blazer_usb ??? port = auto ??? pollinterval = 5 ??? desc = "PowerShield Defender 650" upsd ??? default.battery.voltage.high = 13.70 ??? default.battery.voltage.low = 10.40 upsd.users [local_mon] ??? ??? password = ******** ??? ??? allowfrom =

In my system log file I get messages like: Jul 18 13:05:12 mint upsd[4025]: Host 192.168.145.12 disconnected (read failure) Jul 18 13:10:12 mint last message repeated 5 times Jul 18 13:10:12 mint last message repeated 4 times and broadcast messages like: Communications with UPS mintups at mint.phcomp.co.uk lost 30 seconds later: Communications with UPS mintups at mint.phcomp.co.uk

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Hi Charles, Thanks for your help. Seems to be mostly ok except am getting error access denied. See below. I see from searching this is a common error but so far I can't find a fix. This is how I configured things before make and install. created group nut nut:x:103: created system user ups with group nut. ups:x:123:103::/home/ups:/bin/bash Create statepath directory. sudo mkdir -p

2015-03-21 17:06 GMT+01:00 Melkor Lord <melkor.lord at gmail.com>: > > On Fri, Mar 20, 2015 at 4:40 PM, Emilien Kia <kiae.dev at gmail.com> wrote: > > Some precisions: >> >> we are not alone, some projects had similar problem: >> http://bugs.bitlbee.org/bitlbee/ticket/785 >> And the problem is really coming from NSS initialization. Discussion

On Fri, 29 Mar 2024, Dan Grostick wrote: > It is consistently happening 14-15 minutes after starting. Please see attached > upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary > upssched is used. After the heartbeat failure, is upsd still running? Does the command "upsc -L" report the UPS's? If you use systemd, what does the command

Hi, I spent quite some time pulling my hair out and trying to figure out why NUT wasn't working properly with SSL enabled. I tried several approaches until I found something interesting. I'm using NUT 2.7.1 in Ubuntu Server 14.04 Trusty Tahr After properly configuring a self signed certificate with "certutil" from libnss3-tools, there was no way to get proper SSL connection

Hi Charles and the list here is an update on 2.7.3 2015-03-20 3:33 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 19, 2015, at 2:00 PM, Arnaud Quette <arnaud.quette at gmail.com> > wrote: > > * #158: the branch has been collapsed into one commit, but additional >> documentation (nut-names.txt) is needed: >>

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

FWIW, I wonder if this is a fallout of PR #1274 : https://github.com/networkupstools/nut/pull/1274/files and specifically https://github.com/networkupstools/nut/commit/550064930e369fb3a322c3b28ffff8b4acf53532 which added a `sock_read()` loop continuation effectively if `pconf_char()` returned 0. Just grasping at straws here (since it is a change a couple of months before the release was cut),

FWIW, I wonder if this is a fallout of PR #1274 : https://github.com/networkupstools/nut/pull/1274/files and specifically https://github.com/networkupstools/nut/commit/550064930e369fb3a322c3b28ffff8b4acf53532 which added a `sock_read()` loop continuation effectively if `pconf_char()` returned 0. Just grasping at straws here (since it is a change a couple of months before the release was cut),

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

R pattern-matching and replacement functions are vectorized: they can operate on vectors of targets. However, they can only use one pattern and replacement. Here is code to apply a different pattern and replacement for every target. My question: can it be done better? sub2 <- function(pattern, replacement, x) { len <- length(x) if (length(pattern) == 1) pattern <-

Good morning all. I am on a different system with a different UPS, and I am fighting a similar problem to the one I posted about yesterday, and again making little headway. This system is running Debian Wheezy and connected to an APC BackUPS ES550. Starting things manually seems to go well, but my startup script fails, and nothing is logged anywhere. This may not be a NUT question per se, but I