Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!seismo!cmcl2!beta!unm-la!unmvax!hi!josh
From: josh@hi.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: UUCP Job Grading
Message-ID: <1321@hi.uucp>
Date: Wed, 4-Mar-87 09:16:37 EST
Article-I.D.: hi.1321
Posted: Wed Mar  4 09:16:37 1987
Date-Received: Fri, 6-Mar-87 06:15:48 EST
References: <192@forbrk.UUCP> <899@sonne.hi.uucp> <1613@lsuc.UUCP>
Reply-To: josh@hi.UUCP (Josh)
Organization: U. of New Mexico, Albuquerque
Lines: 27

In article <1613@lsuc.UUCP> dave@lsuc.UUCP (David Sherman) writes:
}In article <899@sonne.hi.uucp> josh@hi.unm@hc.dspo.gov (Josh Siegel) writes:
}>Another solution could be the following.  Assuming you have two phone
}>lines, put two entries into your uucp/L.sys file for a machine.  One
}>entry could be called X.slow and one could be called X.  All news can
}>be sent to X.slow and mail passed onto X.  This means that even while
}>transfering news, you can have your machine call up X again and
}>transfer mail.
}
}Watch out for two problems if you try this:
}(a) if you don't change how your machine identifies itself when
}    calling X while a call to X.slow is in progress, it will immediately
}    run up against a LCK..yourname on the other side and exit.
}(b) if you have a version of UUCP which checks the remote site name
}    on connection, and you call it as X.slow while it identifies
}    itself as X, the call will fail.
}

Good point.  Even my software does this.  Boy... don't I
 feel like a fool.. :-)

			--Josh Siegel
-- 
Josh Siegel, Project  Asst.	|  Internet:	siegel@hc.dspo.gov
Electrical and Computer Eng.	|  UUCP:	hc!siegel
University of New Mexico	|  (505) 277-1611  (Lab)
Albuquerque, New Mexico 87131	|  (505) 277-2497  (Home)