joe@petsd.UUCP (Joe Orost) (02/05/85)
Now that we have a program for building a nice database of low-cost paths,
the uucp map entries need to be checked and updated.
THIS IS YOUR JOB AS NEWS ADMINISTRATOR!
If you want the lowest cost path through your machine to be used, your map
entry needs to be correct - including the cost fields. Please mail the
updated entry to "{akgua,ihnp4,ulysses}!cbosgd!uucpmap".
You will find all the info you need to build the entries in the manual page
which follows. Just a note on the costs: Use the number that indicates how
costly (time+$) it is to send mail to the target system. If you call them
on demand, and also poll them, your entry should say "DIRECT" or "DEMAND";
their entry should say "HOURLY", "EVENING", or "DAILY". Don't mix the
symbols except with the possability of adding "+LOW" for a little more cost,
or "+HIGH" for a little less. For example, here is my updated entry:
#N petsd
#S Perkin-Elmer 3230, Edition VII
#O Perkin-Elmer DSG
#C Joseph M. Orost
#E petsd!joe
#T (201) 870-5844
#P MS313, Perkin-Elmer, 106 Apple St., Tinton Falls, NJ 07724
#L 40 19'49" N / 74 04'37" W
#R
#W Joe Orost 2/5/85
#
# btlunix is a toll call in NJ. peora is in FL.
# pesnta and pesdgc are in CA.
#
petsd vax135(DIRECT), moncol(DIRECT), petfa(LOCAL),
petfe(LOCAL), pesnta(DEMAND+LOW), peora(DEMAND),
pedsgd(DIRECT), pesdgc(DEMAND+LOW), pedsgb(DIRECT),
btlunix(DEMAND+HIGH)
----------------------------------------------------------------------
PATHALIAS(1) UNIX 5.0 PATHALIAS(1)
NAME
pathalias - compute shortest paths
SYNOPSIS
pathalias [ -vcibp ] [ -l host] [ -d link] [ -P file]
[inputfiles ...]
DESCRIPTION
Pathalias computes the shortest paths and corresponding
routes from one host to all other known, reachable hosts.
Pathalias expects as input a sequence of host-to-host
connectivity information, with a host name in column 1,
followed by white space, followed by a comma-separated list
of links (also host names), denoting a connection from the
host to the links. Connections are assumed to be
unidirectional. A link-name may be preceded or followed by
a network character to use in the path name. Valid network
characters are '!', '@', ':', and '%'. The link-name (and
network character, if present) may be followed by a ``cost''
in parentheses.
For example,
down princeton!(DEDICATED)
princeton topaz!(DEMAND+LOW)
topaz @rutgers(LOCAL)
Costs may be arbitrary arithmetic expressions involving
numbers, parentheses, '+', '-', '*', and '/'. Several
symbolic numbers are defined, as follows:
LOCAL 25 (local-area network connection)
DEDICATED 95 (high speed dedicated link)
DIRECT 200 (local call)
DEMAND 300 (normal call)
HOURLY 500 (hourly poll)
EVENING 1800 (time restricted call)
DAILY 5000 (daily poll)
WEEKLY 30000 (irregular poll)
In addition, DEAD is a very large number (effectively
infinite), and HIGH and LOW are -5 and +5 respectively, for
baud-rate or quality bonuses/penalties.
The numbers are intended to represent frequency of
connection, which seems to be far more important than baud
rates for this type of traffic. There is an assumed high
overhead for each hop; thus, e.g., HOURLY is far more than
DAILY / 24.
Aliases may be indicated by including lines of the form
name = alias [ , alias...]
The primary name is used in the output.
Page 1 (printed 2/5/85)
PATHALIAS(1) UNIX 5.0 PATHALIAS(1)
Fully connected networks, such as the ARPANET or a LAN, are
indicated by
net = {host, host, ...}
The host-list may be preceded or followed by a routing
character, and may be followed by a cost:
PrincetonCable = {up, down, yoyo, flakey, quirky, princeton, panic}!(LOCAL)
ARPA = @{sri-unix, mit-ai, su-score}(DEDICATED)
Anything following # on an input line is ignored. A line
that begins with white space is taken as a continuation of
the previous line.
The output, which appears on the standard output, is a list
of host-route pairs, where route is a string appropriate for
use with printf(3), e.g.
rutgers princeton!topaz!%s@rutgers
The ``%s'' in the route string should be replaced by the
user name at the destination host. (This task is normally
performed by a mailer.)
The name of a network is never used in expansions; thus, in
the above example, sri-unix's path to mit-ai would be
'%s@mit-ai', not '%s@ARPA@mit-ai'.
Options:
-i Map all host names to lower case.
-b Create a dbm(3) database as output.
-p Print output on stdout even if -b is specified.
-c Print the costs of paths.
-v Report some statistics on stderr.
-l host
Use host as local host name.
-P file
Use ``file'' as the name of the dbm(3) database. The
database key is host name, the stored value is a
(null-terminated) path.
-d link
Declares a dead link, host, or network. If link is of
the form host1!host2, the link from host1 to host2 is
treated as an extremely high cost (i.e., dead) link.
If link is a single host name, that host is treated as
dead and will be used as an intermediate host of last
resort on any path. If link is a network name, the
network requires a gateway.
Page 2 (printed 2/5/85)
PATHALIAS(1) UNIX 5.0 PATHALIAS(1)
Gateways. Normally, a network is represented by a pseudo-
host with bidirectional links to network members. The links
from pseudo-host to the members have the weight given in the
input (or the default cost), while the links from the
members to the pseudo-host have zero cost. Networks that
are declared dead on the command line show these latter
weights as very expensive links, effectively prohibiting
paths within the network. In this case, the input should
also show a link from some member(s) to the network; these
hosts will act as gateways for the network. E.g., if CSNET
is declared dead on the command line (with the -d flag) and
the input contains
CSNET = {...}
csnet-relay CSNET
then routes to CSNET hosts will use csnet-relay as a
gateway, rather than some other csnet host that may not be
able to act as a gateway.
FILES
/usr/local/lib/palias.{dir,pag} default dbm output
COMPILE-TIME
Edit config.h to accommodate UNIX variants.
AUTHORS
Steve Bellovin (ulysses!smb)
Peter Honeyman (princeton!honey)
Page 3 (printed 2/5/85)
regards,
joe
--
Full-Name: Joseph M. Orost
UUCP: ..!{decvax,ucbvax,ihnp4}!vax135!petsd!joe
ARPA: vax135!petsd!joe@BERKELEY
US Mail: MS 313; Perkin-Elmer; 106 Apple St; Tinton Falls, NJ 07724
Phone: (201) 870-5844
Location: 40 19'49" N / 74 04'37" Wkarsh@geowhiz.UUCP (Bruce Karsh) (02/24/85)
> For example, here is my updated entry: > > #N petsd > #S Perkin-Elmer 3230, Edition VII > #O Perkin-Elmer DSG > #C Joseph M. Orost > #E petsd!joe > #T (201) 870-5844 > #P MS313, Perkin-Elmer, 106 Apple St., Tinton Falls, NJ 07724 > #L 40 19'49" N / 74 04'37" W > #R > #W Joe Orost 2/5/85 > # > # btlunix is a toll call in NJ. peora is in FL. > # pesnta and pesdgc are in CA. > # > petsd vax135(DIRECT), moncol(DIRECT), petfa(LOCAL), > petfe(LOCAL), pesnta(DEMAND+LOW), peora(DEMAND), > pedsgd(DIRECT), pesdgc(DEMAND+LOW), pedsgb(DIRECT), > btlunix(DEMAND+HIGH) I have some questions about how to specify our uucp map entry. 1) I don't know what all the fields mean. Here are my guesses: #N uucp node name #S System description, both hardware and software. #O Organization name #C Name of contact person at site. #E Path name of contact person. (What does the E stand for?) #T Telephone number of contact person. #P Postal address of site. #L Lat. and Lon. of site. #R ??? #W ??? 2) I don't know what to do about the #L field. We could probably set up our sattelite navigation reciever and get an accurate enough value to seperate us from uwvax, across the street. But we plan to set up another system directly above (upstairs) from our current one. Shouldn't the #L field at least contain an elevation entry. And what happens when we put two machines next to each other. Do we *really* have to call the surveyors in, just to get on the network. :-) -- Bruce Karsh | Esperanto: the Universal Second Language U. Wisc. Dept. Geology and Geophysics | Easy to learn. Politically neutral. 1215 W Dayton, Madison, WI 53706 | Spoken by millions in 100 countries. (608) 262-1697 | 100 magazines, thousands of books. {ihnp4,seismo}!uwvax!geowhiz!karsh | Send for the Free Postal Course today!
mark@cbosgd.UUCP (Mark Horton) (02/26/85)
>> #N petsd Name of system >> #S Perkin-Elmer 3230, Edition VII System description >> #O Perkin-Elmer DSG Organization name >> #C Joseph M. Orost Contact person >> #E petsd!joe Electronic address of contact person (no fixed format yet, eventually 822) >> #T (201) 870-5844 Telephone of contact person >> #P MS313, Perkin-Elmer, 106 Apple St., Tinton Falls, NJ 07724 Postal address of contact person (added onto the end of #C and #O) >> #L 40 19 49 N / 74 04 37 W Lat&Long of host, in the format above >> #R Remarks. These can also be in additional # lines below. >> #W Joe Orost 2/5/85 Who last edited this and when > Do we *really* have to call the surveyors in, just to get on the network? Of course not. Just supply the information as accurately as you can. If the best you can do is the nearest minute, or tenth of a degree, fine. This will be used for drawing maps of the network. Most of our data is from an atlas looking up the L&L of the city (thanks go to Mark Brader, who just spent several days doing all of Usenet) so if you don't know, you can look it up in a city list which will be posted to the net soon. If you're using the city L&L, include the word "city": #L 40 19 N / 74 04 W city Mark Horton
spaf@gatech.UUCP (Gene Spafford) (02/26/85)
The fields are as follows:
#N = Name of site
#S = System (machine and OS)
#O = Organization
#C = Contact Person(s)
#E = Electronic mail address(es) of Contact Person(s)
#T = Telephone number(s) of Contact Person(s)
#P = Postal Address of Organization/Contact Person(s)
#L = Latitude and Longitude of site (optional)
#R = Remarks of interest (such as Usenet feeds, machine use, etc)
#W = Written by (last edit by)...and date
The other point that was made, about latitude and longitude, is somewhat
valid. Our latitude and longitude isn't enough once we set up sites
on other planets.... If you want to spend 1/2 hour and find a latitude
and longitude for your site, visit your nearest fair-sized library and
see if they have any U.S Geologic Survery maps for your area. Figuring
the latitude and logitude from the maps (for a value correct enough
for your map entry) is fairly simple. Many campus libraries will
also have these maps.
--
Gene "6 months and counting" Spafford
The Clouds Project, School of ICS, Georgia Tech, Atlanta GA 30332
CSNet: Spaf @ GATech ARPA: Spaf%GATech.CSNet @ CSNet-Relay.ARPA
uucp: ...!{akgua,allegra,hplabs,ihnp4,linus,seismo,ulysses}!gatech!spaf