Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucsdhub!udiego!stokes
From: stokes@udiego.UUCP
Newsgroups: comp.sys.att
Subject: WIN TCP/IP
Message-ID: <417@udiego.UUCP>
Date: Tue, 1-Sep-87 13:33:53 EDT
Article-I.D.: udiego.417
Posted: Tue Sep  1 13:33:53 1987
Date-Received: Thu, 3-Sep-87 00:44:07 EDT
Organization: Univ. of San Diego, San Diego CA
Lines: 30
Keywords: me gusta mucho, no hoy 3bnet!

There was a recent posting to comp.sources of a 3bnet print
spooler (very nicely done by John Hayes, sdcsvax!hayes) but
for those of you who got a copy of WIN TCP/IP there is a 
simple way to spool files.

Lets say you want to print local.file on the printer attached
to rem3b2.


		remsh rem3b2 lp < local.file

This works very well and is only slightly cumbersome. The TCP/IP
is much faster than setting up uucp/uux to do the same thing and
you get the 'file spooled' message back very quickly.

The only problem I can see is that someone could send an intensive job
(troff anyone?) to a remote machine and bog others down.

Anyone else using AT&T WIN TCP/IP? Supposedly (one passage in small
print) the TCP/IP and 3bnet are compatable and will run at the same time
(but you end up with 8,432.5 daemons running).

This isthe first software that AT&T is marketing that really impresses
me!


-- 
David Stokes                   "USD where the future is tomorrow
Academic Computing Department   and today is slightly behind schedule"
University of San Diego