On Sun, 2024-08-25 at 08:51 +0100, Barry wrote:
> The RTC wake powers on the system. But a suspended system is
> already powered up and kernel is in charge.
I wouldn't say so. It's barely powered up, and you're relying on
firmware to control waking it up.
--
uname -rsvp
Linux 3.10.0-1160.119
On Sun, Aug 25, 2024 at 11:30 PM Mike Wright
wrote:
>
> Now that sshd is working as a service I tried to ssh in and got bounced
> out. Trying again with ssh -v FED ( container's name ) yields:
>
> debug1: Server accepts key: /home/mike/...
>
> journalctl -xeu sshd shows:
>
> FED unix_chkpwd[881]:
Fulko Hew:
> > But 'shutdown' provided all the housekeeping work such as:
> > - disabling logins
> > - sending out messages to users screen warning them of the impending
> > doom
> > - providing grace time
> > - unmounted file systems
> > - killed the system
Patrick O'Callaghan:
> Same here. Howev
Hi all,
Now that sshd is working as a service I tried to ssh in and got bounced
out. Trying again with ssh -v FED ( container's name ) yields:
debug1: Server accepts key: /home/mike/...
journalctl -xeu sshd shows:
FED unix_chkpwd[881]: could not obtain user info (mike)
FED sshd[735]: fatal:
On 8/25/24 12:51 AM, Barry wrote:
On 24 Aug 2024, at 12:18, Patrick O'Callaghan wrote:
If the RTC can wake
the system from hibernation, why can't it wake it from suspension?
The RTC wake powers on the system. But a suspended system is
already powered up and kernel is in charge.
Sort of.
Hi gurus,
I've installed f40 as an lxc container named FED. Default image comes
without an ssh server so I "dnf install openssh-server -y" followed by
"systemctl start sshd". It fails. journalctl -xeu sshd shows this:
"FED (sshd)[636]: sshd.service: Referenced but unset environment
variab
I did and everything worked. But my apcupsd.conf file has NOLOGON
disabled so the file should never have been created, or at least so I
thought.
Paolo
On 8/25/24 11:36, Garry T. Williams wrote:
On Friday, August 23, 2024 5:53:53 PM EDT Paolo Galtieri wrote:
I previously sent a message reg
And most importantly sending all running processes a hangup signal to allow them to save things that were volatile (like open files) then (if they were still alive) after the “timeout” had expired sending them a -9 signal to kill them, that was in the days of the “init” daemon, i assume systemd doe
> On 25 Aug 2024, at 11:43, Walter H. via users
> wrote:
>
> or the kernels later than 6.10.3 are buggy and this need to be fixed(!)
>
> I tried the VM with latest VMware Wkstn. - same problem
As I said VMware has a history of breaking on new kernels.
Their hypervisor appears to "know" about
> On 25 Aug 2024, at 15:17, Fulko Hew wrote:
>
> Back in time, there was only 'shutdown'. And it had a default
> timeout of 5 minutes to allow
Yeah back 15 or more years ago...
That 5 mins is the delay before starting the shutdown.
What POC want to avoid is the slow progress of shutdown onc
On Friday, August 23, 2024 5:53:53 PM EDT Paolo Galtieri wrote:
> I previously sent a message regarding my laptop powering off
> unexpectedly. Here is an update. Power came back on, but I cannot
> login to my laptop. When I try to login to the mate gui it replies
> with power failure and aut
On Sun, 2024-08-25 at 16:48 +0100, Patrick O'Callaghan wrote:
> On Sun, 2024-08-25 at 11:14 -0400, Fulko Hew wrote:
> > On Sun, Aug 25, 2024 at 11:08 AM Patrick O'Callaghan
> >
> > wrote:
> >
> > > On Sun, 2024-08-25 at 10:48 -0400, Fulko Hew wrote:
> > > > > Same here. However these are reasonab
On Sun, 2024-08-25 at 11:14 -0400, Fulko Hew wrote:
> On Sun, Aug 25, 2024 at 11:08 AM Patrick O'Callaghan
>
> wrote:
>
> > On Sun, 2024-08-25 at 10:48 -0400, Fulko Hew wrote:
> > > > Same here. However these are reasonable measures on a multi-
> > > > user
> > > > system. On a single-user deskto
On Sun, Aug 25, 2024 at 11:08 AM Patrick O'Callaghan
wrote:
> On Sun, 2024-08-25 at 10:48 -0400, Fulko Hew wrote:
> > > Same here. However these are reasonable measures on a multi-user
> > > system. On a single-user desktop they just get in the way,
> > > especially with journal-based filesystems
On Sun, 2024-08-25 at 10:48 -0400, Fulko Hew wrote:
> > Same here. However these are reasonable measures on a multi-user
> > system. On a single-user desktop they just get in the way,
> > especially with journal-based filesystems.
> >
>
> Then you can simply use 'shutdown now'.
I don't want to s
On Sun, Aug 25, 2024 at 10:40 AM Patrick O'Callaghan
wrote:
> On Sun, 2024-08-25 at 10:17 -0400, Fulko Hew wrote:
> > On Fri, Aug 23, 2024 at 1:36 AM Tim via users
> >
> > wrote:
> >
> > > Sam Varshavchik wrote:
> > > > > I find it highly improbable that there is a "delay reboot for X
> > > > >
On Sun, 2024-08-25 at 10:17 -0400, Fulko Hew wrote:
> On Fri, Aug 23, 2024 at 1:36 AM Tim via users
>
> wrote:
>
> > Sam Varshavchik wrote:
> > > > I find it highly improbable that there is a "delay reboot for X
> > > > minutes for no reason whatsoever" setting somewhere, that
> > > > simply
> >
On Fri, Aug 23, 2024 at 1:36 AM Tim via users
wrote:
> Sam Varshavchik wrote:
> > > I find it highly improbable that there is a "delay reboot for X
> > > minutes for no reason whatsoever" setting somewhere, that simply
> > > needs to be changed. As Mr. Spock would say: "this is not logical".
>
>
On 25.08.2024 09:53, Barry wrote:
On 25 Aug 2024, at 08:50, Walter H. via users
wrote:
I have not used vmware for a long time, but when I did it was
sometimes necessary to wait for vmware to fix something before a new
kernel would work.
I have nothing installed from vmware, the vmware tool
On Sun, 2024-08-25 at 11:13 +0930, Tim via users wrote:
> Doug Herr:
> > > I also enabled the "Magic" check box for the Network Manager
> > > config
> > > for my Ethernet port.
>
> Patrick O'Callaghan:
> > Not sure what that is. I don't see any such box.
>
>
> In the Network Manager open up the
On Sat, 2024-08-24 at 12:17 +0100, Patrick O'Callaghan wrote:
> Having failed to get hibernation working (see recent posts about
> Secure
> Boot getting in the way), I tried to fall back to suspending the
> system
> overnight. That works of course.
>
> What doesn't work is waking it up automatical
On Sun, 2024-08-25 at 08:51 +0100, Barry wrote:
>
>
> > On 24 Aug 2024, at 12:18, Patrick O'Callaghan
> > wrote:
> >
> > If the RTC can wake
> > the system from hibernation, why can't it wake it from suspension?
>
> The RTC wake powers on the system. But a suspended system is
> already powered
On Sat, 2024-08-24 at 20:22 -0700, Doug Herr wrote:
> On Sat, Aug 24, 2024, at 2:23 PM, Patrick O'Callaghan wrote:
> > I use UEFI mode and don't want to change it. I'm pretty sure the
> > UEFI
> > settings have toggles for WOL but I'll need to check. The Android
> > app I
> > have is called WolOn a
On 13/7/24 3:07 pm, Eyal Lebedinsky wrote:
Following an upgrade of the host (38->40) I could not start the vm.
The VM was running f40 for a while just fine. It was "virsh save"d a few days
ago.
$ sudo virsh save e4 /data1/VMs/libvirt/images/e4.saved
Normally I actually stop it but forgot
> On 25 Aug 2024, at 08:50, Walter H. via users
> wrote:
>
>> I have not used vmware for a long time, but when I did it was
>> sometimes necessary to wait for vmware to fix something before a new
>> kernel would work.
>
> I have nothing installed from vmware, the vmware tools
It’s the vmware
> On 24 Aug 2024, at 12:18, Patrick O'Callaghan wrote:
>
> If the RTC can wake
> the system from hibernation, why can't it wake it from suspension?
The RTC wake powers on the system. But a suspended system is
already powered up and kernel is in charge.
You need to use a systemd timer to sched
On 25.08.2024 09:37, Barry wrote:
On 24 Aug 2024, at 14:47, Walter H. via users
wrote:
it is a VMware Guest
I have not used vmware for a long time, but when I did it was
sometimes necessary to wait for vmware to fix something before a new
kernel would work.
I have nothing installed from v
> On 24 Aug 2024, at 14:47, Walter H. via users
> wrote:
>
> it is a VMware Guest
I have not used vmware for a long time, but when I did it was
sometimes necessary to wait for vmware to fix something before a new
kernel would work.
Suspect you need to install a 6.9 kernel and test that.
Bar
28 matches
Mail list logo
