similar to: Power Fail Protection Update

On 8/16/2017 7:49 AM, Chris Olson wrote: > Many thanks to those that responded to my original posting with > information about Network UPS Tools and commercial UPS products. > > In our planning a path forward to implement UPS-based power fail > protection, we have come across what appears to be an issue with > the state of the CentOS 6 machines being UPS protected. Most of >

Has anyone experience with WOL under Centos (5.3).? If so, how exactly do you put the machine to sleep, and how exactly do you wake it up remotely? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin

I am running Samba 3.5.5 on Solaris 10. I have one machine as a PDC, one as a BDC. If I logon to the domain from a Windows 7 Pro (64-bit) laptop, hibernate the machine, unplug the network cable and wake the machine, I can not unlock the screen. I will get the message "There are currently no logon servers available to service the logon request." Other users have reported this.

Hello, Dovecot 2.2.27 (Debian Jessie backports). When issuing a "doveadm kick" for a specific user I was greeted by: --- "warning: other connections would also be kicked from following users:" --- and a list of 22odd thousand users. As it turns out, kick wants to smack the hibernation proces(ses) that have hibernated sessions for this user, obviously the wrong approach here.

My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on

Hello list I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R motherboard. Integrated network card is Realtek 8111B. I can not wake the computer after I shutdown it from FreeBSD. It is a dualboot system - windows xp and freebsd. If I shutdown the computer from windows - later I can wake it up with magic packet. Even if i shutdown the machine on the boot menu with the power

Folks, I am terribly puzzled by an issue reported as bug 2381 [http://bugs.centos.org/view.php?id=2381] ? definitely an upstream bug, as it does the same under X/OS 5 and StartCom 5. Simply put: Hibernation fails with horrendous I/O errors after swsusp starts dumping to swap. What bugs me is that hibernating from the CentOS 5 LiveCD *works*!!! (on the same hardware) How could I investigate to

Hi, In my GNOME System menu (in French) there are basically the following options : - Lock screen - Hibernate - Close session - Shut down Is there any way to disable the "Hibernate" option ? In the past, I've accidentally clicked on it, which put the computer to sleep, only it refused to wake up after that. Maybe some package to uninstall ? But which one ? Cheers, Niki

Some switch hardware can generate the packets directly, negating the need for a box on every VLAN. Meraki hardware can do it, but you have to go through the dashboard so automating it isn't currently possible. Here is some documentation on forwarding WoL on catalyst 3750 switches from Cisco:

On Sun, 2020-05-17 at 20:25 -0600, R C wrote: > Ok, I get that, found it before; "typically sent as a UDP datagram to > port 0, 7 or 9, or directly over Ethernet as EtherType 0x0842" > > > The keyword being 'typically', but what is it that ether-wake actually > uses/does? (I need to forward a WOL packet to a different > > vlan on some Cisco

We've been using hibernate for about half a year with no ill effects. There were various logged errors in earlier versions of dovecot, but even with those, we never heard a reported customer-side error (almost always when transitioning from hibernate back to regular imap; in the case of those errors, presumably the mail client just reconnected silently). For no particular reason besides

The WoL magic packet is only scanned for the string above, and not actually parsed by a full protocol stack, it could be sent as any network- and transport-layer protocol, although it is typically sent as a UDP <https://en.m.wikipedia.org/wiki/User_Datagram_Protocol> datagram <https://en.m.wikipedia.org/wiki/Datagram> to port <https://en.m.wikipedia.org/wiki/TCP_and_UDP_port> 0,]

[-=X.L.O.R.D=-] wrote: > 1guys, > I think it can be done via power management feature if PC idle a period of time, sleep it. Access is exclusively via RDP-sessions. I don?t know if I can get a VM to hibernate when idle and to wake up when someone tries to connect; and delying logins as mmight occur when the VM needs to wake up first is not an option. Besides, internet access would not be

Hello, as some may remember, we're running very dense IMAP cluster here, in excess of 50k IMAP sessions per node (current record holder is 68k, design is for 200k+). The first issue we ran into was that the dovecot master process (which is single thread and thus a bottleneck) was approaching 100% CPU usage (aka using a full core) when trying to spawn off new IMAP processes. This was

Roger, I just ran a manual test, killing power and see what happens.  I set the Synology “Time before DiskStation goes into Safe mode” to 5 minutes so I didn’t have to wait like an hour until it powered down.  Here is the log: https://hastebin.com/ovuwilufeb.sql Everything appeared to be normal; the servers powered off and the Synology went into safe mode.  Power was then cut to the Synology

Everyone, I have not been able to get ether-wake to work waking up other centos 7.6 machines after the upgrade to Centos 7.6. Has anyone else had this problem, and if so any luck with a fix? Greg Ennis

> Actually you are not correct. > > > 1st: I didn't quote the wikipedia article,? someone sent that as an > answer to my previous post. > > ?? (similar mindset probably, as in your response) > > 2: You are wrong,? broadcast packets, like for example DHCP, and also > WOL (if UDP), can be routed, by > > the means of ip helper addresses and directed broadcasts

Thank you very much. I can confirm that the TAP-WIN32 driver behaves differently. The quick tests so far revealed that it either reconnected after Standby and Hibernation. I think that at some point I started using the OpenVPN drivers when I had either had trouble with unsigned drivers or the network detection and then just stayed with it. Thanks for pointing out my self-made problem. On

http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. * master: Removed hardcoded 511 backlog limit for listen(). The kernel should limit this as needed. * doveadm import: Source user is now initialized

http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. * master: Removed hardcoded 511 backlog limit for listen(). The kernel should limit this as needed. * doveadm import: Source user is now initialized