On Tue, 2024-08-27 at 08:01 +0100, Barry wrote:
> Sync is not used on shutdown.
> It is the action of umount that causes all data to be flushed out to the disk.
> As you say that may take a while if the disk is slow, USB, or has just had a
> huge
> amount of data written to it just before shutdown
> On 26 Aug 2024, at 14:38, Jeffrey Walton wrote:
>
> I think part of the problem is the behavior of sync(8) and sync(2)
Sync is not used on shutdown.
It is the action of umount that causes all data to be flushed out to the disk.
As you say that may take a while if the disk is slow, USB, or ha
On Sun, Aug 25, 2024 at 11:55 PM Tim via users
wrote:
>
> 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 s
On Mon, 2024-08-26 at 13:23 +0930, Tim via users wrote:
> 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 f
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
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 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 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 Fri, 2024-08-23 at 12:30 +0200, Roberto Ragusa wrote:
> Unfortunately somebody thinks that showing a useless spinning logo
> is more "elegant" than letting the user understand what's (mis)happening.
> People do not even know they have to press esc to see things.
Doesn't have that cool hacker vi
Ralf Corsépius composed on 2024-08-23 14:01 (UTC+0200):
> schrieb George N. White III:
>> If you want to "see things", remove the `rhgb quiet` from the kernel
>> command-line.
> Also, consider to set the plymouth-theme to "detail"
> (cf. man plymouth-set-default-theme)
Or take the green route,
Am 23.08.24 um 1:32 PM schrieb George N. White III:
If you want to "see things", remove the `rhgb quiet` from the kernel
command-line.
Also, consider to set the plymouth-theme to "detail"
(cf. man plymouth-set-default-theme)
Ralf
--
___
users maili
On Fri, Aug 23, 2024 at 7:31 AM Roberto Ragusa
wrote:
> On 8/22/24 15:18, Thomas Cameron wrote:
>
> > You probably already know this but... When the system is shutting down,
> if you hit
>
> the escape key, it will change from graphical to text mode. You should be
> able to see
>
> what it's hung
On 8/22/24 15:18, Thomas Cameron wrote:
You probably already know this but... When the system is shutting down, if you
hit the escape key, it will change from graphical to text mode. You should be
able to see what it's hung doing while shutting down.
Unfortunately somebody thinks that showin
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".
Tim:
> Although that pretty much describes what I see on a friend'
On Thu, 2024-08-22 at 07:15 -0400, 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".
Although that pretty much describes w
On Thu, 2024-08-22 at 11:28 -0300, George N. White III wrote:
> So you want to "retrieve other state and tracing information from the
> system and service manager, and to verify the correctness of unit
> files. It is also used to access special functions useful for
> advanced system manager debuggi
On Thu, 2024-08-22 at 11:24 -0400, Tom Horsley wrote:
> I always had long reboots as well, then I realized I'm not running
> anything like a database that needs to be properly flushed to disk,
> etc. So I changed DefaultTimeoutStopSec from 90 seconds to 5 seconds
> in /etc/systemd/system.conf and /
I always had long reboots as well, then I realized I'm not running anything
like a database that needs to be properly flushed to disk, etc. So I changed
DefaultTimeoutStopSec from 90 seconds to 5 seconds in
/etc/systemd/system.conf and /etc/systemd/user.conf and now my system
reboots fairly quickly
On Thu, Aug 22, 2024 at 8:44 AM Patrick O'Callaghan
wrote:
> On Thu, 2024-08-22 at 07:57 -0300, George N. White III wrote:
> > On Thu, Aug 22, 2024 at 7:36 AM Patrick O'Callaghan
> >
> > wrote:
> >
> > > When I reboot the system, there's a delay of around a minute before
> > > anything happens.
On 8/22/24 5:36 AM, Patrick O'Callaghan wrote:
When I reboot the system, there's a delay of around a minute before
anything happens. This is a single-user desktop and I really don't need
to stare at a spinner for so long. Is there a setting somewhere that
lets me change this? I'm aware of 'reboot
On Thu, 2024-08-22 at 12:42 +0100, Patrick O'Callaghan wrote:
> > I have these overrides for timeouts:
> >
> > /etc/systemd/user.conf.d/10-barry.conf
> > [Manager]
> > DefaultTimeoutStopSec=15s
> >
> > /etc/systemd/system.conf.d/10-barry.conf
> > [Manager]
> > DefaultTimeoutStopSec=20s
>
> Thank
On Thu, 2024-08-22 at 07:48 -0400, Sam Varshavchik wrote:
> > Sorry if that wasn't clear. I'm talking about the time between
> > initiating a reboot, either from the Shell or from the GUI, and the
> > actual system going down (either for reboot or shutdown) as
> > determined
> > by the display turn
Patrick O'Callaghan writes:
On Thu, 2024-08-22 at 07:15 -0400, Sam Varshavchik wrote:
> Patrick O'Callaghan writes:
>
> > When I reboot the system, there's a delay of around a minute before
> > anything happens. This is a single-user desktop and I really don't
> > need
> > to stare at a spinner
On Thu, 2024-08-22 at 07:57 -0300, George N. White III wrote:
> On Thu, Aug 22, 2024 at 7:36 AM Patrick O'Callaghan
>
> wrote:
>
> > When I reboot the system, there's a delay of around a minute before
> > anything happens. This is a single-user desktop and I really don't
> > need
> > to stare at
On Thu, 2024-08-22 at 12:25 +0100, Barry Scott wrote:
>
>
> > On 22 Aug 2024, at 11:36, Patrick O'Callaghan
> > wrote:
> >
> > When I reboot the system, there's a delay of around a minute before
> > anything happens. This is a single-user desktop and I really don't
> > need
> > to stare at a sp
On Thu, 2024-08-22 at 07:15 -0400, Sam Varshavchik wrote:
> Patrick O'Callaghan writes:
>
> > When I reboot the system, there's a delay of around a minute before
> > anything happens. This is a single-user desktop and I really don't
> > need
> > to stare at a spinner for so long. Is there a settin
> On 22 Aug 2024, at 11:36, Patrick O'Callaghan wrote:
>
> When I reboot the system, there's a delay of around a minute before
> anything happens. This is a single-user desktop and I really don't need
> to stare at a spinner for so long. Is there a setting somewhere that
> lets me change this?
Patrick O'Callaghan writes:
When I reboot the system, there's a delay of around a minute before
anything happens. This is a single-user desktop and I really don't need
to stare at a spinner for so long. Is there a setting somewhere that
lets me change this? I'm aware of 'reboot -f' but I assume
On Thu, Aug 22, 2024 at 7:36 AM Patrick O'Callaghan
wrote:
> When I reboot the system, there's a delay of around a minute before
> anything happens. This is a single-user desktop and I really don't need
> to stare at a spinner for so long. Is there a setting somewhere that
> lets me change this?
When I reboot the system, there's a delay of around a minute before
anything happens. This is a single-user desktop and I really don't need
to stare at a spinner for so long. Is there a setting somewhere that
lets me change this? I'm aware of 'reboot -f' but I assume that would
normally be too dras
36 matches
Mail list logo
