Hi Billy, switching back this thread to -upsdev 2012/2/27 William R. Elliot <bill at wreassoc.com>:> I have been able to set the 'FSD' from the driver and it is picked up by > upsmon.? That gives me the functionality that I was asked to put in the > driver.? If that is against the rules then I'll make an adjustment when the > allowed method is defined.? :-)yup, that's against the tables of the law ;-p more seriously, the right way to do this is to set the status to "OB LB", which will trigger upsmon to add FSD. the reason is that, in master / slave(s) setup, this allows upsmon to do the job, and notify slaves. so, as long as you just catch something that implies the FSD status using "OB LB", everything is fine. don't hesitate to post your patch on -upsdev to get feedback and adjustment request, which is needed before we can merge your contrib. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -- Conseiller Municipal - Saint Bernard du Touvet
On Feb 28, 2012, at 3:44 AM, Arnaud Quette wrote:> Hi Billy, > > switching back this thread to -upsdev > > 2012/2/27 William R. Elliot <bill at wreassoc.com>: >> I have been able to set the 'FSD' from the driver and it is picked up by >> upsmon. That gives me the functionality that I was asked to put in the >> driver. If that is against the rules then I'll make an adjustment when the >> allowed method is defined. :-) > > yup, that's against the tables of the law ;-p > more seriously, the right way to do this is to set the status to "OB > LB", which will trigger upsmon to add FSD. > the reason is that, in master / slave(s) setup, this allows upsmon to > do the job, and notify slaves. > > so, as long as you just catch something that implies the FSD status > using "OB LB", everything is fine. > > don't hesitate to post your patch on -upsdev to get feedback and > adjustment request, which is needed before we can merge your contrib.Arnaud, I looked at some of the existing NUT code for handling FSD, and I think it is a slightly more accurate representation of what is going on when an external source starts a shutdown on an UPS. See the following thread: http://article.gmane.org/gmane.comp.monitoring.nut.devel/5882 My thought is that the external shutdown signal may happen well before the battery is low. I don't see a reason why a driver couldn't set FSD, other than simply by convention. -- Charles Lepple clepple at gmail
Arnaud' the original reason for this was due to having multiple communication channels to the UPS. It is possible for the non-NUT channel to start a UPS delayed shutdown that the NUT master and slaves need to know about. Charles suggested using FSD rather than OB LB to avoid confusing messages about a low battery in the log when there isn't a low battery. Upsmon still does the work, I think, it is just that the driver is setting the flag for upsmon to act on rather than upsmon seeing OB LB and doing the same thing. Can the rules be adjusted? Bill At 03:44 AM 2/28/2012, Arnaud Quette wrote:>Hi Billy, > >switching back this thread to -upsdev > >2012/2/27 William R. Elliot <bill at wreassoc.com>: > > I have been able to set the 'FSD' from the driver and it is picked up by > > upsmon.? That gives me the functionality that I was asked to put in the > > driver.? If that is against the rules then > I'll make an adjustment when the > > allowed method is defined.? :-) > >yup, that's against the tables of the law ;-p >more seriously, the right way to do this is to set the status to "OB >LB", which will trigger upsmon to add FSD. >the reason is that, in master / slave(s) setup, this allows upsmon to >do the job, and notify slaves. > >so, as long as you just catch something that implies the FSD status >using "OB LB", everything is fine. > >don't hesitate to post your patch on -upsdev to get feedback and >adjustment request, which is needed before we can merge your contrib. > >cheers, >Arnaud >-- >Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com >Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ >Debian Developer - http://www.debian.org >Free Software Developer - http://arnaud.quette.free.fr/ >-- >Conseiller Municipal - Saint Bernard du Touvet-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120228/b4796ca4/attachment.html>
Maybe Matching Threads
- Issue with slave FSD notification on Windows port of NUT
- Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)
- System with MGE UPS shuts down too early
- "upsmon -c fsd" cause system shutdown
- Formalize use of the FSD flag (was: NUT driver update process...)