Ralph Katz:
There is no "-t" option.
Jonathan de Boyne Pollard:
In fact there is. It's undocumented; and is one of four undocumented > compatibility options, alongside -a, -f, and -F, that are simply >
parsed and then ignored. There is a fifth undocumented option with an >
effect, -K.
David
Quoting Jonathan de Boyne Pollard (j.deboynepollard-newsgro...@ntlworld.com):
> Ralph Katz:
>
> >There is no "-t" option.
> >
>
> In fact there is. It's undocumented; and is one of four
> undocumented compatibility options, alongside -a, -f, and -F, that
> are simply parsed and then ignored. Th
The Wanderer:
I can certainly see the reasoning, though I'm not sure I wouldn't have
come down on the other side of that decision.
I actually have done myself, on occasion.
The Wanderer:
Wouldn't it at least make sense to print a message to the effect of
"warning, ignoring unsupported le
On 09/12/2015 06:29 PM, Jonathan de Boyne Pollard wrote:
> Ralph Katz:
>
>> There is no "-t" option.
>>
>
> In fact there is. It's undocumented; and is one of four undocumented
> compatibility options, alongside -a, -f, and -F, that are simply parsed
> and then ignored. There is a fifth undocum
On 2015-09-12 at 18:36, Jonathan de Boyne Pollard wrote:
> The Wanderer:
>
>> It's still odd / bothersome that systemd's shutdown would see the
>> unsupported / unrecognized '-t' option and just proceed blithely
>> along, rather than erroring out on the presumption that a mistake
>> may have been
The Wanderer:
there are plenty of hits explaining how to make systemd inhibit
shutdown or add a delay or the like, and a few hits related to Debian
bug 635777 (which seems to be about a delay after the shutdown has
actually begun, not about a delay in initiating the shutdown), but no
real use
David Wright:
I think the arguments have changed/been juggled/reduced. The lack of
-F is especially annoying.
They haven't been. All of the documented options to upstart's shutdown
command and the System 5 rc shutdown command are recognized, albeit that
four of them, including -F, are the
The Wanderer:
It's still odd / bothersome that systemd's shutdown would see the
unsupported / unrecognized '-t' option and just proceed blithely
along, rather than erroring out on the presumption that a mistake may
have been made.
It's an engineering choice, to not break existing scripts a
Ralph Katz:
There is no "-t" option.
In fact there is. It's undocumented; and is one of four undocumented
compatibility options, alongside -a, -f, and -F, that are simply parsed
and then ignored. There is a fifth undocumented option with an effect, -K.
On 2015-09-11 at 14:49, Ralph Katz wrote:
> On 09/11/2015 02:22 PM, The Wanderer wrote:
>
>> I've recently built a VM against jessie, and just for the heck of
>> it, I left it with the default systemd-based configuration.
>>
>> When I log in to the console as root and try to shut down, I get
>> t
Quoting The Wanderer (wande...@fastmail.fm):
> I've recently built a VM against jessie, and just for the heck of it, I
> left it with the default systemd-based configuration.
>
> When I log in to the console as root and try to shut down, I get the
> following:
>
>
> # shutdown -h -t 0
>
On Fri 11 Sep 2015 at 14:22:12 -0400, The Wanderer wrote:
> I've recently built a VM against jessie, and just for the heck of it, I
> left it with the default systemd-based configuration.
>
> When I log in to the console as root and try to shut down, I get the
> following:
>
>
> # shutd
On Fri, 11 Sep 2015, The Wanderer wrote:
> and an immediate shutdown (without even enough delay to log root out
> via Ctrl-D), which is what I get on my other systems, where systemd is
> not the active init system.
I suspect that the shutdown process has actually started immediately,
but that one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/11/2015 02:22 PM, The Wanderer wrote:
> I've recently built a VM against jessie, and just for the heck of
> it, I left it with the default systemd-based configuration.
>
> When I log in to the console as root and try to shut down, I get
> the
Hi.
On Fri, 11 Sep 2015 14:22:12 -0400
The Wanderer wrote:
> I've recently built a VM against jessie, and just for the heck of it, I
> left it with the default systemd-based configuration.
>
> When I log in to the console as root and try to shut down, I get the
> following:
>
>
> # s
I've recently built a VM against jessie, and just for the heck of it, I
left it with the default systemd-based configuration.
When I log in to the console as root and try to shut down, I get the
following:
# shutdown -h -t 0
Broadcast message from root@hostname (Fri 2015-09-11 14:08:29 E
16 matches
Mail list logo
