🚀 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.  

This is unavoidable for SUN III sites, and may well get worse if any
more sites with identical node names come onto the net. (Perfectly
reasonable for X.400 style names.) It's nothing to do with the MHS-SUN
gateways, and everything to do with the fact that SUN III can't handle
conflicting node names very well. I advise people with SUN III to just
ignore these messages, unless they affect a node name they usually
communicate with. (In which case you will have to override the toplogy
to ensure the node you really want is included and the conflicting one
you can ignore is excluded.)

If you are feeling brave -- since SUN III sites all have source code --
why not hack the code to not mail you about these errors?

 > Or will I just trash SUN-III and run something that works, like UUCP
 > (1/2 :-)

Running UUCP would certainly get rid of these messages :-)
--

Computer Science, Sydney University, Madsen Bldg F09, Sydney NSW 2006
Phone: +61 2 692 3423				  Fax: +61 2 692 3838