similar to: Bug#501087: nut: support for a tripplite avr750u

Package: xcp-xapi-debug Version: 1.3.2-11 Severity: normal User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in

Package: xcp-xapi Version: 1.3.2-11 Severity: important User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in

Package: xcp-xapi Version: 1.3.2-14 Severity: important User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in ./usr/lib/xcp/lib/host-restore line

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

I have a TrippLite AVR550U that my company uses several individual Linux boxes in one large system, all running Ubuntu 18.04LTS, and all will be using the package version of nut - 2.7.4. In my scenario, our usage case is for the PCs to all shut down, followed by the individual UPSes, when mains power is removed from the whole system. (This isn't a typical setup for UPS, but it's what

Package: blktap-utils Version: 2.0.90-1 Severity: important User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in ./usr/sbin/vhdpartx line 40

Thanks for the quick response! On Sat, Jun 27, 2020, at 22:17, Manuel Wolfshant wrote: > On 6/28/20 4:25 AM, Scott Colby wrote: > > Hello, > > > > I am having difficulty using NUT to shut down my Netgate SG-1100 > > (a pfSense router) when the power level of the UPS gets critically > > low. > > > > Here is some relevant information: > > - OS:

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and

For my Smart 2200, a charged battery string is anywhere between 25.6 and 26.8 volts. I'm seeing nut report 13.0 volts, which seems suspicious. Even if the UPS were reporting half of the actual battery voltage to keep protocol compatibility with models having a 12V battery system, the value of exactly 13.0 seems unlikely. According to the page at

Hello, https://networkupstools.org/ddl/Tripp_Lite/AVR750U.html Going off of this page, it looks like this should be supported by usbhid-ups, but it seems to be failing. Attached is a log of my attempts to start the driver. Let me know what I can do to help. -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 6/28/20 5:54 AM, Scott Colby wrote: > > I'm not convinced this is the problem; I think that pfSense has > an alternative way of running the NUT components: > # ps aux | grep ups > root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon > uucp 45751 0.0 0.1 6796 772 - S 02:22 0:00.10 /usr/local/sbin/upsmon > uucp 46796

On Sun, 28 Jun 2020, Scott Colby wrote: > I'm now becoming suspicious of a couple of the values reported by > `upsc`: > - battery.charge.warning = 30, but there is no battery.charge.low. > Does this mean that the low battery flag will never be raised? When you disconnect wall power, do you get email notifications for events [OB] and [LB] ? > - ups.timer.reboot,

I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I posted in the github issue I created, perhaps that will give you some hints on your issue. Maybe

I am driving a Suse 8.2 linux with cups 1.1.18 and samba 2.2.7a. The problem: The host serves several printers via cups. If some jobs are in one of the queues "lpq -Pprinter" or "lpstat -o printer" shows up the complete listing. Fine. Connected to the same print queue from a Windows (XP/NT/98/2k) box I cannot see the complete listing. Sometimes I see some of the jobs, most of

An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20090120/ffb91e55/attachment.htm

On 6/28/20 4:25 AM, Scott Colby wrote: > Hello, > > I am having difficulty using NUT to shut down my Netgate SG-1100 > (a pfSense router) when the power level of the UPS gets critically > low. > > Here is some relevant information: > - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) > - NUT version: 2.7.4 > - Installed from: pfSense package 2.7.4_7 > - UPS:

Hello, I am searching for a solution that I thought should be kind of standard, but until now I was not successful finding anything. Here is the problem: At our site we offer windows and linux, most servers (eg file, samba, web) are linux based. User data is stored on NFS file servers. Windows systems are part of a Windows domain with an ADS domain controller. At the moment the linux samba

Hello Luc, thanks for your answer. If I understand you correctly than you are using samba4 as windows domaincontroller and you do not have another Windows DC? So after all you have exactly one Kerberos Server that is part of the samba4 server? Thanks Rainer Am 24.03.2015 um 12:41 schrieb Luc Lalonde: > Guten tag Rainer, > > We use our Samba4/Win2k8 AD domain to authenticate all our

Dear Ladies and Gentlemen! On a CD-ROM-server at the University Koblenz-Landau we are using Samba (2.0.5a) with Red Hat Linux (6.0, Kernel 2.2.5). The server is located here in Koblenz, but also used from another department of the university at Landau (about 80 miles from Koblenz; they have their own class B network). A traceroute from both locations gave a response time of about 10-50 msec. On

I am driving Suse 8.2, samba 2.2.7a, cups 1.1.18 As I mentioned recently I cannot see the cups printer queues from a windows client even if lpq -Pprinter on the cups server gives the correct status. I tested a litte more and got the following results: 1.) If I configure samba to printing = CUPS printcap name = CUPS I can see all queue entries in the windows status panel, too -- except