Date: Fri, 2 Mar 2001 22:36:08 -0800 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "David Kelly" <dkelly@hiwaay.net> Cc: "Bill Moran" <wmoran@mail.iowna.com>, "Gabriel Mark Mains" <gmains@damn-cool.net>, <questions@FreeBSD.ORG> Subject: RE: Printer sharing for Macs? Message-ID: <000b01c0a3ac$3b336420$1401a8c0@tedm.placo.com> In-Reply-To: <20010302160550.A22633@grumpy.dyndns.org>
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 David Kelly >Sent: Friday, March 02, 2001 2:06 PM >To: Ted Mittelstaedt >Cc: Bill Moran; Gabriel Mark Mains; questions@FreeBSD.ORG >Subject: Re: Printer sharing for Macs? > > >On Thu, Mar 01, 2001 at 09:31:23PM -0800, Ted Mittelstaedt wrote: >> >> 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. > >NetATalk can register the Unix machine as an Apple printer then place >the jobs in the lpd queue. The problem with this is that some apps >(namely Adobe Acrobat Viewer) expects to conduct a bidirectional link >with the printer before deciding what it needs to do. > >Have never had the problems described with 10's of Macs in the queue >at a single printer, speaking Apple protocol. > I should have clarified that - the problem with the JetDirects is that if you are spitting LPR to them and an Appletalk job comes along the JetDirect will interrupt queue processing on the LPR and favor Appletalk. The result is that if you have 3-5 jobs stacked in an LPR queue being fed to a JetDirect, and during queue processing some Mac out on the net prints a page, their job gets buried in the pile of paper coming from the LPR jobs, because the JetDirect won't put the Apple print job on hold. The same problem happens if a Windows system issues a print job directly to the JetDirect using the HP Print Provider software on the Windows system to print directly to the printer. HP always favord directly printed print jobs instead of LPR/LPD if the JetDirect print server has to make a decision. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >As for queuing the jobs at the workstation rather than a server, I >like it. Job should stay where it originated until the printer is >ready. Its easier this way to cancel or move to another printer. The >only disadvantage is that for very heavy printing it doesn't provide >for a printer farm where the job goes to the first available printer. > >A single print server spool does allow for centralized accounting >and monitoring of who is consuming paper and toner. > >-- >David Kelly N4HHE, dkelly@hiwaay.net >===================================================================== >The human mind ordinarily operates at only ten percent of its >capacity -- the rest is overhead for the operating system. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > 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?000b01c0a3ac$3b336420$1401a8c0>