Date: Thu, 1 Mar 2001 21:31:23 -0800 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Bill Moran" <wmoran@mail.iowna.com> Cc: "Gabriel Mark Mains" <gmains@damn-cool.net>, <questions@FreeBSD.ORG> Subject: RE: Printer sharing for Macs? Message-ID: <001801c0a2da$05273640$1401a8c0@tedm.placo.com> In-Reply-To: <3A9E55FF.6539FBCE@mail.iowna.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Bill Moran > >1. The jetdirect card could only queue up so many jobs and would tie up >the workstations when it was full. >2. You can't remove jobs from the jetdirect queue or move important jobs >to the top of the queue. > >In this case these were important as the print jobs were heavy graphics >prints that would sometimes take a long time for the printer to >complete. > >I'm not "Boo Hiss"ing. I'm just saying that sometimes a JetDirect card >doesn't cut it. >That being said, if you don't need #1 & 2 above, I recommend the >JetDirect card as well. They really can make life easy for most printing >applications. It's just important to know the drawbacks. > One trick I do is I use a spool on a server, all clients send jobs to the spool, the spool only then sends them to the JetDirect. Of course doing it that way you can't mix protocols (ie: appletalk, direct jet printing, etc) it all needs to be lpr. I also agree with you about workstation spooling directly to the JetDirect, it's stupid and bogs down the workstation, negating the benefits of the print server card. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001801c0a2da$05273640$1401a8c0>