Just noticed this when I used SSH to login:

$ ssh alex@kakapo

Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2

Last interactive login on Thursday, 4-APR-2024 21:57:38.46
Last non-interactive login on Wednesday, 17-NOV-1858 00:00:00.00

1858???? :-D
--
Tactical Nuclear Kittens

On 4/4/2024 4:59 PM, Single Stage to Orbit wrote:
> Just noticed this when I used SSH to login:
>
> $ ssh alex@kakapo
>
> Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2
>
> Last interactive login on Thursday, 4-APR-2024 21:57:38.46
> Last non-interactive login on Wednesday, 17-NOV-1858 00:00:00.00
>
> 1858???? :-D

17-NOV-1858 00:00:00.00

Isn't that the start of the VMS epoch?

bill

On Thu, 2024-04-04 at 17:18 -0400, bill wrote:
> On 4/4/2024 4:59 PM, Single Stage to Orbit wrote:
> > Just noticed this when I used SSH to login:
> >
> > $ ssh alex@kakapo
> >
> >   Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2
> >
> >      Last interactive login on Thursday,  4-APR-2024 21:57:38.46
> >      Last non-interactive login on Wednesday, 17-NOV-1858
> > 00:00:00.00
> >
> > 1858???? :-D
>
>
> 17-NOV-1858 00:00:00.00
>
> Isn't that the start of the VMS epoch?

It's odd because I checked and the date/time were correct. Not sure why
that happened.
--
Tactical Nuclear Kittens

On 4/4/2024 6:12 PM, Single Stage to Orbit wrote:
> On Thu, 2024-04-04 at 17:18 -0400, bill wrote:
>> On 4/4/2024 4:59 PM, Single Stage to Orbit wrote:
>>> Just noticed this when I used SSH to login:
>>>
>>> $ ssh alex@kakapo
>>>
>>>   Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2
>>>
>>>      Last interactive login on Thursday,  4-APR-2024 21:57:38.46
>>>      Last non-interactive login on Wednesday, 17-NOV-1858
>>> 00:00:00.00
>>>
>>> 1858???? :-D
>>
>>
>> 17-NOV-1858 00:00:00.00
>>
>> Isn't that the start of the VMS epoch?
>
> It's odd because I checked and the date/time were correct. Not sure why
> that happened.

I think it is what happens if the field is zero. So if there has been
no non-interactive logins then I guess it is sort of as expected. If
you submit a batch job as ALEX does it change to the time of the batch
job?

Arne

On Thu, 2024-04-04 at 18:42 -0400, Arne Vajhøj wrote:
> > It's odd because I checked and the date/time were correct. Not sure
> > why that happened.
>
> I think it is what happens if the field is zero. So if there has been
> no non-interactive logins then I guess it is sort of as expected. If
> you submit a batch job as ALEX does it change to the time of the
> batch job?

Ah, you might be right, that could be it. Netherless, its just odd.
--
Tactical Nuclear Kittens

On 4/4/2024 6:42 PM, Arne Vajhøj wrote:
> On 4/4/2024 6:12 PM, Single Stage to Orbit wrote:
>> On Thu, 2024-04-04 at 17:18 -0400, bill wrote:
>>> On 4/4/2024 4:59 PM, Single Stage to Orbit wrote:
>>>> Just noticed this when I used SSH to login:
>>>>
>>>> $ ssh alex@kakapo
>>>>
>>>>    Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2
>>>>
>>>>       Last interactive login on Thursday,  4-APR-2024 21:57:38.46
>>>>       Last non-interactive login on Wednesday, 17-NOV-1858
>>>> 00:00:00.00
>>>>
>>>> 1858???? :-D
>>>
>>>
>>> 17-NOV-1858 00:00:00.00
>>>
>>> Isn't that the start of the VMS epoch?
>>
>> It's odd because I checked and the date/time were correct. Not sure why
>> that happened.
>
> I think it is what happens if the field is zero. So if there has been
> no non-interactive logins then I guess it is sort of as expected. If
> you submit a batch job as ALEX does it change to the time of the batch
> job?

$ type t.pas
[inherit('sys$library:starlet')]
program t(input,output);

var
tzero : integer64;
tstr : varying [255] of char;

begin
tzero := 0;
$asctim(tstr.length, tstr.body, tzero);
writeln(tstr);
end.
$ pas t
$ link t
$ run t
17-NOV-1858 00:00:00.00

Arne

On 2024-04-04, Single Stage to Orbit <alex.buell@munted.eu> wrote:
> Just noticed this when I used SSH to login:
>
> $ ssh alex@kakapo
>
> Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2
>
> Last interactive login on Thursday, 4-APR-2024 21:57:38.46
> Last non-interactive login on Wednesday, 17-NOV-1858 00:00:00.00
>
> 1858???? :-D

That needs reporting in the forum. That last line should be suppressed
when there is a zero date value in that VMS quad time field (which is
what the above date/time is).

It looks like a check for a zero (ie: missing) date/time is going wrong,
which is something that could have implications elsewhere.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 4/5/24 7:12 AM, Simon Clubley wrote:
> On 2024-04-04, Single Stage to Orbit <alex.buell@munted.eu> wrote:
>> Just noticed this when I used SSH to login:
>>
>> $ ssh alex@kakapo
>>
>> Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2
>>
>> Last interactive login on Thursday, 4-APR-2024 21:57:38.46
>> Last non-interactive login on Wednesday, 17-NOV-1858 00:00:00.00
>>
>> 1858???? :-D
>
> That needs reporting in the forum. That last line should be suppressed
> when there is a zero date value in that VMS quad time field (which is
> what the above date/time is).
>
> It looks like a check for a zero (ie: missing) date/time is going wrong,
> which is something that could have implications elsewhere.

If the display needs modification (debatable) it should not be
suppressed; it should say "never" because that's what the start of epoch
value has always meant in the UAF time fields.

On Fri, 2024-04-05 at 08:53 -0500, Craig A. Berry wrote:
> > It looks like a check for a zero (ie: missing) date/time is going
> > wrong, which is something that could have implications elsewhere.
>
> If the display needs modification (debatable) it should not be
> suppressed; it should say "never" because that's what the start of
> epoch value has always meant in the UAF time fields.

Correct answer.
--
Tactical Nuclear Kittens

On 2024-04-05, Craig A. Berry <craigberry@nospam.mac.com> wrote:
>
> On 4/5/24 7:12 AM, Simon Clubley wrote:
>> On 2024-04-04, Single Stage to Orbit <alex.buell@munted.eu> wrote:
>>> Just noticed this when I used SSH to login:
>>>
>>> $ ssh alex@kakapo
>>>
>>> Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2
>>>
>>> Last interactive login on Thursday, 4-APR-2024 21:57:38.46
>>> Last non-interactive login on Wednesday, 17-NOV-1858 00:00:00.00
>>>
>>> 1858???? :-D
>>
>> That needs reporting in the forum. That last line should be suppressed
>> when there is a zero date value in that VMS quad time field (which is
>> what the above date/time is).
>>
>> It looks like a check for a zero (ie: missing) date/time is going wrong,
>> which is something that could have implications elsewhere.
>
> If the display needs modification (debatable) it should not be
> suppressed; it should say "never" because that's what the start of epoch
> value has always meant in the UAF time fields.
>

When you login via another method (say LAT or CTERM), what is currently
shown on the last non-interactive login line when the account has never
had a non-interactive login ?

Does the answer change depending on whether it is VAX, Alpha, IA64,
or x86-64 ?

The above ssh on x86-64 example needs to match the current behaviour on
other architectures and other login protocols, IMHO.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.