search for: baldiniebaldini

On Oct 2, 2015, at 9:01 PM, Davide Baldini <baldiniebaldini at gmail.com> wrote: > > When I manually unplug the mains, the computer waits 3 minutes, shutdowns, and there it stays. As per the above commands, issued from ups_events.sh, it is instead supposed to boot up after 6 minutes (360 / 60 seconds) counted from t?, the moment of the unplug. Aft...

On Wed, 14 Oct 2015, Davide Baldini wrote: >> Is there any command in the list provided by "upscmd -l myups" which is >> accepted by this UPS? > > None of the command sin the list successfully completes, not even > beeper.toggle. It looks as if the problem is more general than turning off the UPS. The command mechanism is broken. > I added -q and -D to

Hello, my Atlantis UPS (model on "subject" line) fails to cycle off the outlet power after a power failure on the mains followed by an automatic shutdown of the computer. The UPS simply remains always on, preventing the computer from restarting. ** Setup: ** Nut version 2.7.2 Nut driver blazer_usb Linux 4.1.1 The config files are pretty default; the peculiar customization is

Guess I can assume that my OnePower A03-S1001 just doesn't support the shutdown command. Might this be the case? -- Davide

Thanks Roger, the full output of upsc ${myups} is at https://pastebin.mozilla.org/8849188 ; in particular: ups.delay.shutdown: 30 ups.delay.start: 180 However, the UPS does not shut down, not immediately nor well after the timeout of the command: upscmd -u admin -p mypass myups shutdown.return 360 -- Davide

On 10/14/2015 10:17 AM, Roger Price wrote: > What does "ps aux | grep ups" report? ps aux | grep ups nut 2902 0.0 0.0 20588 1140 ? Ss 00:10 0:02 /lib/nut/nutdrv_qx -a myups nut 2946 0.0 0.0 37632 1428 ? Ss 00:10 0:00 /lib/nut/upsd root 2970 0.0 0.0 37616 1436 ? Ss 00:10 0:00 /lib/nut/upsmon root 2973

On 10/14/2015 12:18 PM, Roger Price wrote: > Is there any command in the list provided by "upscmd -l myups" which is accepted > by this UPS? None of the command sin the list successfully completes, not even beeper.toggle. My list: # upscmd -l myups Instant commands supported on UPS [myups]: beeper.toggle - Toggle the UPS beeper load.off - Turn off the load

On 10/14/2015 06:11 PM, Roger Price wrote: > Is /etc/init.d/nut-client a Bash/Dash script? Is it possible to add the option to > the call of the driver in this script? Looks like some options can be passed: /etc/init.d/nut-client is a dash script and when it is started or restarted, it executes: start-stop-daemon -S -q -p $upsmon_pid -x $upsmon \ -- $UPSMON_OPTIONS >/dev/null

Can two wineserver share the same virtualdesktop? I got nearly to an impasse: one windows application (A) must run continuously without interruption, while (B) is supposed to respawn frequently and interact with (A). Well, whatever (A) application is has absolutely no influence on troubles, but if (B) is autoHotKey (..yes i need that stuff under debian) it's execution times get delayed

I think autoHotKey leaves some session-long alterations to wine status when it quits, somehow slowing its own further executions. A check with taskmgr.exe shows autoHotKey quits properly with no processes hanged up. I have absolutely no idea of what it keeps from tidying up. How can processes alterations be tracked?

I changed the driver from blazer_usb to nutdrv_qx, by editing /etc/nut/ups.conf. To apply changes, I did: # service nut-server restart # service nut-client restart Then I've run a second test, this time simpler than the first one described in my previous email; the test only consists in toggling off/on a wall switch which controls power to the UPS. This way, electric ground remains