I pulled the AC power and let the system shutdown. ?Everything appears to have gone well. ?Checked thesystem log and found the following sequence of events: [CODE] Jul 15 10:20:50 debian upsmon[678]: UPS 1 on batteryJul 15 10:26:05 debian upsmon[678]: UPS 1 battery is lowJul 15 10:26:05 debian upsd[675]: Client upsmon at 127.0.0.1 set FSD on UPS [Asium_p700]Jul 15 10:26:05 debian upsmon[678]: Executing automatic power-fail shutdownJul 15 10:26:05 debian upsmon[678]: Auto logout and shutdown proceedingJul 15 10:26:10 debian systemd-shutdownd[1973]: Shutting down at Wed 2015-07-15 10:26:10 CST (poweroff)...Jul 15 10:26:10 debian systemd-shutdownd[1973]: Creating /run/nologin, blocking further logins...Jul 15 10:26:10 debian rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="532" x-info="http://www.rsyslog.com"] exiting on signal 15. [CODE] So, the system shut down and turned off the UPS, which is exactly what I would have expected. ?Also, when I?reconnected the AC power the system did NOT automatically start up, which again is what I would have wanted,and hoped for. ? So, in conclusion, NUT appears to be working correctly. ?Just wish I new why I wasn't getting messages. ?But I?can live with the way it is. ?Thanks for all your help and a big thank you to the developers. ? John "Science is organized common sense. Philosophy is organized piffle" -attributed to Bertrand Russel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150715/dbc154bd/attachment.html>
On Jul 15, 2015, at 12:38 PM, john hart <jsamcr at yahoo.com> wrote:> So, the system shut down and turned off the UPS, which is exactly what I would have expected. Also, when I > reconnected the AC power the system did NOT automatically start up, which again is what I would have wanted, > and hoped for.Good to hear!> So, in conclusion, NUT appears to be working correctly. Just wish I new why I wasn't getting messages. But I > can live with the way it is. Thanks for all your help and a big thank you to the developers.Not sure if you mentioned, but if you run something like "echo hi | wall", does it broadcast a message? If not, I'd say that's a bug in wall, but you could configure upsmon to run a different program to send a message. -- Charles Lepple clepple at gmail
Tried 'echo hi | wall' and no message. ?I looked at 'wall -h'
and it would seem that it is supposed to. ?I eventried ?' wall
?[<filename> | <message>] ' ?and got nothing. ? Not sure what
that means, as when using theNUT-Monitor program I get banners and a
'message' on the system try. ? Strange !
John ??"Science is organized common sense. Philosophy is organized
piffle"
-attributed to Bertrand Russel
From: Charles Lepple <clepple at gmail.com>
To: john hart <jsamcr at yahoo.com>
Cc: NUT Developers <nut-upsdev at lists.alioth.debian.org>
Sent: Wednesday, July 15, 2015 6:12 PM
Subject: Re: Good news
On Jul 15, 2015, at 12:38 PM, john hart <jsamcr at yahoo.com> wrote:
> So, the system shut down and turned off the UPS, which is exactly what I
would have expected.? Also, when I
> reconnected the AC power the system did NOT automatically start up, which
again is what I would have wanted,
> and hoped for.?
Good to hear!
> So, in conclusion, NUT appears to be working correctly.? Just wish I new
why I wasn't getting messages.? But I
> can live with the way it is.? Thanks for all your help and a big thank you
to the developers.?
Not sure if you mentioned, but if you run something like "echo hi |
wall", does it broadcast a message? If not, I'd say that's a bug in
wall, but you could configure upsmon to run a different program to send a
message.
--
Charles Lepple
clepple at gmail
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150716/9ae46820/attachment-0001.html>