search for: forceshutdown

2010/10/13 Vitaly Lavrov > I found bug in nut/drivers/megatec.c - force shutdown may dont work. > See patch. > could you please give a try to blazer, since it is set to replace megatec with 2.6.0. Arjen will quite probably comment on your patch usefulness within the blazer scope. thanks for your contrib. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton -

...if (broken_driver) { printf("Fatal error: broken driver. It probably needs to be con\verted.\n"); printf("Search for 'broken_driver = 1' in the source for more d\etails.\n"); exit(EXIT_FAILURE); } if (do_forceshutdown) forceshutdown(); The call to setup_signals() does not reference any files in the statepath directory. memset() does not reference any files in the statepath directory upsdrv_initups() does not reference any files in the statepath directory ... at least not for cyberpower.c nor...

...in the shutdown-restore and load.off section. (I saw in git that there has been changes already not to send the "Rxxx" part when shutdown without return has been requested - that's what I found, too, does the proprietary driver.) There is a change in main.c, too, because sending the forceshutdown() before upsdrv_initinfo did not read the additional protocol parameter so the ups was not shut down when upsdrvctl shutdown was called from the halt script in init.d. So I moved the forceshutdown below the initinfo. CU, Gernot -------------- next part -------------- A non-text attachment was scru...

I have a TrippLite AVR550U that my company uses several individual Linux boxes in one large system, all running Ubuntu 18.04LTS, and all will be using the package version of nut - 2.7.4. In my scenario, our usage case is for the PCs to all shut down, followed by the individual UPSes, when mains power is removed from the whole system. (This isn't a typical setup for UPS, but it's what

...mmediately report low battery > if you put it in test mode (which it does every two weeks on its own). Nut > would then immediately shut down the Linux system, and once that was done, > it would proceed to force a shutdown of all the other UPSs. > > The smoking gun is in upsmon's forceshutdown(): > > /* set FSD on any "master" UPS entries (forced shutdown in progress) */ > for (ups = firstups; ups != NULL; ups = ups->next) > if (flag_isset(ups->status, ST_MASTER)) { > isamaster = 1; >...

...> UPSs. This is by design. If the power is really out, the systems that are connected to the NUT server *must* be shutdown, if the NUT server must go down. Otherwise, they would not be able to be shutdown if the UPS that feeds them is low on battery. >> The smoking gun is in upsmon's forceshutdown(): >> >> /* set FSD on any "master" UPS entries (forced shutdown in progress) */ >> for (ups =3D firstups; ups !=3D NULL; ups =3D ups->next) >> if (flag_isset(ups->status, ST_MASTER)) { >> isamaste...

Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by