EISNER will be down from 12-JUL-2023 through, hopefully, not past
17-JUL-2023. Rob sent the following to me:

VSI is moving to a different colocation facility next week.

The system will be shut down late morning eastern time on
Wednesday, and come up sometime over the weekend.

We'll have to change the IP address in DNS, and I don't have that yet,
so I'm not exactly sure when that'll happen.

Hopefully we'll get everything squared away soon after this weekend.

--
Hunter
------
Hunter Goatley, Process Software, http://www.process.com/
goathunter@goatley.com http://hunter.goatley.com/

On 7/11/2023 7:22 AM, Hunter Goatley wrote:
> EISNER will be down from 12-JUL-2023 through, hopefully, not past 17-JUL-2023. Rob sent the following to me:
>
>         VSI is moving to a different colocation facility next week.
>
>         The system will be shut down late morning eastern time on
>         Wednesday, and come up sometime over the weekend.
>
> We'll have to change the IP address in DNS, and I don't have that yet, so I'm not exactly sure when that'll happen.
>
> Hopefully we'll get everything squared away soon after this weekend.
>

VSI Sent out a notice today for their SFTP server being down as well but muffed the date and put June 12 - 14th instead of July.

Probably most will figure it out anyway.

John H. Reinhardt

> Probably most will figure it out anyway.

I figured that they meant June next year.

On Tue, 2023-07-11 at 22:10 -0700, Steven Schweda wrote:
> > Probably most will figure it out anyway.
>
>    I figured that they meant June next year.

At least they didn't use US centric dates.
--
Tactical Nuclear Kittens

In article <b184dd587e0796f96e087c76c5d8e1e43cd0e3cd.camel@munted.eu>,
alex.buell@munted.eu (Single Stage to Orbit) wrote:

> At least they didn't use US centric dates.

The VMS date format, as per the subject line, was first standardised by
the US Department of Defense. They picked it because it isn't anyone's
native format, but everyone can understand it.

I work for a British branch of a US-based company that's owned by a
German firm. I use VMS format dates for all official communications, even
though we haven't had VMS running for over twenty years.

John

On Wed, 2023-07-12 at 12:21 +0100, John Dallman wrote:
> > At least they didn't use US centric dates.
>
> The VMS date format, as per the subject line, was first standardised
> by the US Department of Defense. They picked it because it isn't
> anyone's native format, but everyone can understand it.
>
> I work for a British branch of a US-based company that's owned by a
> German firm. I use VMS format dates for all official communications,
> even though we haven't had VMS running for over twenty years.

It's perfect.
--
Tactical Nuclear Kittens

On 12/07/2023 13:30, Single Stage to Orbit wrote:
> On Wed, 2023-07-12 at 12:21 +0100, John Dallman wrote:
>>> At least they didn't use US centric dates.
>>
>> The VMS date format, as per the subject line, was first standardised
>> by the US Department of Defense. They picked it because it isn't
>> anyone's native format, but everyone can understand it.
>>
>> I work for a British branch of a US-based company that's owned by a
>> German firm. I use VMS format dates for all official communications,
>> even though we haven't had VMS running for over twenty years.
>
> It's perfect.

That is of course one form of standard UK date. I also regularly use the
DEC comparison format, aka Japanese date, of YYYY-MM-DD as sortable, and
also unmistakeable

--
Chris

Den 2023-07-12 kl. 15:12, skrev Chris Townley:
> On 12/07/2023 13:30, Single Stage to Orbit wrote:
>> On Wed, 2023-07-12 at 12:21 +0100, John Dallman wrote:
>>>> At least they didn't use US centric dates.
>>>
>>> The VMS date format, as per the subject line, was first standardised
>>> by the US Department of Defense. They picked it because it isn't
>>> anyone's native format, but everyone can understand it.
>>>
>>> I work for a British branch of a US-based company that's owned by a
>>> German firm. I use VMS format dates for all official communications,
>>> even though we haven't had VMS running for over twenty years.
>>
>> It's perfect.
>
> That is of course one form of standard UK date. I also regularly use the
> DEC comparison format, aka Japanese date, of YYYY-MM-DD as sortable, and
> also unmistakeable
>

Which is also the international ISO-8601 standard date/time format.

https://en.wikipedia.org/wiki/ISO_8601.

Not sure why you call it "Japanese date". Japan is just one of approx.
50 countries that has adopted ISO-8601 as its national standard.
But there is nothing else ”Japanese” about this format.

To simplify everything, it would be better to use the ISO-6801 standard.

ISO-8601 has also been adopted as an US national standard:
ANSI INCITS 30-1997 (R2008) and NIST FIPS PUB 4-2.

See the link above for further details…

On 12/07/2023 15:07, Jan-Erik Söderholm wrote:
> Den 2023-07-12 kl. 15:12, skrev Chris Townley:
>> On 12/07/2023 13:30, Single Stage to Orbit wrote:
>>> On Wed, 2023-07-12 at 12:21 +0100, John Dallman wrote:
>>>>> At least they didn't use US centric dates.
>>>>
>>>> The VMS date format, as per the subject line, was first standardised
>>>> by the US Department of Defense. They picked it because it isn't
>>>> anyone's native format, but everyone can understand it.
>>>>
>>>> I work for a British branch of a US-based company that's owned by a
>>>> German firm. I use VMS format dates for all official communications,
>>>> even though we haven't had VMS running for over twenty years.
>>>
>>> It's perfect.
>>
>> That is of course one form of standard UK date. I also regularly use
>> the DEC comparison format, aka Japanese date, of YYYY-MM-DD as
>> sortable, and also unmistakeable
>>
>
> Which is also the international ISO-8601 standard date/time format.
>
> https://en.wikipedia.org/wiki/ISO_8601.
>
> Not sure why you call it "Japanese date". Japan is just one of approx.
> 50 countries that has adopted ISO-8601 as its national standard.
> But there is nothing else ”Japanese” about this format.
>
> To simplify everything, it would be better to use the ISO-6801 standard.
>
> ISO-8601 has also been adopted as an US national standard:
> ANSI INCITS 30-1997 (R2008) and NIST FIPS PUB 4-2.
>
> See the link above for further details…
>

I started using it before ISO-8601 (first published 1988), when it was
the Japanese date format.

--
Chris

On 2023-07-12 17:27, Chris Townley wrote:
> On 12/07/2023 15:07, Jan-Erik Söderholm wrote:
>> Den 2023-07-12 kl. 15:12, skrev Chris Townley:
>>> On 12/07/2023 13:30, Single Stage to Orbit wrote:
>>>> On Wed, 2023-07-12 at 12:21 +0100, John Dallman wrote:
>>>>>> At least they didn't use US centric dates.
>>>>>
>>>>> The VMS date format, as per the subject line, was first standardised
>>>>> by the US Department of Defense. They picked it because it isn't
>>>>> anyone's native format, but everyone can understand it.
>>>>>
>>>>> I work for a British branch of a US-based company that's owned by a
>>>>> German firm. I use VMS format dates for all official communications,
>>>>> even though we haven't had VMS running for over twenty years.
>>>>
>>>> It's perfect.
>>>
>>> That is of course one form of standard UK date. I also regularly use
>>> the DEC comparison format, aka Japanese date, of YYYY-MM-DD as
>>> sortable, and also unmistakeable
>>>
>>
>> Which is also the international ISO-8601 standard date/time format.
>>
>> https://en.wikipedia.org/wiki/ISO_8601.
>>
>> Not sure why you call it "Japanese date". Japan is just one of approx.
>> 50 countries that has adopted ISO-8601 as its national standard.
>> But there is nothing else ”Japanese” about this format.
>>
>> To simplify everything, it would be better to use the ISO-6801 standard.
>>
>> ISO-8601 has also been adopted as an US national standard:
>> ANSI INCITS 30-1997 (R2008) and NIST FIPS PUB 4-2.
>>
>> See the link above for further details…
>>
>
> I started using it before ISO-8601 (first published 1988), when it was
> the Japanese date format.

It was in use in Sweden before that time as well. Just because ISO
published a document about it don't mean it wasn't in existance and used
before then, by multiple countries. (I have no idea how long Sweden have
been using this format, but it feels like forever...)

Johnny

On Wed, 2023-07-12 at 14:12 +0100, Chris Townley wrote:
> > It's perfect.
>
> That is of course one form of standard UK date. I also regularly use
> the DEC comparison format, aka Japanese date, of YYYY-MM-DD as
> sortable,and also unmistakeable

Aka ISO-8601 (https://www.iso.org/iso-8601-date-and-time-format.html)
We use it all the time as searchable timestamps (with delimiters
stripped out)
--
Tactical Nuclear Kittens

On 7/12/2023 12:52 PM, Johnny Billquist wrote:
> On 2023-07-12 17:27, Chris Townley wrote:
>> On 12/07/2023 15:07, Jan-Erik Söderholm wrote:
>>> Den 2023-07-12 kl. 15:12, skrev Chris Townley:
>>>> On 12/07/2023 13:30, Single Stage to Orbit wrote:
>>>>> On Wed, 2023-07-12 at 12:21 +0100, John Dallman wrote:
>>>>>>> At least they didn't use US centric dates.
>>>>>>
>>>>>> The VMS date format, as per the subject line, was first standardised
>>>>>> by the US Department of Defense. They picked it because it isn't
>>>>>> anyone's native format, but everyone can understand it.
>>>>>>
>>>>>> I work for a British branch of a US-based company that's owned by a
>>>>>> German firm. I use VMS format dates for all official communications,
>>>>>> even though we haven't had VMS running for over twenty years.
>>>>>
>>>>> It's perfect.
>>>>
>>>> That is of course one form of standard UK date. I also regularly use the DEC
>>>> comparison format, aka Japanese date, of YYYY-MM-DD as sortable, and also
>>>> unmistakeable
>>>>
>>>
>>> Which is also the international ISO-8601 standard date/time format.
>>>
>>> https://en.wikipedia.org/wiki/ISO_8601.
>>>
>>> Not sure why you call it "Japanese date". Japan is just one of approx.
>>> 50 countries that has adopted ISO-8601 as its national standard.
>>> But there is nothing else ”Japanese” about this format.
>>>
>>> To simplify everything, it would be better to use the ISO-6801 standard.
>>>
>>> ISO-8601 has also been adopted as an US national standard:
>>> ANSI INCITS 30-1997 (R2008) and NIST FIPS PUB 4-2.
>>>
>>> See the link above for further details…
>>>
>>
>> I started using it before ISO-8601 (first published 1988), when it was the
>> Japanese date format.
>
> It was in use in Sweden before that time as well. Just because ISO published a
> document about it don't mean it wasn't in existance and used before then, by
> multiple countries. (I have no idea how long Sweden have been using this format,
> but it feels like forever...)
>
> Johnny
>

Are we discussing DD-Mon-YYYY or YYYYMMDD ?

RSTS from the beginning used DD-Mon-YY, only 2 digits for the yesr, but same
format. That was prior to 1974, not sure how long before.

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

On 7/12/2023 7:21 AM, John Dallman wrote:
> In article <b184dd587e0796f96e087c76c5d8e1e43cd0e3cd.camel@munted.eu>,
> alex.buell@munted.eu (Single Stage to Orbit) wrote:
>> At least they didn't use US centric dates.
>
> The VMS date format, as per the subject line, was first standardised by
> the US Department of Defense. They picked it because it isn't anyone's
> native format, but everyone can understand it.
>
> I work for a British branch of a US-based company that's owned by a
> German firm. I use VMS format dates for all official communications, even
> though we haven't had VMS running for over twenty years.

I use VMS date format all the time.

When communicating a date to a group spread out over both
US and Europe, then it is a nice unambiguous format.

So it has become a habit and I use it everywhere. Also when
writing a check or dating signature on some stupid form!

Arne

On 7/12/2023 6:49 PM, Arne Vajhøj wrote:
>
>
> So it has become a habit and I use it everywhere. Also when
> writing a check or dating signature on some stupid form!
>

Most forms I have to fill out specify the date format they require.
Using something else usually results in having to do it all over
again.

bill

On 2023-07-12 20:13, Dave Froble wrote:
> On 7/12/2023 12:52 PM, Johnny Billquist wrote:
>> On 2023-07-12 17:27, Chris Townley wrote:
>>> On 12/07/2023 15:07, Jan-Erik Söderholm wrote:
>>>> Den 2023-07-12 kl. 15:12, skrev Chris Townley:
>>>>> On 12/07/2023 13:30, Single Stage to Orbit wrote:
>>>>>> On Wed, 2023-07-12 at 12:21 +0100, John Dallman wrote:
>>>>>>>> At least they didn't use US centric dates.
>>>>>>>
>>>>>>> The VMS date format, as per the subject line, was first standardised
>>>>>>> by the US Department of Defense. They picked it because it isn't
>>>>>>> anyone's native format, but everyone can understand it.
>>>>>>>
>>>>>>> I work for a British branch of a US-based company that's owned by a
>>>>>>> German firm. I use VMS format dates for all official communications,
>>>>>>> even though we haven't had VMS running for over twenty years.
>>>>>>
>>>>>> It's perfect.
>>>>>
>>>>> That is of course one form of standard UK date. I also regularly
>>>>> use the DEC
>>>>> comparison format, aka Japanese date, of YYYY-MM-DD as sortable,
>>>>> and also
>>>>> unmistakeable
>>>>>
>>>>
>>>> Which is also the international ISO-8601 standard date/time format.
>>>>
>>>> https://en.wikipedia.org/wiki/ISO_8601.
>>>>
>>>> Not sure why you call it "Japanese date". Japan is just one of approx.
>>>> 50 countries that has adopted ISO-8601 as its national standard.
>>>> But there is nothing else ”Japanese” about this format.
>>>>
>>>> To simplify everything, it would be better to use the ISO-6801
>>>> standard.
>>>>
>>>> ISO-8601 has also been adopted as an US national standard:
>>>> ANSI INCITS 30-1997 (R2008) and NIST FIPS PUB 4-2.
>>>>
>>>> See the link above for further details…
>>>>
>>>
>>> I started using it before ISO-8601 (first published 1988), when it
>>> was the
>>> Japanese date format.
>>
>> It was in use in Sweden before that time as well. Just because ISO
>> published a
>> document about it don't mean it wasn't in existance and used before
>> then, by
>> multiple countries. (I have no idea how long Sweden have been using
>> this format,
>> but it feels like forever...)
>>
>>   Johnny
>>
>
> Are we discussing DD-Mon-YYYY or YYYYMMDD ?
>
> RSTS from the beginning used DD-Mon-YY, only 2 digits for the yesr, but
> same format.  That was prior to 1974, not sure how long before.

The ISO standard is YYYY-MM-DD, which was called "Japanese date" for
some obscure reason above.

I think the DD-Mmm-YY(YY) format was sortof a DEC standard format. I
think almost all DEC OSes used that in the past, and still do.
It's good since it's pretty unambiguous.

In RSX these days, you can actually choose which date format to use:

DD-Mmm-YY
DD-Mmm-YYYY
YYYY-MM-DD

And programs that take date as input usually accept all three formats,
with the year being inferred if just two digits are used.

Johnny

On Tuesday, July 11, 2023 at 8:22:46 AM UTC-4, Hunter Goatley wrote:
> EISNER will be down from 12-JUL-2023 through, hopefully, not past
> 17-JUL-2023. Rob sent the following to me:
>
> VSI is moving to a different colocation facility next week.
>
> The system will be shut down late morning eastern time on
> Wednesday, and come up sometime over the weekend.
>
> We'll have to change the IP address in DNS, and I don't have that yet,
> so I'm not exactly sure when that'll happen.
>
> Hopefully we'll get everything squared away soon after this weekend.
>
> --
> Hunter
> ------
> Hunter Goatley, Process Software, http://www.process.com/
> goath...@goatley.com http://hunter.goatley.com/

Is there any word on progress?

On 7/17/2023 9:09 AM, Cliff Chipman wrote:
>
> Is there any word on progress?

I was told the system would be booted today, but it hasn't been yet, and
I've heard nothing more yet.

--
Hunter
------
Hunter Goatley, Process Software, http://www.process.com/
goathunter@goatley.com http://hunter.goatley.com/

EISNER is back up now!

Hunter

On 18/7/2023 1:38 am, Hunter Goatley wrote:
> On 7/17/2023 9:09 AM, Cliff Chipman wrote:
>>
>> Is there any word on progress?
>
> I was told the system would be booted today, but it hasn't been yet, and
> I've heard nothing more yet.

Online 3 hours ago.

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.

On 11/7/2023 9:52 pm, Hunter Goatley wrote:
> EISNER will be down from 12-JUL-2023 through, hopefully, not past
> 17-JUL-2023. Rob sent the following to me:
>
> VSI is moving to a different colocation facility next week.
>
> The system will be shut down late morning eastern time on
> Wednesday, and come up sometime over the weekend.
>
> We'll have to change the IP address in DNS, and I don't have that yet,
> so I'm not exactly sure when that'll happen.
>
> Hopefully we'll get everything squared away soon after this weekend.

and

On 15/8/2023 6:40 am, Hunter Goatley wrote:
> On 8/14/2023 8:39 AM, Simon Clubley wrote:
>>
>> Every so often, Eisner's network services (including SSH) simply stop
>> working. Sometimes, basic stuff such as ICMP continues to work, but
>> anything involving process creation is utterly stuffed.
>
> Lately, it's been a problem of EISNER seeing an unprecedented (per
> EISNER's history) level of dictionary attacks via SSH and SMTP. I've
> had to increase quotas for MultiNet's Intrusion Prevention Service
> process to try to keep up with the events. Each time, I've thought,
> "Well, that should be enough," and then the number of attacks grows,
> and it's not.

FWIW the new colocation has reduced .au <--> .us RTT by some 40%.
WASD's Server Admin interface contains an RTT calculation (top lines of
bottom-right panel)

https://wasd.vsm.com.au/wasd_root/wasdoc/features/admin.png

which now consistently reports this ~320mS where previously ~520mS.

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.

On 8/16/2023 7:27 PM, Mark Daniel wrote:

> FWIW the new colocation has reduced .au <--> .us RTT by some 40%.
> WASD's Server Admin interface contains an RTT calculation (top lines of
> bottom-right panel)
>
> https://wasd.vsm.com.au/wasd_root/wasdoc/features/admin.png
>
> which now consistently reports this ~320mS where previously ~520mS.

We are very pleased with the new colo facility!

--

--- Rob

On 17/8/2023 9:02 am, Robert A. Brooks wrote:
> On 8/16/2023 7:27 PM, Mark Daniel wrote:
>
>> FWIW the new colocation has reduced .au <--> .us RTT by some 40%.
>> WASD's Server Admin interface contains an RTT calculation (top lines
>> of bottom-right panel)
>>
>> https://wasd.vsm.com.au/wasd_root/wasdoc/features/admin.png
>>
>> which now consistently reports this ~320mS where previously ~520mS.
>
> We are very pleased with the new colo facility
A notable change to c.o.v. RTT as well :-|

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.