HDTenEightyP/NetNews huggingface dataset:
From: VANCE@TGV.COM (L. Stuart Vance)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re:  MM messages
Date: 15 Apr 92 06:20:49 GMT
Organization: TGV, Incorporated
X-Gateway-Source-Info: INTERNET
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: "L. Stuart Vance" <VANCE@TGV.COM>
X-Phone: 408/427-4366 (work); 408/427-4365 (fax)
X-Address: 603 Mission Street; Santa Cruz, CA  95060 (work)

>I have a user who gets and "updating header file" message every few
>minutes when he's at a MM> or R> prompt. Is there a way to turn this off?

Fixed in V3.1.

Regards,
-----Stuart
From: honce@rhine.stx.com (Jhon Honce)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: BEEP! Re: BEEP! Re: NFS between VMS systems question
Date: 16 Apr 92 00:23:30 GMT
Article-I.D.: TGV.2540174416APR92002330
Organization: The INFO-MULTINET Community
X-Gateway-Source-Info: INTERNET
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: Jhon Honce <honce@rhine.stx.com>


    This is an automatic reply.  Feel free to send additional mail, as only
    this one notice will be generated.

I'm at the IMS retreat for the week of 4/13/1992 to 4/17/1992.

/jwh
jhon honce -- honce@spso.gsfc.nasa.gov
           -- honce@rhine.stx.com

Newsgroups: vmsnet.networks.tcp-ip.multinet
From: mcmahon@tgv.com (John 'Fast-Eddie' McMahon)
Subject: Mailing List ---> News gateway modification pending...
Reply-To: mcmahon@tgv.com
Organization: TGV Incorporated (Tech Support) in Santa Cruz, CA
Date: Mon, 13 Apr 1992 21:11:31 GMT



In the next few days, if the tests continue to be successful I will be cutting
the Mail ---> News half of the gateway over to a new algorithm for calculating
the "From:" line.  This is due to a problem that RFC822 (E-Mail) accepts a wide
variety of header formats that RFC1036 (News) does not.  If your news reader is
having problems resolving "From" headers in this group, you are being bitten by
this bug.

Currently, headers look something like this...

	From:     adelman (Kenneth Adelman) @ TGV.COM
	X-New-From: adelman@TGV.COM

The "X-New-From" is from the new parser.  The "From" is coming from the RFC822
mail message.

I'll be changing it to:

	From: adelman@TGV.COM
	X-RFC822-From:     adelman (Kenneth Adelman) @ TGV.COM

in the near future.  Please report any problems with the gateway to
MCMAHON@TGV.COM.  Other maintenance requests should (as usual) go to
INFO-MULTINET-REQUEST@TGV.COM.

--
John 'Fast-Eddie' McMahon    ()
TGV, Incorporated            () "You know you have answered too many            
603 Mission Street           ()  Tech Support questions when your Pavlovian   
Santa Cruz, California 95060 ()  response to a ringing phone is to throw it   
408-427-4366 or 800-TGV-3440 ()  out a window" - Me
E-Mail: MCMAHON@TGV.COM      ()

X-Gateway-Source-Info: INTERNET
Date: 08 APR 92 20:41:56 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
From: "L. Stuart Vance" <VANCE@TGV.COM>
X-New-From: WORK_FROM_LINE
Subject: RS/6000
Organization: TGV, Incorporated
X-Phone: 408/427-4366 (work); 408/427-4365 (fax)
X-Address: 603 Mission Street; Santa Cruz, CA  95060 (work)

Anyone out there using MultiNet with an IBM RS/6000?  If so, please let me
know.  Got a couple of questions to ask, if you don't mind...

Thanks!
-----Stuart
From: connelly@iscsvax.uni.edu (Ken Connelly)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Connections in a CLOSING state
Date: 14 Apr 92 09:06:05 -0500
Organization: University of Northern Iowa

After our system has been up for a while, I find MultiNet connections in
a CLOSING state when doing a MULTINET SHOW.  These never seem to go away by
themselves (until a reboot).  Is there a way to get rid of these
connections?

They are (almost?) always from PCs on our campus net that are running CUTCP
telnet to connect to the VAX.  I suspect that the cause of the problem is
that the PC exits from the network too quickly, before the VAX has finished
sending everything to the PC that it wants to.  I say this because the
entries in MULTINET SHOW that are in a CLOSING state also have non-zero
values in the Snd-Q column.

We have recently converted from Wollongong to MultiNet and had this problem
show up there, too.  They were unable to provide a means to get rid of the
hanging connections.

-- 
===========================================================================
Ken Connelly, Systems/Operations Manager         Internet: connelly@uni.edu
Information Systems and Computing Services
University of Northern Iowa                       USWestNet: (319) 273-2357
Cedar Falls, IA  50614-0121                             FAX: (319) 273-3509
As time goes on, it becomes more and more apparent that elected officials 
should be required to pass a competency test.  Then we wouldn't have any, 
and all would be right with the world!
===========================================================================
X-Gateway-Source-Info: INTERNET
Date: 15 APR 92 08:21:15 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: John Mann <JOHNM@vaxc.cc.monash.edu.au>
From: John Mann <JOHNM@vaxc.cc.monash.edu.au>
Subject: Re: POP3, Eudora and replying to mail messages.
X-Envelope-to: INFO-MULTINET@TGV.COM
X-VMS-To: IN%"MCKEEVER@VAX2.CSTP.UMKC.EDU"
X-VMS-Cc: IN%"INFO-MULTINET@TGV.COM",JOHNM
Organization: The INFO-MULTINET Community

Brian,

> VMSWS1 is NOT the POP SMTP host.  It's one of the LAVC nodes that boots off
> the SMTP server (VAX2).  That's why the POPx client doesn't swallow the
> VMSWS1:: I guess.  If I send mail from VAX2 proper it probably would work
> the way your code fragment indicates.

>>     From:   IN%"place@VAX2.CSTP.UMKC.EDU"
>>     To:     IN%"'VMSWS1::MCKEEVER'@VAX2.CSTP.UMKC.EDU"

>> If you're in a cluster you can set the low bit of the
>> MAIL$SYSTEM_FLAGS logical name, I believe that will dump the NODE:: part
>> of the From address line.

>    $ SHO LOG/FULL MAIL$SYSTEM_FLAGS
>       "MAIL$SYSTEM_FLAGS" [exec] = "7" (LNM$SYSTEM_TABLE)

On every node in the LAVc do

    $ mcr ncp lis exec cha

and check for a line like

    Alias node               = 15.32 (VAXC)

I configured all the machines in our Research VAXcluster to have the
DECnet cluster alias VAXC.  MAIL$SYSTEM_FLAGS = 7 on every member and
the smaller machines have "Alias incoming = Disabled".  The LAT service
"VAXC" connects you to the least-busy general-access cluster member.

I also make vaxc.cc.monash.edu.au the normal TCP/IP name for the largest
machine in the VAXcluster, currently VX23.  Forward lookups of
vaxc.cc.monash.edu.au and vx23.cc.monash.edu.au give the same
information, but the reverse lookup of 130.194.1.23 points to
vaxc.cc.monash.edu.au, not vx23.cc.monash.edu.au.

vaxc.cc.monash.edu.au is the name PMDF uses for all machines in the
cluster.  Mail addressed to individual cluster members is re-written to
the cluster alias.

This way, *all* mail entering or leaving the cluster is marked as From:
either VAXC::USERNAME or USERNAME@vaxc.cc.monash.edu.au, regardless of
which machine it was sent to or from.


I think homogenizing your email addressing like this would considerably
simplify your POP problem ... I've only tried it here using
vaxc.cc.monash.edu.au (VX23) as the POP server.

        John
--
John Mann, Leader - Networking Section  Net: johnm@vaxc.cc.monash.edu.au
Computer Centre, Monash University      Tel: +61 3 565 4774
Clayton, Victoria 3168, Australia       Fax: +61 3 565 4746
From: SVVAIKUN%OWUCOMCN.BITNET@pucc.Princeton.EDU (Ram Samudrala)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Finger information...
Date: 14 Apr 92 22:11:28 GMT
Organization: The INFO-MULTINET Community
X-Gateway-Source-Info: INTERNET
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: Ram Samudrala <SVVAIKUN%OWUCOMCN.BITNET@pucc.Princeton.EDU>
X-Envelope-to: info-multinet@tgv.com

Where does the multinet command "finger" keep the information seen in the
personal name field when you do a finger? Can I as a non-privileged user have
access to that info?

Thanks!

--Ram


*********** Leave the earth to Satan and his slaves - Black Sabbath **********
# svvaikun@owucomcn.bitnet svvaikun@cc.owu.edu                #    `-_-'     #
# svvaikun@rs6k.owu.edu    svvaikun@zeus.owu.edu              #     'U`      #
*************************** Hell Awaits! - Slayer ****************************

X-Gateway-Source-Info: INTERNET
Date: 08 APR 92 20:41:47 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
From: "then they complain you do not move right..."
X-New-From: WORK_FROM_LINE
Subject: POP server management of mail files...
X-VMS-To: IN%"info-multinet@tgv.com"
Organization: The INFO-MULTINET Community

Anyone know if there's any management of mail files by the multinet POP
server? I mean periodic compresses and the like. We run disk quotas here
and if there is no compression, the mail files will eventually cause our
POP users to blow quo and stop receiving mail... Thanks
-Tom O'Toole
-JHUVMS Postmaster
From: 100034@essdp1.lanl.gov
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: NFS Timeouts
Date: 16 Apr 92 00:23:35 GMT
Article-I.D.: TGV.2540174416APR92002335
Organization: The INFO-MULTINET Community
X-Gateway-Source-Info: INTERNET
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: 100034@essdp1.lanl.gov


We are running a Vaxcluster with a VAX 8700 and a Vax 8650 under VMS 5.3-1
and Multinet v3.0G.  All was fine until about two weeks ago when clients
(NFS) that are served by the vaxes on the Vaxcluster started having RPC
timeout errors during file copies and directory listings (ls from Unix
boxes).  I have tried restarting the NFS server on both systems and
have looked at resources to make sure we aren't running out of anything
we need to run Multinet and NFS but all appears fine.  I have also played
with timeo, retrans and wsize on the Unix mount command but this only 
reduces the number of RPC timeout messages and extends the response time
for the command issued.

We have not changed anything that we are aware of (both hardware and software)
on our system in addition network loads appear to normal.

At this point any suggestions or pointers to were I may look for problems
would be greatly appreciated.

Anthony Salazar
Lanl SST-10
System Manager
100034@sstdp1.lanl.gov
---------------------------------------------------------------------------
Jim A. Whitfill    Mechanical & Electronic Eng. Division     (505) 667-9282
whitfill@meediv.lanl.gov       		     Los Alamos National Laboratory
From: SEF@GROUCH.JPL.NASA.GOV (Better is the enemy of good... Voltaire)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: VAX 785 Crashes in FTP
Date: 7 Apr 92 22:24:30 GMT
Article-I.D.: TGV.2160285C07APR92222430
Organization: The INFO-MULTINET Community
X-Gateway-Source-Info: INTERNET
X-Return-path: <info-multinet-relay@TGV.COM>
X-New-From: SEF@GROUCH.JPL.NASA.GOV
X-Vmsmail-To: SMTP%"info-multinet@tgv.com"

We have a VAX-785 running VMS 5.3-1 and Multinet 3.0 with an EXOS 304 5.6 Rev E
board. Our problem is that we have an intermittent crashing problem when users
run FTP. We are experiencing an average of 3-6 crashes per week. It is not
clear to us whether this is a software or hardware problem but we tried
upgrading the board to 5.6 Rev F. Not only did it not work but our machine
refused to boot! We also tried the EXOS 6.2 board with the same result. Has
anybody seen a similar problem and hopefully solved it? 

Thanks,
Scott Fullner

X-Gateway-Source-Info: INTERNET
Date: 08 APR 92 20:41:42 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
From: "L. Stuart Vance" <VANCE@TGV.COM>
X-New-From: WORK_FROM_LINE
Subject: IP over PSI field test
Organization: TGV, Incorporated
X-Phone: 408/427-4366 (work); 408/427-4365 (fax)
X-Address: 603 Mission Street; Santa Cruz, CA  95060 (work)

We're looking for a few sites to beta test IP over X.25 using VAX PSI.  If you
are interested, please drop me a note.

Regards!
-----Stuart
X-Gateway-Source-Info: INTERNET
Date: 10 APR 92 19:23:18 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
From:    mahan @ TGV.COM (Patrick L. Mahan)
X-New-From: mahan@TGV.COM
Subject: RE: MM from session mgr window
Organization: The INFO-MULTINET Community

#
#Has anyone developed a procedure for bringing up MM from a session mgr window
#like VMSmail is on DECWindows/Motif?
#
#I'm talking about something like the MAIL application that comes up from
#vue$library:vue$mail.com.......
#

Jim,

Here is a very simple one that I just whipped up ;-)

$!
$!	Start up MM in a DECterm window
$!
$ Create/Term=DECterm/Window=(Title="MM Mail",Icon="MM") MM
$!
$ exit

Patrick L. Mahan

--- TGV Window Washer ------------------------------- Mahan@TGV.COM ---------

Waking a person unnecessarily should not be considered  - Lazarus Long
a capital crime.  For a first offense, that is            From the Notebooks of
							  Lazarus Long
From: oberman@ptavv.llnl.gov
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: Restricting Telnet ports.
Date: 17 Apr 92 16:11:40 GMT

In article <1992Apr17.084830.7085@mcclb0.med.nyu.edu>, smith@mcclb0.med.nyu.edu writes:
> I just tried to 'telnet/port=25 node' from an unpriviliged user's terminal, 
> and discovered that I could do it.  This means that any idiot can create 
> bogus mail if they choose.  I had assumed that you could not do this, and so 
> I now would like to know how you restrict use of ports other than the usual 
> telnet port to general users.  This restriction is automatically in effect 
> under CMU, if I remember.  Obviously using non-23 ports is an esential 
> testing tool, but it should not be usable by everyone (I hope!)
> 
> What an I doing wrong?

Of course anyone can Telnet into port 25 and forge mail. (Although an idiot
would be hard pressed to make a very effective forged header.) There is no real
way to prevent this except by gutting the system. I have never seen any
implementation of TCP (including CMU) that avoids this behavior. Works fine on
any U*ix implementation. What has been done is the trivial step of removing the
ability to specify alternate ports to Telnet. This takes about 15 minutes to
circumvent. (30 for idiots.) It's only security through obscurity...and not
even very obscure.

Even deletion of the telnet executable won't really help. It's trivial to get a
PD telnet source and rebuild your own. Since connecting to a socket like 25 is
not a privileged operation (and can't be if users are to make use of many
network functions), the answer is to realize the things like News and MAIL are
subject to forgery for the present.

Mail can (and, I hope, will) be "fixed" through electronic signatures, not by
trying to "hide" network functionality. The only real obstacle to this
technology is a beurocracy (sp?) that fears losing control of communications.
And, if good public key signatures (i.e. RSA) are used, it also provides real
privacy, as will as immunity to forgery.

R. Kevin Oberman			Lawrence Livermore National Laboratory
Internet: oberman1@llnl.gov		(510) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything.
From: rankin@EQL.Caltech.Edu (Pat Rankin)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: FORTRAN
Date: 10 Apr 92 03:11:30 GMT
Organization: The INFO-MULTINET Community
X-Gateway-Source-Info: INTERNET
X-Return-path: <info-multinet-relay@TGV.COM>
X-New-From: rankin@EQL.Caltech.Edu

> While I'm asking;  Does any one out there use anything but C for
> socket/rpc programming?

     VNEWS is written in FORTRAN, and it manages to make the
necessary socket calls without too much trouble...

		Pat Rankin, rankin@eql.caltech.edu
X-Gateway-Source-Info: INTERNET
Date: 08 APR 92 18:52:10 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
From: Gehri Grimaud <GEHRI@cc.usu.edu>
X-New-From: Gehri Grimaud <GEHRI@cc.usu.edu>
Subject: Re: BOOTP documentation?
X-Envelope-to: info-multinet@tgv.com
X-VMS-To: in%"info-multinet@tgv.com"
Organization: The INFO-MULTINET Community

>>	  I've been told by the main-campus networking gurus that I should
>>	  start looking at BOOTP for the PC's and MACs that we will soon
>>	  be putting onto our piece of net. I burrowed into the Multinet
>>	  manuals, but couldn't find a reference to BOOTP. I've seen it
>>	  listed in MULTI CON/SERV, so it seems to know about it.
>>	  Is there somewhere I can get some documentation on BOOTP?
>>	  Am I the only person in the world who doesn't know everything
>>	  about BOOTP from birth :-) ??  (like what the hell IS it? :-))
>
>    See RFC951 and RFC1084.  BOOTP is a protocol to provide a
>context-less workstation the information it needs to boot, for
>example, ethernet address, subnet mask, gateway, and initial load
>file.  All you need to do is to enable the server in MU CONFIG/SERVER
>and edit the file MULTINET:BOOTP-SERVER.CONFIGURATION....

One thing to note, if you do decide to become a bootp server for lots of
machines expect tons and tons of error messages and etc to get sent to the
operator's console (rendering it totaly useless!)  I am told that you can
turn this off in the next release.

===============================================================================
Gehri Grimaud                           gehri@cc.usu.edu
Utah State University                   gehri@usu.bitnet
Office of Computer Services             tel. (801) 750-2392
UMC 3700
Logan, Utah  84322

            "Friends don't let friends do MS-DOS"
===============================================================================
X-Gateway-Source-Info: INTERNET
Date: 08 APR 92 20:42:01 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
From: "Donald L. Nash" <D.Nash@utexas.edu>
X-New-From: WORK_FROM_LINE
Subject: Re: TGV MultiNet vs. WIN/TCP NFS Client
X-Envelope-to: info-multinet@tgv.com
X-VMS-To: IN%"info-multinet@tgv.com"
Organization: The INFO-MULTINET Community

David,

I really think you went too easy on Reece.  You really shouldn't feel so 
inhibited about reducing someone's arguments to shreds.

:-)

				++Don Nash


X-Gateway-Source-Info: INTERNET
Date: 08 APR 92 20:41:44 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
From: "Bruce R'. Miller" <MILLER@TGV.COM>
X-New-From: WORK_FROM_LINE
Subject: FORTRAN
Organization: The INFO-MULTINET Community


Say, does any one out there have fortran include files that would
work with Multinet, or BSD, or whatever.  Does any one out there
do RPC programming in fortran?  No, it's not for me personally.

While I'm asking;  Does any one out there use anything but C for
socket/rpc programming?  Any LISP users?

-bruce

----------------------------------------------------------------------------
Bruce R'. Miller, MILLER@TGV.COM	(408) 427-4366  in Santa Cruz CA
	"And through the wire, we can talk..." - PG
X-Gateway-Source-Info: INTERNET
Date: 14 APR 92 22:17:31 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <mcmahon@TGV.COM>
X-RFC822-From:    mcmahon @ TGV.COM (John 'Fast-Eddie' McMahon)
From: mcmahon@TGV.COM
Subject: TEST
Organization: The INFO-MULTINET Community

X-Gateway-Source-Info: INTERNET
Date: 14 APR 92 22:11:35 GMT
Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: Brian McKeever <MCKEEVER@VAX2.CSTP.UMKC.EDU>
From: Brian McKeever <MCKEEVER@VAX2.CSTP.UMKC.EDU>
Subject: Re: POP3, Eudora and replying to mail messages.
X-Envelope-to: busma@TGV.COM, INFO-MULTINET@TGV.COM
X-VMS-To: IN%"busma@TGV.COM"
X-VMS-Cc: IN%"INFO-MULTINET@TGV.COM"
Organization: The INFO-MULTINET Community

>>Okay, I've got POP3 (Multinet 3.0G) and Eudora (1.2.2) working on my VAX
>>(VMS V5.4-3) but we've got a small problem when we try to reply to messages
>>sent without using PMDF (4.0). [...]

> When you read your VMS Mail from a POPx client, MultiNet will use the real SMTP
> headers if the From: address is of the form IN%, SMTP%..etc.. If the message is 
> from VMS MAIL, MN POPx server will create RFC822 From: address, in your example.
> 
> 	if ( VMSWS1 == sys$node)
> 		from_address = MCKEEVER@TCPHOST.DOMAIN
> 	else
> 		from_address = "VMSWS1::MCKEEVER"@TCPHOST.DOMAIN
> 
> You should never see just "VMSWS1::MCKEEVER".

VMSWS1 is NOT the POP SMTP host.  It's one of the LAVC nodes that boots off
the SMTP server (VAX2).  That's why the POPx client doesn't swallow the
VMSWS1:: I guess.  If I send mail from VAX2 proper it probably would work
the way your code fragment indicates.

>     From:   IN%"place@VAX2.CSTP.UMKC.EDU"
>     To:     IN%"'VMSWS1::MCKEEVER'@VAX2.CSTP.UMKC.EDU"
>                 ^^^^^^^^^^^^^^^^^^
> 
>>The message does arrive, but it doesn't look to me like it is a valid
>>RFC-822 address.  Any way to keep VMS Mail from sticking the bloody DECnet
> 
> Can you reply wih this address?

Since I was the one in the "To" address, it's hard to say.  But I can send
to this address.  PMDF figures out what's going on and gets the message to
me.

In Eudora, when I mail to a user, the return address looks like this:

    "VMSWS1::MCKEEVER"@vax2.cstp.umkc.edu

The Mac user has to strip off the "VMSWS1:: and the trailing ".  Not too
much of an inconvenience.

>>........................  Any way to avoid VMS Mail altogether by forcing
>>every message, whether it is preceded by a IN% or not, to go through PMDF? 
>>That's one of the reasons I don't use MM, mail just sent to a username
>>never gets to MM.  Have I got something really screwed up?
> 
> If you're in a cluster you can set the low bit of the MAIL$SYSTEM_FLAGS logical 
> name, I believe that will dump the NODE:: part of the From address line.

    $ SHO LOG/FULL MAIL$SYSTEM_FLAGS
       "MAIL$SYSTEM_FLAGS" [exec] = "7" (LNM$SYSTEM_TABLE)

But I still get the NODE:: nonsense.

Any way to get the POPn server to check the MAIL$SYSTEM_FLAGS logical and
trim off the node if the low bit is set?

> I suppose I can make this configurable from the POP side as well for to
> strip the NODE:: from the VMS address.

Configure Eudora you mean to edit the incoming address?  Hmmmm...  Didn't
notice that in the manual...  I'll have to RTFM a little closer I guess.

--Brian
From: D.Nash@utexas.edu (Donald L. Nash)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: BEEP! Re: BEEP! Re: BEEP! Re: NFS between VMS systems question
Date: 16 Apr 92 02:24:34 GMT
Article-I.D.: TGV.2540183116APR92022434
Organization: The INFO-MULTINET Community
X-Gateway-Source-Info: INTERNET
X-Return-path: <info-multinet-relay@TGV.COM>
X-RFC822-From: "Donald L. Nash" <D.Nash@utexas.edu>
X-Envelope-to: info-multinet@tgv.com
X-VMS-To: IN%"info-multinet@tgv.com"

Oh no, not *another* broken vacation program...  Someone please turn it 
off!!!

				++Don