Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!cornell!rochester!PT.CS.CMU.EDU!cadre!pitt!darth!formtek!ditka!kls
From: kls@ditka.UUCP (Karl Swartz)
Newsgroups: comp.mail.uucp
Subject: Re: Pathalias vs reality
Message-ID: <130@ditka.UUCP>
Date: 3 Mar 88 08:44:38 GMT
References: <3008@fluke.COM>
Reply-To: kls@ditka.UUCP (Karl Swartz)
Organization: Pittsburgh Fish Hackery, Pittburgh, PA
Lines: 31
Summary: Faster routes and dead {} are overrides

In article <3008@fluke.COM> jeff@tc.fluke.COM (Jeff Stearns) writes:
>How do I gracefully change my map data?  I have many uucp neighbors.  The
>configuration changes from week to week, so the published pathalias data is
>always somewhat out-of-date.
>
>What is the proper way to merge my path.local data with the comp.mail.maps data?
>
>For example, I'd like pathalias to understand that my path.local file always
>has precedence over anything posted to comp.mail.maps.

Two things.  If the published maps say

	fluke	foo(HOURLY), bar(HOURLY)

and you now call foo on demand and have dropped your link to bar,
your path.local file should look like this:

	fluke	foo(DEMAND)
	dead	{fluke!bar}

Pathalias will always use the fastest route, so your declaration
for fluke!foo will effectively override the published one.  And
the 'dead' declaration will override anything elsewhere in the
maps.  When the lack of connection to bar finally propogates to
the maps, you can remove the 'dead' line.

-- 
Karl Swartz		|UUCP	decvax!formtek!ditka!kls
1-412/937-4930 office	|	{floyd,pitt,psuvax1}!idis!formtek!ditka!kls
			|BIX	kswartz
"I never let my schooling get in the way of my education."  (Twain)