similar to: RE: Nut-upsuser Digest, Vol 11, Issue 3

Hello, Help me please with *newhidups* setup. Does it work for someone on *BSD ? Here is the data. --------------------------------------------------------------- *** FreeBSD root.srv# uname -a FreeBSD xxxxxx.dyndns.info 5.3-RELEASE FreeBSD 5.3-RELEASE #2: Tue Feb 8 07:38:22 UTC 2005 admin@temp.botka.homeunix.org:/usr/src/sys/i386/compile/SRV i386 *** NUT ver.2.0.3 root.srv# ll /var/db/pkg/

On Jul 16, 2019, at 3:52 AM, Patrick M. Hausen wrote: > The OS is FreeBSD: > > FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at nemesis:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64 > > This is the device: > > ugen0.6: <POWERCOM Co.,LTD HID UPS

Hi, Have anybody tried Cyberpower Value 600E (USB) under FreeBSD? usbhid-ups from nut 2.4.1 does not recognize (find) the device on my machine. [root at substance /usr/local/libexec/nut]# uname -a FreeBSD substance.dyndns.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root at walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [root at substance

Hi all, I’m new to NUT and have some trouble getting my new UPS to work. Since the HCL listed Powercom UHID models as „green“ I thought buying a Roline (German rebranded Powercom) model would be a good idea. The OS is FreeBSD: FreeBSD freenas-pmh.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+6aad246318c(HEAD): Mon Jun 24 17:25:47 UTC 2019 root at

Hello, I'm new to the list, new to NUT, but not new to Unix-likes. I could use some help getting NUT to talk to my Tripp Lite G1000U. Searching Google for "Tripp Lite G1000U" returns exactly two hits at this writing, so that may not be a good sign. ;-) It may just be rebranded for sale through this source (Costco). Externally, the G1000U looks much like the SMART1000LCD: an amber

Hi, colleagues! Something strange happens with a server. I am attempting to connect management interface of UPS with server via USB. In console I see a lot of errors: Mar? 7 13:42:04 xxx kernel: ugen2.2: <POWERCOM Co.,LTD HID UPS Battery> at usbus2 Mar? 7 13:42:05 xxx kernel: uhid0 on uhub6 Mar? 7 13:42:05 xxx kernel: uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.02,

All: I am having a devil of a time getting nut to work on freebsd. Here is what I have done. I am trying to load the drivers, and here is my ups.conf file: [tripplite] driver=trippliteesu port=auto When I dmesg on freebsd 7.1 for my usb device: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2> on uhub0 using the usbdevs -v command: Controller /dev/usb0: addr 1:

I wrote a small app that monitors a Back-UPS ES500 UPS via the uhid0 interface. I want to run the daemon with as little privs as possible. gastest# ls -l /dev/uhid0 crw-rw---- 1 root operator 122, 0 Nov 12 05:26 /dev/uhid0 gastest# Is it safe to chmod o+r /dev/uhid0 ? Or is there a better way to drop privs of the daemon yet still be able to read from the device ? All I am doing is

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

I am thankful for all support received so far and I feel I'm getting closer to a solution. To get back to basics and a more transparent setup I have made a clean Ubuntu 16.04 installation and followed this guide https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server Windows clients users are logged in with username Admin (local account, administrator). The samba share is

On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > 0.016485 Trying megatec protocol... > 0.017411 send: Q1 > 0.252545 read: (244.4 244.4 229.9 028 50.0 2.19 23.1 00000001 > 0.252589 Status read in 1 tries > 0.252602 Supported UPS detected with megatec protocol > 1.288032 send: Unknown error > 1.288085 Permissions problem: Input/output error

Hi all. I'm trying to get a CyberPower OR700LCDRM1U UPS working with NUT (via USB). I assumed this would be compatible since the OR2200LCDRM2U is. Clearly I'm wrong or missing something vital. I'm on FreeBSD, using the version of NUT from the ports tree (2.6.1). FWIW, I tried compiling from source with similar results. Here's my UPS in ups.conf: [ssups] driver=usbhid-ups

On 2/5/14, 9:55 PM, Charles Lepple wrote: > On Feb 5, 2014, at 9:03 PM, Chris Duffy wrote: > >>> Please run this: >>> >>> /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D >>> >>> and send the output back to the list. >>> >> Output from the above command: >> >> 0.000000 debug level is '1' >>

Hello, I have a server pfsense in bridge mode to function as transparent FW, the problem is that once I connect the pfsense between my router core and my core switch catalyst a few seconds begin to appear several messages like these: em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting And the connection falls

Hi! I'm having problems connecting Ippon Smart power pro 1000 UPS to nut via usb under FreeBSD 7-stable The UPS uses megatec protocol and works fine via RS232 (UPS has RS232 and USB connectors) When I connect USB /dev/uhid0 is created. Tried port=/dev/uhid0 - doesn't work. Kernel rebuild w/o option uhid. On connect I get 2 devices /dev/ugen1, /dev/ugen1.1. Tried both of them.

Hello all! Some days ago we received new UPS?Powercom BNT-2000AP with USB interface to replace an old staff and I've spent three last days trying to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. # dmesg|grep -i powercom ugen0.3: <POWERCOM Co.,LTD> at usbus0 uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01, addr 3> on usbus0 uhid0: <POWERCOM

On April 28, 2017 9:11:59 AM GMT+03:00, "????????? ?????????" <vtk-alexb at mail.ru> wrote: >Hello all! > >Some days ago we received new UPS?Powercom BNT-2000AP with USB >interface to replace an old staff and I've spent four last days trying >to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. > ># dmesg|grep -i powercom >ugen0.3:

Thx Charles, So since this is a new type of UPSonic UPS, do you think the vendor screwed up or is it just some quirk on Freebsd? Yes, if you can look into this I would appreciate it. I do not see anyone else on the Web attempting to use this new device yet.....but....... Regards chris On 2/6/14, 8:24 AM, Charles Lepple wrote: > On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote: > >>

Mandi! L.P.H. van Belle via samba In chel di` si favelave... > Im not really sure here. Seems that nfs-config crate the file correctly: root at vdmpp1:/srv# cat /run/sysconfig/nfs-utils PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS=" 8" RPCMOUNTDARGS="--manage-gids" STATDARGS="" RPCSVCGSSDARGS="-vvvvv -n" but the nfs(s) systemd unit file