Greg Wooledge wrote:
> On Tue, Nov 22, 2022 at 06:22:57PM +0100, to...@tuxteam.de wrote:
>> Hm. With SysV, you can't either (spoiler alert: the shutdown process
>> itself is the one doing the timing by sleeping until fulfillment of
>> its task). But you always can cancel it (shutdown -c with SysV,
Sven Joachim writes:
> Perhaps that the --show option was only added in systemd 250 and is not
> available in Bullseye and older Debian releases.
Except as a backport, Bullseye backports has systemd 251.3.
Sven Joachim writes:
[...]
>
> Perhaps that the --show option was only added in systemd 250 and is not
> available in Bullseye and older Debian releases.
>
> Cheers,
>Sven
Ach, indeed. Sorry.
KJ
--
http://wolnelektury.pl/wesprzyj/teraz/
Kamil Joñca writes:
> kjonca@alfa:~%man shutdown
> SHUTDOWN(8)
>
> shutdown
>
On Tue, Nov 22, 2022 at 10:11:15PM +0100, Ximo wrote:
> El 22/11/2022 a las 13:23, Urs Thuermann escribió:
> > After shutdown -h I see no way to see this scheduled shutdown.
> > Before systemd, I could always see the shutdown process with its
> > arguments using ps(1).
> >
>
> # date --date @$(h
On Tue, 22 Nov 2022 21:11:55 +0100
Sven Joachim wrote:
> > kjonca@alfa:~%sudo shutdown --show
> > No scheduled shutdown.
> >
> > Am I overlooked something?
>
> Perhaps that the --show option was only added in systemd 250 and is
> not available in Bullseye and older Debian releases.
I certainl
El 22/11/2022 a las 13:23, Urs Thuermann escribió:
After shutdown -h I see no way to see this scheduled shutdown.
Before systemd, I could always see the shutdown process with its
arguments using ps(1).
# date --date @$(head -1 /run/systemd/shutdown/scheduled |cut -c6-15)
On 2022-11-22 20:18 +0100, Kamil Jońca wrote:
> Urs Thuermann writes:
>
>> After shutdown -h I see no way to see this scheduled shutdown.
>> Before systemd, I could always see the shutdown process with its
>> arguments using ps(1).
>
> Hm.
> kjonca@alfa:~%man shutdown
> SHUTDOWN(8)
On Tue, Nov 22, 2022 at 08:18:31PM +0100, Kamil Jońca wrote:
> Urs Thuermann writes:
>
> > After shutdown -h I see no way to see this scheduled shutdown.
> > Before systemd, I could always see the shutdown process with its
> > arguments using ps(1).
>
> Hm.
> kjonca@alfa:~%man shutdown
> SHUTDO
Urs Thuermann writes:
> After shutdown -h I see no way to see this scheduled shutdown.
> Before systemd, I could always see the shutdown process with its
> arguments using ps(1).
Hm.
kjonca@alfa:~%man shutdown
SHUTDOWN(8)
On Tue, Nov 22, 2022 at 12:29:49PM -0500, Greg Wooledge wrote:
> On Tue, Nov 22, 2022 at 06:22:57PM +0100, to...@tuxteam.de wrote:
> > Hm. With SysV, you can't either [change the time, but you can cancel]
> The systemd shutdown(8) man page has a -c option for canceling a pending
> shutdown. I hav
On Tue, Nov 22, 2022 at 06:22:57PM +0100, to...@tuxteam.de wrote:
> Hm. With SysV, you can't either (spoiler alert: the shutdown process
> itself is the one doing the timing by sleeping until fulfillment of
> its task). But you always can cancel it (shutdown -c with SysV, dunno,
> again, with syste
On Tue, Nov 22, 2022 at 09:09:56AM -0600, David Wright wrote:
> On Tue 22 Nov 2022 at 15:56:48 (+0100), to...@tuxteam.de wrote:
> > On Tue, Nov 22, 2022 at 08:48:25AM -0600, David Wright wrote:
> >
> > [...]
> >
> > > There's a file, "scheduled", that's created in /run/systemd/shutdown,
> > > whi
On Tue, 22 Nov 2022 09:09:56 -0600
David Wright wrote:
> > > I haven't tried editing, say, the noisiness, to see whether I can
> > > stop the flow of Wall messages on all my xterms.
> >
> > *My* shutdown has a command line option (-Q) for the latter. Dunno
> > about yours ;-)
>
> # shutdown
On Tue 22 Nov 2022 at 15:56:48 (+0100), to...@tuxteam.de wrote:
> On Tue, Nov 22, 2022 at 08:48:25AM -0600, David Wright wrote:
>
> [...]
>
> > There's a file, "scheduled", that's created in /run/systemd/shutdown,
> > which contains the time, noisiness and destiny of the shutdown.
> > I haven't t
On Tue, Nov 22, 2022 at 08:48:25AM -0600, David Wright wrote:
[...]
> There's a file, "scheduled", that's created in /run/systemd/shutdown,
> which contains the time, noisiness and destiny of the shutdown.
> I haven't tried editing, say, the noisiness, to see whether I can stop
> the flow of Wall
On Tue 22 Nov 2022 at 13:23:14 (+0100), Urs Thuermann wrote:
> After shutdown -h I see no way to see this scheduled shutdown.
> Before systemd, I could always see the shutdown process with its
> arguments using ps(1).
>
> Now, the call to shutdown returns to the shell immediately leaving no
> pro
17 matches
Mail list logo
