similar to: Ubuntu 16.04 Server as Domain Member Problem

Hi, I have recently installed NUT 2.7.3.1 on a freshly installed Ubuntu 16.04 LTS (64-bit) system, connected via USB cable to APC Smart-UPS 1500 (SMT model). I am trying to make this configuration work for automatic shutdown/restart but it seems that it completely ignores /etc/killpower presence. I know the APC SMT models are problematic but it looks like I could not even make the simplest

Hi Charles, On Wednesday, July 13, 2016 11:40:09 PM Charles Lepple wrote: > On Jul 12, 2016, at 5:27 PM, Ivan Adzhubey <iadzhubey at rics.bwh.harvard.edu> > wrote: > > I have recently installed NUT 2.7.3.1 on a freshly installed Ubuntu 16.04 > > LTS (64-bit) system, connected via USB cable to APC Smart-UPS 1500 (SMT > > model). I am trying to make this configuration

Hello samba4 rc3 *s4-ad -> samba server Host name test.s4.com -> domain name* *Dns Server -> Samba Internal DNS server , Bind 9.9.1-P2* *win xp* have access to default share such as sysvol by dns name (\\test.s4.com \sysvol) but if created a share in smb.conf Only access by IP such as : \\test.s4.com\myshare -> no access and ask me for user and password !

This module is able to power off a system via APM. It replaces the poweroff COMBOOT module. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> --- com32/modules/Makefile | 2 +- com32/modules/poweroff.c | 88 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 89 insertions(+), 1 deletions(-) create mode 100644 com32/modules/poweroff.c diff --git

There is a race case where the user does ''poweroff'' and at the same time the system admin does ''xl shutdown''. Depending on the race, the system_state will be SYSTEM_RUNNING or SYSTEM_POWER_OFF. If SYSTEM_RUNNING we just end up making a duplicate call to ''poweroff'' (while it is running). That will fail or execute (And if executed then it will

I have a root cron job that powers down my server every day at 1am and 6pm. The output of '# crontab -l' is shown below. * 1,18 * * * poweroff Last night, after the server powered down at 6pm, I decided I wanted to use the server so I started it with the power button. The server, after a minute or so, powered itself down. This behaviour happened repeatedly until I waited past 7pm.

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

Hi! I'm using nut to control a ups powerware 9135. All are working, but, in the shutdown, the ups don't poweroff. I did check with upsc, and I can't see a ups.delay.shutdown variable to set the time of automatic poweroff, when I did complete the shutdown of machines. Before, I did use a propietary program to work with this ups, and the daemon did poweroff the ups without problems. But,

On Tue, Nov 06, 2018 at 04:06:35PM +0100, Pino Toscano wrote: > On Tuesday, 6 November 2018 14:07:51 CET Richard W.M. Jones wrote: > > On Tue, Nov 06, 2018 at 12:51:30PM +0100, Pino Toscano wrote: > > > +static void > > > +shutdown_clicked (GtkWidget *w, gpointer data) > > > +{ > > > + if (!is_iso_environment) > > > + return; > > >

I just noticed that CentOS (6.2) by default allows any user to reboot/poweroff system without any admin rights, or without any further questions, if using commands 'reboot' or 'poweroff'. But 'shutdown' still requires admin rights. What is the preferred way to restrict any regular user from rebooting / powering off the system (by accident)? IMHO, sudo should be

On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> > We would need at least: > > A_ the partitions and directory structure in which the following items > are _located_ : /dev/sda1: # tree . . ??? extlinux ? ??? ldlinux.c32 ? ??? ldlinux.sys ? ??? libcom32.c32 ? ??? libmenu.c32 ? ??? libutil.c32 ? ??? menu.c32 ? ???

I'm trying to enable offline auth in a Ubuntu 22.04 box, following: https://wiki.samba.org/index.php/PAM_Offline_Authentication using standard ubuntu samba package (4.15.13+dfsg-0ubuntu1.1). I've enabled workaround 'lock directory = /var/cache/samba'. Still does not work, and behave very badly with no conectivity or bad connectivity (wireless): sometime the

Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit LABEL halt com32 poweroff.c32 Does not power off my qemu, it stays open in halt mode. qemu -cdrom ubuntu.iso -boot d -net nic,model=virtio -m 1024 -curses If I boot into ubuntu first and do sudo halt -p it powers off and closes qemu. Can poweroff.c32 do the same as sudo halt -p in ubuntu?

I'm new to the list. Hello. I just googled and tried some general news lists. There is hard to compose good question to google, cause shutdown and poweroff are standard ups jobs. Then. I've upgraded some computer Centos 5.3 to Centos 6.1. It is powered with Powercom BNT-400AP ups. A problem is, when I try to start upsdriver - powercom. While connecting to the ups (via ttyS) it

On Fri, Jun 28, 2013 at 2:31 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 27, 2013 at 6:03 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit >> >> LABEL halt >> com32 poweroff.c32 >> >> Does not power off my qemu, it stays open in halt mode. >> qemu -cdrom

When i execute poweroff.com, I get the following error: "APM not present" Is there some workaround currently? The restart option works, and when I boot into ANY linux OS, the poweroff or lalt commands DO Power off the computer. This was reported at the PartedMagic's forum at http://forums.partedmagic.com/viewtopic.php?f=5&t=582

while finishing some work on the HAL integration (I'm now mapping DBus method with NUT commands, to allow at least the final UPS poweroff), I was horrified to realize (and so late) the changes in usbhid-ups->upsdrv_shutdown(). We've lost a lot there, but making a generic code, instead of keeping the subdrivers delegation. For example, the shutdown.return command (which is or should be

Hello all, I was asked about a proper way to ensure powerfail shutdown of a blade server fed off an APC SmartUPS, which is monitored by all hosts over SNMP. In particular, they'd like to avoid the "untimely" return of utility power - when the OSes are already shutting down, and would stay down because the UPS is well-fed now and thus won't power off and later power on to boot

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

"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). >> >>