[Info-vax] New installment in The OpenVMS Consultant: Shutdowns using STARTUP.COM
Jan-Erik Söderholm
jan-erik.soderholm at telia.com
Tue Dec 29 04:32:53 EST 2020
Den 2020-12-28 kl. 17:48, skrev Stephen Hoffman:
> On 2020-12-28 12:48:45 +0000, Jan-Erik Søderholm said:
>
>> Den 2020-12-28 kl. 09:12, skrev Phillip Helbig (undress to reply):
>>> In article <rsbc8v$oiv$1 at dont-email.me>, Simon Clubley
>>> <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>>
>>>> On 2020-12-27, David Jones <osuvman50 at gmail.com> wrote:
>>>>>
>>>>> The biggest hazard to an orderly shutdown is that you terminal session
>>>>> goes when the network is shut off, leaving your system in a partially
>>>>> shutdown state.
>>>>> I changed my shutdown symbol from "@sys$system:shutdown ..." to
>>>>> "$SYSMAN SHUTDOWN NODE /minutes=..." (appending /auto/save as needed).
>>>>
>>>> That's another thing that Unix got right big time.
>>>>
>>>> I routinely reboot Linux servers from a SSH session to the server and
>>>> never have to worry about this.
>>>
>>> I think that at some point that was fixed on VMS.
>>
>> What was "fixed" in VMS? I do not remember anything that was fixed that
>> has any bearing on the issues with running SHUTDOWN.COM from an
>> interactive telnet or ssh session. Just do not do that. And it is easy to
>> avoid.
>
> Some of this shutdown "design" did get fixed.......
OK. Back on track, what was "fixed" around the issues with a lost
terminal session when doing a shutdown using a telnet or ssh session?
More information about the Info-vax
mailing list