similar to: TLS support in NUT

On 6/13/21 3:36 PM, Jim Klimov via Nut-upsdev wrote: > Haven't got many ideas on this today, preoccupied with other > house-work, but can share a couple :) > > Regarding two implementations - I believe NSS and OpenSSL are licensed > differently and/or are (initially were?) available non-overlapping on > different OSes. A quick googling now showed that they both were >

On June 13, 2021 9:02:46 PM GMT+03:00, Tim Dawson <tadawson at tpcsvc.com> wrote: >Let's not overlook the simple fact that a lot of deployments are behind >secure firewalls, on secure networks, and on servers and lans that no >users have access to (physical ormotherwise), and thus have negligible >security requirements beyond what the environment already provides. >Yes,

I'm using NUT 2.4.1 with openSUSE 11.2, my UPS is an MGE/Eaton Ellipse ASR 1500 USBS. The set-up is as described at http://rogerprice.org/NUT.html. Since NUT uses TCP wrappers, I have the /etc/hosts.allow entry upsd : 10.0.0/24, localhost, LOCAL, 127.0.0.1 : ALLOW When I pull the plug from the wall to test my setup, I get the sequence of KDE notifications and finally a

I upgraded an operating system to openSUSE 42.2, kernel 4.4 and recompiled nut 2.7.4. ./configure, make clean and make went well, but make install failed. Make reports Making install in clients make[1]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' make[2]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' /usr/bin/mkdir -p '/usr/lib64'

On Thu, 14 Jul 2016, Dmitri Stepanov wrote: > Some of those hosts haven't NUT including upsmon (and other software > which is not included by suppliers of the hosts) for a number of > reasons. I don't need to inform not-NUT hosts about any UPS events, > etc... but only shutdown all the hosts after upssched timer expired. So > I think shutdown them via ssh would be

Dear Sirs, I'm Massimo Zampieri responsible for the software and connectivity accessories for Riello UPS. I would like to list our UPS to NUT. For this porpoise we will provide to you all the information requested as serial protocols, end even some ups in case. We have 2 way to communicate with our ups via RS232 and USB (with our driver, but the source code will be provided in case) and via

I am backing up a user's directories from local machine titan to remote machine maria. On the remote machine maria file /etc/rsyncd.conf contains [rprice-home] ... exclude = *.dvi I start the backup by using this command on the local machine titan: rprice at titan ~ rsync -av --dry-run /mnt/home/rprice rsync://rprice at maria/rprice-home I get the messages sending incremental

On Thu 18 Jan 2024, Roger Price via rsync wrote: > I am backing up a user's directories from local machine titan to remote > machine maria. On the remote machine maria file /etc/rsyncd.conf contains > > [rprice-home] > ... > exclude = *.dvi > > I start the backup by using this command on the local machine titan: > > rprice at titan ~ rsync -av --dry-run

Thank you for answer Stuart >?????, 13 ???? 2016, 17:54 +03:00 ?? Stuart Gathman <stuart at gathman.org>: > >On 07/13/2016 10:02 AM, Stuart Gathman wrote: >> On 07/13/2016 04:17 AM, Dmitri Stepanov wrote: >>> I need to shutdown a number of hosts which has not NUT from one which has it. >> Let's make sure you are not missing an obvious point. By

Ok, so I have made some progress that seems to suggest the initial “fix” I stumbled upon isn’t required. I haven’t yet worked backwards to figure out reasons why our customers have had similar complaints or solve the problem on the CentOS VM yet, but that is on the todo list. I am hoping it ends up just being not enabling the service on startup, but I can’t say that explains away all the symptoms

I am (belatedly) updating pkgsrc to 2.8.1 (+ bugfix). (FWIW, I think a 2.8.1.1 or 2.8.2 immediately with the fix is in order. >From a packaging viewpoint, the effort to update for a release is about 3 minutes plus time to adapt anythhing that has changed. So I'd much rather have releases more often.) In the pkgsrc build, nut finds tcp wrappers because they are part of the base system.

oiaohm <wineforum-user at winehq.org> at Aug 30, 2008 3:53 PM (MST) [Wine] Re: Wine Feature suggestion (Windows Compatibility System) > >There is still a part missing from wine. Windows Compatibility system. The shim's that automatically provide overrides for some applications. > This is possible through winecfg. However, I agree that this should be packaged with Wine based

I have just recently gotten NUT to work on my system, with much assistance from Charles Lepple, and am very?grateful for his assistance. ? I now have a question regarding the NUT-Monitor program. ?There is a tool in the GUI that is for sending devicecommands. ?I can't get it to work. ?Whenever I try to send a command I get the following message: Failed to send <command> ?(ERR USERNAME

Hi, I've browsed the archives back for a few months and nothing has jumped out at me as being helpful, but since there doesn't seem to be a search facility it's certainly possible I've missed what I'm looking for. Anyway, I wonder if someone can help me. I've very recently installed nut 2.0.4-r1 on a gentoo box and am in the initial stages of configuration and testing.

While browsing the sources of the nss-ssl-port sources I noticed that client certificates were added. What is the reason behind this? As far as I can see, using a server certificate and validating it in the upsmon client should provide us with a secure channel. Authorizations for the server will then be handled by the settings in upsd.users by logging into the server with user and

I think I have found a way to deal with the issue of the spurious message on startup of NUT. Before implementing it, I would like to see what the other developers think of this idea. My proposal is not to wait for DUMPDONE in the startup of upsd for a duration of MAXINIT seconds, but rather to send the fake "INIT" status in response to a ups.status request. As soon as DUMPDONE hits, or

Hi, I cant get it working. Here is my terminal output: root at debian-jessie-final:~# lsusb -d 051d:0002 Bus 001 Device 010: ID 051d:0002 American Power Conversion Uninterruptible Power Supply root at debian-jessie-final:~# ls -l /dev/bus/usb/001/010 crw-rw-r-- 1 root nut 189, 9 Mai 6 15:35 /dev/bus/usb/001/010 root at debian-jessie-final:~# sudo upsdrvctl start Network UPS Tools - UPS driver

First off, my apologies for bringing back this thread from the dead (September 2005, http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-September/000150.html), however my problem seems relevant enough that I wondered what happened to this thread as it seems to have died after the message I quote below. Despite the fact that I am having trouble getting my Sweex 1000VA UPS (USB) to work, and

First off, my apologies for bringing back this thread from the dead (September 2005, http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-September/000150.html), however my problem seems relevant enough that I wondered what happened to this thread as it seems to have died after the message I quote below. Despite the fact that I am having trouble getting my Sweex 1000VA UPS (USB) to work, and

Hello, I have been using the package "spdep" to run spatial regressions on a data set with about 2500 observations. It has performed well up until now, but the following code resulted in an error: > load("Panel.90s.ok.R") > attach(Panel.90s.ok) > neighs<-dnearneigh(cbind(x,y),0,50000) > help(nbdists) > dists<-nbdists(neighs,cbind(x,y)) >