Hi Arnaud! > Hi Denis, > > the Windows port is not yet fully functional, nor as mature as the Unix > versions. > Currently, upssched is not working.
It is indeed sad... > So you can only use the simple scheduling approach: > http://www.networkupstools.org/docs/user-manual.chunked/ar01s07.html#_the_simple_approach_using_your_own_script > > I can't give any date on a fix for this point though, since it's bound to > Eaton resource allocation (which is sponsoring this feature). Unfortunately, NOTIFYCMD with custom script doesn't work without starting additional "upsmon" process (as I wrote in original message). In other words, there is no action by default. As I run one more "upsmon", script is executing successfully... That is strange, isn't? > > 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/ With the best wishes, Denis _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
