🚀 go-pugleaf

gnb@duke.bby.oz.au (Gregory N. Bond) writes:
>I'm running Sun-III (Vn="1.519.21"), connecting to another SUN-III
>site.  I have been getting about 15 messages a day about bad state
>messages from tmx.mhs.oz / sol.jna.com, because sol is the name of the
>machine at deakin.  I understand that this is probably an artifact of
>the MHS->SUN-III gatewaying, but is there any way to avoid it?  Is it
>just me? I can see this getting much worse as other MHS sites pick
>conflicting names.  

As of yesterday I've given up listening to badhandler messages... due 
to this particular problem (>10 bad messages a day from tmx).

I mailed Piers and he said that this was another thing that SunIII just
couldn't cope with.

Now I direct these badhandler warnings to some obscure mailbox that I 
only look at occasionaly (eg: when /usr is getting full :-)   Pity, as 
now I won't get the really *important* ones when I need them.
(I'm contemplating building a simple mail filter for messages about
sites I just don't care about)

My question is also: *why* is tmx sending out so many messages a day?
I've seen this problem over and over again and I thought SunIV was
supposed to *help* in this regard (wrt SunIII).  Previously many
state messages a day have been sent out by SunIV sites that were deemed
to be misconfigured in some way.  Fair enough.  They were usually
fixed (I get no continual badhandler messages from any other site).
However tmx.mhs.oz is a site that I thought shouldn't be in this boat 
(I mean, hey, these people *sell* the product; shouldn't they be trying
to maintain compatability?)

With SunIII the state mesages were only about 300 bytes or so, but SunIV 
they're often 5-10 times larger.  Pity our modem bandwidth hasn't gone
up by the same factor in the last 5 years.

Ian D