search for: shudowning

Hello samba-list, I'm able to shutdown remote mashines using: supzli02pdc:~ # net rpc shutdown -S <target-pc> -U Administrator%<passwd> -r -t 1 --comment=Abmelden I wounder if this is also possible with an mashine account auth (from the PDC)? I couldn't get it to work: supzli02pdc:~ # net -n supzli02pdc -P rpc shutdown -r -t 1 -S <target-pc> --comment=Abmelden

Nut-names.txt states that 1. ups.start.auto controls whether the UPS starts when mains is (re)applied. 2. shutdown.stayoff causes "turn off the load possibly after a delay and remain even if power returns". 3. shutdown.return causes "turn off the load possibly after a delay and return when power is back". 1 seems to conflict with 2 and 3. That is, 2

> > Did you see a line in the journal similar to this ? > Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]: > nut-delayed-ups-shudown.service calling > upsdrvctl to shut down UPS unit Never after I disabled the service. I pasted the whole journal section of the successful shutdown from last email. However I have been thinking about this line

P.S. There is a typo in your nut-delayed-ups-shutdown.service. Line: ExecStart=/usr/bin/logger -t upsdrvctl "nut-delayed-ups-shudown.service calling upsdrvctl to shut down UPS unit" shudown is missing a 't'. It is in the log message but might still be worth fixing for grepping. BTW why is that service in /etc/systemd/system/ and not in /usr/lib/systemd/system/ ? --- George

Hi, I had an issue where after returning the power from a shutdown.return the ups would do another shutdown.return during the boot, and kept this forever. After some investigation I found the problem is a bug on the ups - TSSHARA model, driver nutdrv_qx: every time I shutdown with return, and reconnect the usb after the power is back it would start another shudown.return cycle. When I used my

Another question. When my database is running, I do [oracle@LNCSTRTLDB03 LPTE3]$ cp --o_direct xdb01.dbf /tmp cp: cannot open `xdb01.dbf' for reading: Permission denied [oracle@LNCSTRTLDB03 LPTE3]$ When the database is shudown it works. Is this normal for ocfs because with any other filesystem I can just copy a file at any time (Its only a testing, I know I cant copy datafiles and have

Answers bellow. 2018-02-28 1:41 GMT-03:00 Daniele Pezzini <hyouko at gmail.com>: > 2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > > Hi, > > > > I had an issue where after returning the power from a shutdown.return the > > ups would do another shutdown.return during the boot, and kept this > forever. > > After some

2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hi, > > I had an issue where after returning the power from a shutdown.return the > ups would do another shutdown.return during the boot, and kept this forever. > After some investigation I found the problem is a bug on the ups - TSSHARA > model, driver nutdrv_qx: every time I shutdown with return, and

Hello, a typical connection close, tcpdump'ed on the server side, looks as follows: 21:44:01.168131 IP xxx.xxx.3.101.143 > xxx.xxx.3.96.35518: Flags [FP.], seq 3982457856:3982457959, ack 1570044906, win 243, options [nop,nop,TS val 138698279 ecr 159494908], length 103 21:44:01.172405 IP xxx.xxx.3.101.143 > xxx.xxx.3.96.35518: Flags [R], seq 3982457960, win 0, length 0 21:44:01.172442

Hi all I'm busy testing the Powerware9120 and am stuck at the powering down of the UPS. I'm running the latest Debian Lenny and here is my versions Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools - BCMXCP UPS driver 0.14 (2.2.2) ups.conf [pw] driver = bcmxcp_usb port = auto shutdown_delay = 60 I get all the correct info from the UPS and NUT works great and

Beautiful! The shutdown succeeded. Thank you very much. However there was no any notification on desktop at all. Only in journalctl. Here it is: Oct 27 23:38:11 i7 upsmon[2224]: UPS myups at localhost on battery Oct 27 23:38:11 i7 upssched[2244]: Timer daemon started Oct 27 23:38:11 i7 upssched[2244]: New timer: two-minute-warning-timer (5 seconds) Oct 27 23:38:11 i7 upssched[2244]: New timer:

On Wed, 28 Oct 2015, George Anchev wrote: > Beautiful! The shutdown succeeded. Did you see a line in the journal similar to this ? Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]: nut-delayed-ups-shudown.service calling upsdrvctl to shut down UPS unit > However there was no any notification on desktop at I'm guessing you use KDE and this

Dear list members, I'd like to setup my UPS in a way that it only shuts the server (including 5 VMs down if really necessary). We do have a rather stable power supply here, but there are multiple 200ms outages within a year and there also have been some that lasted more than half an hour. So: since the shudown is rather quick, I'd ideally set it to "shut down when only 20% battery

Hello, I think that on this file nutdrv_qx_megatec.c the definition for shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m while on the megatec protocol description ( http://networkupstools.org/protocols/megatec.html) the command is just "S%s\r". When I changed it my system was abe to at least stay off, and stopped making an instant power recycling.

Hi Charles, thank you VERY MUCH for all your hints. > If you have a jumper wire handy, you can connect the PC's TxD to RxD I should have tried to connect from another computer in the first place. Or access another device known to work from this computer. It turned out that the shield I used to connect the mainboard connector to the PC case expected another mainboard pin layout. So all I

Hi Michal, Looking in the logs, it looks like the libvirt process sent a sigkill to the qemu process: 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerAcquire:358 : lock=0x7f6bc80de170 state='(null)' flags=3 action=0 fd=0x7f6bdf3bf074 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerFree:395 : lock=0x7f6bc80de170 2013-10-11 19:59:22.132+0000: 10212: debug :

Hello.... I'm testing the functionality of my NUT-setup (NUT 2.0.4-4 - Debian stable). The system is connected to the UPS, but is not powered by it. When running "upsmon -c fsd", upsmon says "Auto logout and shutdown proceeding". This is all well and good, but I never see the machine waiting for the UPS to cut the power. Instead it shuts down. It's my

http://bugs.freedesktop.org/show_bug.cgi?id=22763 Summary: suspend doesn't works Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

Hi,we have use glusterfs for two years. After upgraded to 3.2.5,we discover that when one of replicate node reboot and startup the glusterd daemon,the gluster will crash cause by the other replicate node cpu usage reach 100%. Our gluster info: Type: Distributed-Replicate Status: Started Number of Bricks: 5 x 2 = 10 Transport-type: tcp Options Reconfigured: performance.cache-size: 3GB

Dino, Alexey, there are a number of users suffering issues with your Powercom devices. Could you (Dino, and Keven if possible) please have a look at the below one, from Angela, and check for a fix? I've scheduled to release 2.6.1 next week, and having that fixed is part of the list. 2011/5/16 Angela Williams <angierfw at gmail.com> > Hi All > > On Friday 13 May 2011 at