Ciprian Vizitiu wrote:
Ok, most likely it's me but I'm out of ideas right now; last night my very
first attempt was to use NOTIFYCMD with
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC
... and the very simple script for sending
Ciprian Vizitiu wrote:
Another thing: am I supposed to be able to see some activity in the
PIPEFN/LOCKFN folder during the declared AT timings? 'coz there is none!
:-o And upssched.conf has the same perms like all other files in /etc/ups/
You should see some activity there (the PIPEFN is
Really? Silly me then; Megatec looked like a fairly evolved protocol so I
was afraid that, since no RTS/CTS signaling was in place into the
manufacturer supplied cable, maybe plain RX/TX/GND won't do. For example
Minicom showed Offline all the time during the tests.
Most (if not all) smart
2.0.3 is biting me bad in the upssched department so I
guess I'll have
to go for SVN. :-(
Like how? There have not been too many major bugs in upssched
and as far as I know this has not changed significantly (if
at all) since nut-2.0.3.
Could you please describe what is not
... Of course the line:
AT ONBATT [EMAIL PROTECTED] START-TIMER onbattwarn 60 AT
ONLINE [EMAIL PROTECTED] CANCEL-TIMER onbattwarn
Should read:
AT ONBATT [EMAIL PROTECTED] START-TIMER onbattwarn 60
AT ONLINE [EMAIL PROTECTED] CANCEL-TIMER onbattwarn
So the mistake is not there.
Another
Hi everybody,
I've got an Unitek iZi UPS 525 with a serial interface. The supplied cable
looks fairly simple: RX-RX , TX-TX and GND-GND. Using this cable and
Minicom with 2400 8N1 I'm able to issue commands to the UPS using the
Megatec Protocol
6 matches
Mail list logo
