Displaying 10 results from an estimated 10 matches for "nutuser".
Did you mean:
ntuser
2006 Jun 07
1
RPM spec file
...file. Please find a copy of the slightly updated spec file
attached. The changes are documented at the bottom of the spec file.
Regards,
Will
-------------- next part --------------
# don't know how different I can do this
%define majorver 2.0
%define version 2.0.3
%define relver 1
%define nutuser nutmon
# what version of RH are we building for?
%define redhat7 1
%define redhat6 0
# Options for Redhat version 6.x:
# rpm -ba|--rebuild --define "rh6 1"
%{?rh6:%define redhat7 0}
%{?rh6:%define redhat6 1}
# some systems dont have initrddir defined
%{?_initrddir:%define _initrddir /e...
2018 Jun 27
2
upsmon Can not initialize SSL context (letsencrypt) #563
Hello all.
Thx for the log-tip.
It was a access right violation on /etc.../letsencrypt/....cert . The folder was own by root:root
Had to create a group nutusers including root and my nut users. After that, had to change the chmod for the folder from 755 to 775
Now, running upsc -l
Init SSL without certificate database
850PRO
Witch is better. But still problématic wuth the init ssl database warning.
________________________________
De : Nut-upsuser &...
2013 Sep 25
0
RedHat init script
...t/upsd 2012-07-31 10:38:56.000000000 -0700
+++ /etc/init.d/upsd 2013-09-24 16:36:42.000000000 -0700
@@ -58,16 +58,16 @@
start)
# new style drivers uses 'upsdrvctl'
echo -n "NUT Starting UPS model drivers: "
- # starting ase nut user
+ # starting as nut user
daemon --user $NUTUSER `which upsdrvctl` start
- echo
if [ $? -eq 0 ]; then
+ echo
echo -n "NUT Starting UPS daemon: "
- # starting ase nut user
+ # starting as nut user
daemon upsd -u $NUTUSER
- echo
touch /var/lock/subsys/upsd
fi
+ echo
;;
stop)
@@ -98,9 +98,6 @@
;;
status)
- #...
2018 Jun 28
0
upsmon Can not initialize SSL context (letsencrypt) #563
On Wed, 27 Jun 2018, tech wrote:
> It was a access right violation on /etc.../letsencrypt/....cert . The folder was own by root:root
> Had to create a group nutusers including root and my nut users. After that, had to change the chmod for the folder from 755 to 775
>
> Now, running upsc -l
>
> Init SSL without certificate database
> 850PRO
>
> Witch is better. But still problématic wuth the init ssl database warning.
Without using SSL...
2019 Apr 03
2
upssched Not Running
...M SYSLOG+WALL
> NOTIFYFLAG NOPARENT SYSLOG+WALL
> RBWARNTIME 43200
> NOCOMMWARNTIME 300
> FINALDELAY 60
> CERTVERIFY 0
> FORCESSL 0
>
> Another thing worth noting, and probably unrelated to this specific
> scenario, is somehow I have a "nut" user and a "nutuser" user. I don't
> know how that happened. On my Debian setup (details in previous
> message), user "nutuser" does not work, where the "nut" user does work.
> Perhaps this happened during one of the incremental updates over the
> years and I thought I...
2006 Aug 25
2
Add USB vendor/device id for Belkin F6C120-UNV
I just moved my UPS over from serial to USB and found that I needed to
add it to the hotplug USB list to make things work.
Belkin F6C120-UNV
- Bus 002 Device 004: ID 050d:0912 Belkin Components
It seems to be working OK on 2.0.4 with newhidups. Attached is a patch
which I think should add the appropriate device id's in the right places
to the trunk code.
Jon
-------------- next part
2019 Mar 30
2
upssched Not Running
2019 Apr 03
0
upssched Not Running
2018 Jun 19
2
upsmon Can not initialize SSL context (letsencrypt) #563
those mails list are from last century but i give it a try !
created : https://github.com/networkupstools/nut/issues/563
Hello all,
Trying to run an EATON 850pro via USB on a Debian Stretch Stable.
I have letsencrypt certificate installed and working.
When trying to manage the EATON device, i got:
upsmon Can not initialize SSL context
When 850pro is connected via USB, i can:
lsusb
Bus 009
2007 Feb 03
2
Powerware 5110
I have an FC5 system with a powerware 5110 usb ups.
The system seems to find the UPS
------------------------------
[root@b1 src]# lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0592:0002 Powerware Corp.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
-------------------------------
[root@b1