search for: monslave

...ild/ports/nut/files/nut.sh.in To address your original concern (adding remote users for monitoring), I would edit the RC file, which is probably /usr/local/etc/rc.d/nut, to include something like this at the end of the nut_mkconf() function: cat <<__EOF__ >> ${nut_upsd_users} [monslave] password = abcd upsmon slave __EOF__ (Be sure to add it after the line containing "... > ${nut_upsd_users}") Of course, this will be lost when you upgrade NAS4Free, but maybe you can convince one of the developers to add this as a core feature, such t...

Thanks, the strange is that I could set in this way the master user. At NAS4Free forum cannot get help, I presented the problem there too, but no real help. On Thu, Aug 22, 2013 at 2:19 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > > > Having the next problem, manually adding via WinSCP in the upsd.users > file the

...; > To address your original concern (adding remote users for monitoring), I > would edit the RC file, which is probably /usr/local/etc/rc.d/nut, to > include something like this at the end of the nut_mkconf() function: > > cat <<__EOF__ >> ${nut_upsd_users} > [monslave] > password = abcd > upsmon slave > __EOF__ > > (Be sure to add it after the line containing "... > ${nut_upsd_users}") > > Of course, this will be lost when you upgrade NAS4Free, but maybe you can > convince one of the developers...

...> > On Aug 26, 2013, at 8:08 AM, Incze Andras wrote: > >> Here is the result with the code inserted into script and the modified script too > > I didn't realize that the "xml" command didn't add a trailing newline, and I should not have indented the "[monslave]" line. > > The attached script should work better. > > -- > Charles Lepple > clepple at gmail > -------------- next part -------------- A non-text attachment was scrubbed... Name: nut Type: application/octet-stream Size: 3494 bytes Desc: not available URL: <http://...

...xx7/32 ACL nutSlave2 xx.xx.xx.xx3/32 ACCEPT localhost nutMaster nutSlave1 nutSlave2 REJECT all upsd.users ---------- $ grep -v "#" upsd.users [upsadmin] password = **** allowfrom = nutMaster actions = SET instcmds = ALL [monmaster] password = **** allowfrom = nutMaster upsmon master [monslave-nutSlave1] password = **** allowfrom = nutSlave1 upsmon slave [monslave-nutSlave2] password = **** allowfrom = nutSlave2 upsmon slave upsmon.conf ----------- $ grep -v "#" upsmon.conf MONITOR apcups at nutMaster.domain.uk 1 monmaster **** master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/sh...

...h.in > > To address your original concern (adding remote users for monitoring), I would edit the RC file, which is probably /usr/local/etc/rc.d/nut, to include something like this at the end of the nut_mkconf() function: > > cat <<__EOF__ >> ${nut_upsd_users} > [monslave] > password = abcd > upsmon slave > __EOF__ > > (Be sure to add it after the line containing "... > ${nut_upsd_users}") > > Of course, this will be lost when you upgrade NAS4Free, but maybe you can convince one of the developers to...

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

hi: my testing server has two power supply and attach to two ups. one of the ups is connect to the server with usb. my upsmon.conf like below: # for two ups MONITOR ftups at localhost 1 monmaster nutmaster master MONITOR ftups at 10.1.1.2 1 monslave nutslave slave MINSUPPLIES 1 # for early shutdown NOTIFYFLAG ONBATT EXEC+WALL+SYSLOG NOTIFYFLAG ONLINE EXEC+WALL+SYSLOG NOTIFYCMD /usr/sbin/upssched the early shutdown script use "upsmon -c fsd" to set FSD to master ups. but when testing, the "upsmon -c fsd" not only set...

...; > To address your original concern (adding remote users for monitoring), I > would edit the RC file, which is probably /usr/local/etc/rc.d/nut, to > include something like this at the end of the nut_mkconf() function: > > cat <<__EOF__ >> ${nut_upsd_users} > [monslave] > password = abcd > upsmon slave > __EOF__ > > (Be sure to add it after the line containing "... > ${nut_upsd_users}") > > Of course, this will be lost when you upgrade NAS4Free, but maybe you can > convince one of the developers...

...g in upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL webinterface 192.168.0.2/32 ACL slave 192.168.50.22/32 ACCEPT localhost ACCEPT webinterface ACCEPT slave REJECT all and in upsd.users: [monmaster] password = secret0 allowfrom = localhost upsmon master [monslave] password = secret1 allowfrom = slave upsmon slave [admin] password = secret2 actions = SET instcmds = ALL allowfrom = webinterface Although upsd runs in a secured, private network, I would like to restrict the access. However, afte...

...UPSA is "alive/no need shutdown" when it is stale, but I want to assume UPSB is "dead/need shutdown" when it is stale. to accomplish that, maybe uspmon can have a flag to indicate that: MONITOR ftups at localhost 1 monmaster passmaster master alive MONITOR ftups at 10.1.1.1 1 monslave nutslave slave dead maybe there are other situations that people want to declare "stale" ups as "dead/need shutdown".. Regards, tbskyd

...: ondelay=6 ------------- upsd.conf:LISTEN 127.0.0.1 3493 upsd.conf:LISTEN 192.168.7.105 3493 ----------- upsd.users:[root] upsd.users:password=**password** upsd.users:actions=set upsd.users:instcmds=all upsd.users:[monmaster] upsd.users:password=***password* upsd.users:upsmon master upsd.users:[monslave] upsd.users:password=**password** upsd.users:upsmon slave upsd.users:[piebnsrv] upsd.users:password=**password** upsd.users:upsmon slave ------------ upsmon.conf: MONITOR ippon at localhost 1 monmaster bggjy master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /sbin/upssched...

...r mode you use, don't forget to modify passwords in the created files (users section, either in users.conf or in nut.conf if you used the single file mode). By default, the UPS declared by upsconfig is nammed myups, the admin nutadmin, the upsmon master monmaster and the upsmon slave is nammed monslave, and the passwords are put to "!", that is to say invalide password, and users having such a password (or an empty password) will be ignored. By default, upsconfig use CONFPATH/base_config directory to find the nut.conf template to generate the configuration file (/usr/local/nut-new-conf...

...S_USER root HOSTS.CONF MONITOR ups at localhost "IBM-eSERVER" UPSD.USERS [admin] password = mypassword! actions = SET instcmds = ALL [monuser] password = mypassword! allowfrom = localhost fileserver upsmon master [monslave] password = mypassword! allowfrom = firewall The version of nut is from the Ubuntu 8.10 repositories (2.2.2) and the server is running Ubuntu-Server 8.10 So what have I got so horribly wrong for things to make "ME" a little grumpy! so any advice on this would renew my sanity! Thanks......