I suspected as much. For some reason installing nut using apt didn't dl all the
config files. SuSE isn't the greatest with apt (nor YAST). Anyway I copied over
the old config files from 1.2.2 server to the 2.0.2 server, changed ACCESS to
ACCEPT and shangri la.
Thanks a milion
>>> "Charles Le
On 9/7/06, Chris Boyd <[EMAIL PROTECTED]> wrote:
Anyone have any ideas?
Not for NUT 1.2, no. That version is very old, and a number of
fundamental changes have been made since then.
--
- Charles Lepple
___
Nut-upsuser mailing list
Nut-upsuser@lists.
Anyone have any ideas?
Sorry I'm just stuck at this point.
>>> "Chris Boyd" <[EMAIL PROTECTED]> 09/05/06 3:09 >>>
OK I've changed to a different machine as I don't think it install all of nut.
Now I'm working with nut-1.2.2
I changed the driver to newapc and it's now finding the RT 3000 corre
OK I've changed to a different machine as I don't think it install all of nut.
Now I'm working with nut-1.2.2
I changed the driver to newapc and it's now finding the RT 3000 correctly.
I'm still getting the reject TCP in messages:
upsd[17078]: Rejecting TCP connection from 10.133.1.49
Sep 5 1
On 9/4/06, Chris Boyd <[EMAIL PROTECTED]> wrote:
stat /etc/ups/upsd.conf: No such file or directory
This is key.
ups.conf configures the drivers, whereas upsd.conf controls access to
the driver from the network.
If you are setting up a standalone system, you can use this as a
starting point f
I have a Dell PE 2850 connected via 940-0024C cable to serial port on the UPS
mentioned above.
I've used apt-get to install nut-2.0.2-3 and attempted to configure based on
the documentation.
So far I'm getting the following when I try to start ups daemon:
server:/etc/ups # /etc/init.d/ups sta
6 matches
Mail list logo
