[HECnet] PyDECnet
Wilm Boerhout
wboerhout at gmail.com
Fri Apr 16 10:42:33 PDT 2021
And ONAPI4:: (29.206) is now running that version, splendid!
Wilm
-----Original Message-----
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf Of
Paul Koning
Sent: Friday, April 16, 2021 7:20 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] PyDECnet
> On Apr 16, 2021, at 10:00 AM, Paul Koning <paulkoning at comcast.net> wrote:
>
>
>
>> On Apr 16, 2021, at 9:41 AM, Keith Halewood
<Keith.Halewood at pitbulluk.org> wrote:
>>
>> Hi,
>>
>> A general point about pyDECnet usage. I leave the default
'Identification' string alone so that anybody interested can discover the
version of pydecnet being used (SHOW EXEC CHAR). I have noticed that others
tend to personalise the string, often removing that version number. Would it
be possible to append your personalisation to the version rather than
replace it? From a trouble-shooting point of view, knowing that two routers
connected by a circuit are either same version or vastly different often
helps.
>>
>> Just a thought.
>>
>> Keith
>
> Interesting idea. Strictly speaking, that string is rather short, though
some other DECnet implementations send oversized values.
>
> Another option would be to have the version information be a separate
read-only parameter, that would be easy.
Done. It turns out a suitable parameter already exists in the standard,
parameter 126, "Software identification". As of rev 583 that will report
the PyDECnet version number.
paul
More information about the Hecnet-list
mailing list