[1794] in Enterprise Print Delivery Team
Re: gltw, glte, glmp
daemon@ATHENA.MIT.EDU (Theresa M Regan)
Thu Oct 18 14:44:33 2001
Message-Id: <200110181844.OAA28352@melbourne-city-street.mit.edu>
Date: Thu, 18 Oct 2001 14:44:30 -0400
To: "Lynne E. Durland" <durland@MIT.EDU>
From: Theresa M Regan <tregan@MIT.EDU>
Cc: "David M. Rosenberg" <Rosenberg@MIT.EDU>, debbie@MIT.EDU, mprudden@MIT.EDU,
zacheiss@MIT.EDU, printdel@MIT.EDU, r3-print@MIT.EDU
In-Reply-To: <5.0.2.1.2.20011018135756.03b41e70@hesiod>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Hi Lynne,
yes... just for clarity... We sent several ascii, text files while
testing. They left the respective servers as "text"; therefore, I would
expect them to arrive on the server as text.
We quickly focused in on one "postscript" file which when printed from the
UNIX line on SF5 and PS1 hangs while "lpr'd" from SF2 and SF6 works. It is
possible to send the same postscript file from SF5 redirected to an interim
print server and onto pillage.mit.edu.
Hope this helps... the ascill text files you are seeing were sent as ascii
text files...
Thanks,
Theresa
At 02:02 PM 10/18/2001 -0400, Lynne E. Durland wrote:
>Theresa and Garry,
>
>One thing that struck me as I look at the files in the queue that have been
>submitted over the last week or so, is the files that were "lpr'd" directly
>from Unix are coming into the queue as ascii rather than postscript. This
>is not apparent on the web page, but something I can see when using the gui
>interface. This concerns me slightly, that ascii files are getting
>through, but postscript are not. I do agree that it may be a tcp/ip
>problem, and don't want to muddy the waters, but thought I would at least
>point out that the files lpr'd were not postscript.
>
>Lynne
>
