If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? NOTIFYFLAG ONLINE SYSLOG NOTIFYFLAG ONBATT SYSLOG NOTIFYFLAG LOWBATT SYSLOG NOTIFYFLAG FSD SYSLOG NOTIFYFLAG COMMOK SYSLOG NOTIFYFLAG COMMBAD SYSLOG NOTIFYFLAG SHUTDOWN SYSLOG NOTIFYFLAG REPLBATT SYSLOG NOTIFYFLAG NOCOMM SYSLOG NOTIFYFLAG NOPARENT SYSLOG The 'wall' messages (message.exe) don't pop-up and worst case, I had so many message.exe's running that all memory was consumed. This is because Windows hasn't allowed services to interact with the desktop for some time. Maybe it works pre-Vista. The worst case is probably because upsmon will log a problem every poll interval until it's corrected. Intended? I don't mind *not* having a tray notification app, particularly because I've had back luck with those spamming the desktop with pop-ups. Not sure why these things don't have a pop-up limiter. A single message of each type up at one time would be enough. Thank you
Kris Jordan wrote, On 2/24/2014 10:13 PM:> The worst case is probably because upsmon will log a problem every > poll interval until it's corrected. Intended?Correction, poll interval --> POLLFREQ (in upsmon.conf).
On Feb 25, 2014, at 1:13 AM, Kris Jordan wrote:> If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? > > NOTIFYFLAG ONLINE SYSLOG > NOTIFYFLAG ONBATT SYSLOG > NOTIFYFLAG LOWBATT SYSLOG > NOTIFYFLAG FSD SYSLOG > NOTIFYFLAG COMMOK SYSLOG > NOTIFYFLAG COMMBAD SYSLOG > NOTIFYFLAG SHUTDOWN SYSLOG > NOTIFYFLAG REPLBATT SYSLOG > NOTIFYFLAG NOCOMM SYSLOG > NOTIFYFLAG NOPARENT SYSLOG > > The 'wall' messages (message.exe) don't pop-up and worst case, I had so many message.exe's running that all memory was consumed. This is because Windows hasn't allowed services to interact with the desktop for some time. Maybe it works pre-Vista. > > The worst case is probably because upsmon will log a problem every poll interval until it's corrected. Intended? > > I don't mind *not* having a tray notification app, particularly because I've had back luck with those spamming the desktop with pop-ups. Not sure why these things don't have a pop-up limiter. A single message of each type up at one time would be enough. > > Thank youEmelien, It looks like you have been working on that branch. Is this something you can merge in? -- Charles Lepple clepple at gmail
Hi all, 2014-02-28 15:10 GMT+01:00 Charles Lepple <clepple at gmail.com>:> On Feb 25, 2014, at 1:13 AM, Kris Jordan wrote: > > > If there is a next Windows release, perhaps the default NOTIFYFLAG's > should be adjusted? > > > > NOTIFYFLAG ONLINE SYSLOG > > NOTIFYFLAG ONBATT SYSLOG > > NOTIFYFLAG LOWBATT SYSLOG > > NOTIFYFLAG FSD SYSLOG > > NOTIFYFLAG COMMOK SYSLOG > > NOTIFYFLAG COMMBAD SYSLOG > > NOTIFYFLAG SHUTDOWN SYSLOG > > NOTIFYFLAG REPLBATT SYSLOG > > NOTIFYFLAG NOCOMM SYSLOG > > NOTIFYFLAG NOPARENT SYSLOG > > > > The 'wall' messages (message.exe) don't pop-up and worst case, I had so > many message.exe's running that all memory was consumed. This is because > Windows hasn't allowed services to interact with the desktop for some time. > Maybe it works pre-Vista. > > > > The worst case is probably because upsmon will log a problem every poll > interval until it's corrected. Intended? > > > > I don't mind *not* having a tray notification app, particularly because > I've had back luck with those spamming the desktop with pop-ups. Not sure > why these things don't have a pop-up limiter. A single message of each type > up at one time would be enough. > > > > Thank you > > > Emelien, > > It looks like you have been working on that branch. Is this something you > can merge in? > > -- > Charles Lepple >Yes I can look at this. BR, Emilien -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140303/b36501d9/attachment.html>