search for: shutdowns

...-p <password> ups upsrw -s ups.delay.start=60 -u <username> -p <password> ups upscmd -u <username> -p <password> ups shutdown.return # wait ~15 seconds, then: upscmd -u <username> -p <password> ups shutdown.stop # load.on executed after one of the previous shutdowns (after a successful shutdown.stayoff or while ups.delay.start elapses); # e.g. after a shutdown.return: upsrw -s ups.delay.shutdown=30 -u <username> -p <password> ups upsrw -s ups.delay.start=60 -u <username> -p <password> ups upscmd -u <username> -p <password> u...

...ups.delay.start set to 60 seconds; > - shutdown.return with ups.delay.shutdown set to 60 seconds and > ups.delay.start set to 0 seconds; > - shutdown.stop executed after one of the previous commands (while > ups.delay.shutdown elapses); > - load.on executed after one of the previous shutdowns (after a > successful shutdown.stayoff or while ups.delay.start elapses); > - load.off and then load.on. > > Thanks in advance for your patience. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser...

Hello! I'm a total noob in the NUT world, and have 0 experience dealing with Linux distributions. Since NUT is poorly ported to Windows it's driving me crazy, I hope you can help me. I have, after 3 days of painful reading, testing and failing, successfully set up NUT to communicate with my cheap-ass line-interactive 1000VA Chinese UPS (just no brand at all, it is a locally rebranded UPS,

...upsrw -s ups.delay.start=60 -u <username> -p <password> ups > upscmd -u <username> -p <password> ups shutdown.return > # wait ~15 seconds, then: > upscmd -u <username> -p <password> ups shutdown.stop > > # load.on executed after one of the previous shutdowns (after a > successful shutdown.stayoff or while ups.delay.start elapses); > # e.g. after a shutdown.return: > upsrw -s ups.delay.shutdown=30 -u <username> -p <password> ups > upsrw -s ups.delay.start=60 -u <username> -p <password> ups > upscmd -u <username&...

...own set to 60 seconds and ups.delay.start set to 60 seconds; - shutdown.return with ups.delay.shutdown set to 60 seconds and ups.delay.start set to 0 seconds; - shutdown.stop executed after one of the previous commands (while ups.delay.shutdown elapses); - load.on executed after one of the previous shutdowns (after a successful shutdown.stayoff or while ups.delay.start elapses); - load.off and then load.on. Thanks in advance for your patience. -------------- next part -------------- A non-text attachment was scrubbed... Name: original-attachments.tar.gz Type: application/x-gzip Size: 8392 bytes Desc:...

Is it possible to shutdown a Linux computer through Samba using the shutdown command in Windows XP and 2003? I've tried: shutdown /r /m hostname This doesn't work and results in Windows reporting "The remote procedure call failed.' in the command window. The Samba log shows the following: ------------ CLIP --------------------------------------------------- [2006/11/07

I just installed NUT on a new Linux (Gentoo) system. Most things work, (notification after 10 seconds on battery, notification and system shutdown after 100 seconds on battery.) However I can't seem to get the UPS (an Eaton 5SC1500) to turn itself off after the Gentoo system shutdown. This is the shutdown command I am using in /etc/nut/upsmon.conf: SHUTDOWNCMD "/usr/sbin/upsdrvctl

This is testing the delay filter, and we want to use the name ‘test-shutdown’ in a later commit to test the new nbdkit_shutdown() API, so let’s rename it. --- tests/Makefile.am | 4 ++-- tests/{test-shutdown.sh => test-delay-shutdown.sh} | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/tests/Makefile.am b/tests/Makefile.am index

Hi, we have a problem in oVirt that highly available VMs don't restart after host poweroff because Vdsm identifies the case as a user initiated shutdown (https://bugzilla.redhat.com/1800966). When poweroff is run on the host, libvirt-guests service takes an action. `virsh shutdown' is run on the VM, the guest OS is shut down cleanly and libvirt reports a shutdown event with

I am running CentOS 5.3 and have just the two accounts "root" and "buz". I would like to be able to issue "shutdown" from the account "buz", and thus created /etc/shutdown.allow with the single entry "buz" (without any quotes). I still get the error message "only root can do this" (or something similar) even if I include the

Hi ?? I need to shutdown a number of hosts which has not NUT from one which has it. ?? I tried to do it from upssched script (after upssched's timer) like this: case $1 in ??????? earlyshutdown) ??????????????? logger -t upssched-cmd "Early shutdown is started" ??????????????? /bin/sh /usr/local/sbin/shutdown-all-hosts.sh ??????????????? /usr/local/sbin/upsmon -c fsd

I am looking at the shutdown method, but if the guest system is a desktop system, like for example ubuntu, it just has the effect to show a box prompting the user for a shutdown/reboot/ and such. I could enter the guest and change this default behaviour and it actually works..but I'd like for a way to send a shutdown command without doing so. Is it possible?

docs/man/xl.pod.1 | 6 +++++- tools/libxl/xl_cmdimpl.c | 39 ++++++++++++++++++++++++++++++++++++--- tools/libxl/xl_cmdtable.c | 3 ++- 3 files changed, 43 insertions(+), 5 deletions(-) xl: Introduce shutdown xm compatibility option -a to shutdown all domains Signed-off-by: Sander Eikelenboom <linux@eikelenboom.it> diff -r 9dc729b75595 -r 67f9ef649937 docs/man/xl.pod.1 ---

On Wed, 14 Oct 2015, Davide Baldini wrote: > 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 What does "ps aux |

Denny: Thank you. Problem solved. I switched SHUTDOWNCMD back to the default and added nut.powerfail to the shutdown runlevel. Now the UPS turns off after the system shutdown, if the shutdown is caused by lack of power going to the UPS. I checked and found the file sys-power:nut-2.7.4-r1:2018...log in /var/log/portage/elog/*. It did contain the message you pointed out. I should have checked

On Wed, 13 Jul 2016, Dmitri Stepanov wrote: > Hi > > ?? I need to shutdown a number of hosts which has not NUT from one which has it. > > ?? I tried to do it from upssched script (after upssched's timer) like this: > > case $1 in > ??????? earlyshutdown) > ??????????????? logger -t upssched-cmd "Early shutdown is started" > ??????????????? /bin/sh

Hello Charles, Thank you for your comment. Just tried to use ups.delay.shutdown to postpone the UPS shutdown. The thing is that if the PC shutdown first, then the UPS, it wasn't able to send "shutdown.reboot" any more because everything is power off after the UPS shuts down. Also play on the watchdog for Tripp Lite. Looks like it has the command of reset.watchdog but not

I've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system

"Daniel P. Berrange" <dan@berrange.com> writes: > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: >> Hi, >> > >> we have a problem in oVirt that highly available VMs don't restart after >> host poweroff because Vdsm identifies the case as a user initiated >> shutdown (https://bugzilla.redhat.com/1800966). >> >>

Init.d/system.d script doesn't kill gluster automatically on reboot/shutdown? Il 29 giu 2017 5:16 PM, "Ravishankar N" <ravishankar at redhat.com> ha scritto: > On 06/29/2017 08:31 PM, Renaud Fortier wrote: > > Hi, > > Everytime I shutdown a node, I lost access (from clients) to the volumes > for 42 seconds (network.ping-timeout). Is there a special way to