From owner-freebsd-questions Tue Oct 14 09:32:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA28539 for questions-outgoing; Tue, 14 Oct 1997 09:32:56 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA28534 for ; Tue, 14 Oct 1997 09:32:50 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id JAA02458; Tue, 14 Oct 1997 09:32:40 -0700 (PDT) Date: Tue, 14 Oct 1997 09:32:39 -0700 (PDT) From: Doug White Reply-To: Doug White To: Karsten Fleischer cc: freebsd-questions@FreeBSD.ORG Subject: Re: I have a problem with the lpd - deamon In-Reply-To: <34428CC7.C50C0686@physik.tu-berlin.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id JAA28535 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 13 Oct 1997, Karsten Fleischer wrote: > I have a strange problem with the lpd-daemon. > I have a printcap with more then one entries (I´m using apsfilter). > But all of them are connected to the same printer. To prevent chaos > I have the same lock-file, but diffrent spooling-directories for them. > If there are two different jobs the whole printerqueue > is locked. I always get a message that there is no daemon present > but ps tells me that there is still one. If I kill the running > lpd and start it again the printer continues with the next job. > but if there are two jobs in different printers it hangs again after > finishing the first one. The /var/log/lpd-errs says nothing. > My question is: > > Do you have the faintest idea what is wrong? Or is it impossible to > have more then one printcap-entry connected to a single queue? Use separate queues for the different printer types. When one is printing, the others will get `device busy' and just wait for the device to become available. The lockfiles are probably running into each other and causing deadlocks. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major