search for: nutdev

...-s /usr/local/ups/etc /etc/nut md /lib/ups; cp lib/* /lib/ups/ cp libexec/* /usr/libexec cp sbin /sbin/ ln -s /usr/local/ups/lib /lib/ups [Configuration details...] [Why reinvent the wheel and risk a problem?] nut-scanner -qUN > /etc/nut/ups.conf [Configuration of /etc/nut/ups.conf becomes:] [nutdev-usb1] driver = "usbhid-ups" port = "auto" vendorid = "0764" productid = "0501" product = "SL Series" vendor = "CPS" # bus = "001" # device = "049" # busport = "003" [Configuration of /etc/nut/nut.conf:] #MODE...

...; enabled; preset: enabled) Drop-In: /etc/systemd/system/nut-driver at malaysia.service.d ??nut-driver-enumerator-generated-checksum.conf Active: activating (auto-restart) (Result: exit-code) since Tue 2023-07-04 19:03:20 CDT; 9s ago Process: 14926 ExecStart=/bin/sh -c NUTDEV="`/usr/libexec/nut-driver-enumerator.sh --get-device-for-service malaysia`" && [ -n "$NUTDEV" ] || { echo "FATAL: Could not find a NUT device section for service unit malaysia" >&2 ; exit 1 ; } ; /sbin/upsdrvctl start "$NUTDEV" (code=exited,...

...t; Drop-In: /etc/systemd/system/nut-driver at malaysia.service.d > ??nut-driver-enumerator-generated-checksum.conf > Active: activating (auto-restart) (Result: exit-code) since Tue > 2023-07-04 19:03:20 CDT; 9s ago > Process: 14926 ExecStart=/bin/sh -c > NUTDEV="`/usr/libexec/nut-driver-enumerator.sh --get-device-for-service > malaysia`" && [ -n "$NUTDEV" ] || { echo "FATAL: Could not find a NUT > device section for service unit malaysia" >&2 ; > exit 1 ; } ; /sbin/upsdrvctl start "$NUTDEV" (...

...? ?Drop-In: /etc/systemd/system/nut-driver at malaysia.service.d > ? ? ? ? ? ? ? ??nut-driver-enumerator-generated-checksum.conf > ? ? ? Active: activating (auto-restart) (Result: exit-code) since Tue 2023-07-04 19:03:20 CDT; 9s ago > ? ? ?Process: 14926 ExecStart=/bin/sh -c NUTDEV="`/usr/libexec/nut-driver-enumerator.sh --get-device-for-service > malaysia`" && [ -n "$NUTDEV" ] || { echo "FATAL: Could not find a NUT device section for service unit malaysia" >&2 ; > exit 1 ; } ; /sbin/upsdrvctl start "$NUTDEV&quot...

...on SuSE distro and adapted init-scripts from package for > this distro style. Send you them with hope that you find them useful > for other users and may be include them in NUT package. > And one question. When i try use secure scheme that describe in > 'docs/FAQ' (with 'nutdev' and 'nutsrv' users) i get problem when > i tested power race conditions. When i run command > /usr/local/ups/sbin/upsmon -c fsd > at the end of 'halt' script i see: > --------------------------------------------------- > > Network UPS Tools - UPS drive...

...system/nut-driver at malaysia.service.d > > ??nut-driver-enumerator-generated-checksum.conf > > Active: activating (auto-restart) (Result: exit-code) since > Tue 2023-07-04 19:03:20 CDT; 9s ago > > Process: 14926 ExecStart=/bin/sh -c > NUTDEV="`/usr/libexec/nut-driver-enumerator.sh --get-device-for-service > > malaysia`" && [ -n "$NUTDEV" ] || { echo "FATAL: Could not find a > NUT device section for service unit malaysia" >&2 ; > > exit 1 ; } ; /sbin/upsdrvctl start &qu...

...m/nut-driver at malaysia.service.d > >? ? ? ? ? ? ? ? ? ? ??nut-driver-enumerator-generated-checksum.conf > >? ? ? ? ? ? Active: activating (auto-restart) (Result: exit-code) since Tue 2023-07-04 19:03:20 CDT; 9s ago > >? ? ? ? ? ?Process: 14926 ExecStart=/bin/sh -c NUTDEV="`/usr/libexec/nut-driver-enumerator.sh --get-device-for-service > >? ? ?malaysia`" && [ -n "$NUTDEV" ] || { echo "FATAL: Could not find a NUT device section for service unit > malaysia" >&2 ; > >? ? ?exit 1 ; } ; /sbin/upsdr...

I'm trying to work out how to set up a custom udev rule to override permissions on serial ports (/dev/ttyS* and /dev/ttyUSB*) on CentOS 5.3 The default rule, in /etc/udev/rules.d/50-udev.rules has the line: KERNEL=="tty[A-Z]*", NAME="%k", GROUP="uucp", MODE="0660" and I would like the mode to be 0666 Various docs on web say that you

Digitus DN-170014 root at home:/home/scripts# upsc ups device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.4 driver.version.internal: 0.04 ups.mfr: Richcomm dry-contact to USB solution ups.model: UPS USB MON V1.4

Hello! I've ran into this annoying issue when setting up a new server. I have an APC SmartUPS hooked up on a USB-serial converter on /dev/ttyUSB0. This works nicely, until: hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling... pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 usb 3-1: pl2303 converter now attached to ttyUSB1 apcsmart gets into an infinite loop of this: