Lyle,
> Second - I went in a edited the /etc/sysconfig/ups file to > set the HOST > variable to the IP address of my UPS master and then > restarted the UPS > deamons. When I test the configuration by pulling the UPS > cord, I get a > message displayed on the Master LCD screen and a power fail > message sent to > a logged in telnet session. Nothing happens on the Slave > system (no lcd > message and no terminal message). How can I test that the > salve is working > correctly. The slave should display the same LCD messages that the master displays. If it is not, then it is not communicating with the master. I don't have time right now to detail out how the config files should look, but that documentation should be in the smartups documentation. If you cannot figure it out, pop me another mail and I'll try to look it up on Monday. - Lyle
I had a mistake in my /etc/ups/uspd.conf file. Once I had corrected it the slave monitoring of the Master did work fine (still had the problem with set-up of the IP address through the LCD panel). This does point up a problem with the approach of configuring the UPS agent through the LCD panel. In order to properly configure the slaves, you need to create the proper configuration entires in /etc/ups/upsd.conf on the Master and /etc/ups/hosts.conf and /etc/ups/upmon.conf on the Slaves. This is not done in the current package In addition, you would need to extend it to provide for entry of the password. As of today, you are required to manually edit these files. This should be covered in the documentation (the existing doc does not even refer to the smartupstools documentation). Alternatively, remove the Slave functionality from the existing package.
I have some time so I am thinking of installing the current version of NUT on my Cobalts - they will be adding the early shutdown feature that I am looking for. If you give me some documentation on the lcd panel calls, I will add the power status messages on the lcd. I hate to just copy your code, since I don't know what side effects the calls may have (if any).
thanks, mike dierker Michael Dierker PineTree Consulting Email: mdierker@xxxxxxxxxxx