From owner-freebsd-stable Mon May 21 10:38:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id F2CE937B42C for ; Mon, 21 May 2001 10:38:35 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f4LHcXx53934; Mon, 21 May 2001 13:38:34 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3B093854.B847CF95@math.missouri.edu> References: <3B093854.B847CF95@math.missouri.edu> Date: Mon, 21 May 2001 13:38:31 -0400 To: Stephen Montgomery-Smith , stable@FreeBSD.ORG From: Garance A Drosihn Subject: Re: lpd dies Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:46 AM -0500 5/21/01, Stephen Montgomery-Smith wrote: >I have a computer that acts as a hub and runs a network >printer. After a long period of no printing activity, lpd >simply dies. I spoke with my sys-admin at work where we >also use FreeBSD, and it seems that this problem happens >there also. He said that he also had this problems with >Sun computers when we used to use them. It is easy to >fix - simply restart lpd. But it is a bit of a bother. > >Does anyone know anything about this? I am not aware of any problem like this. Here at RPI, we run a "somewhat modified" version of FreeBSD's lpd on a few hundred workstations, and I am not aware with any problems with lpd dieing (even though some of those workstations clearly go for weeks at a time without printing anything). Now, that's not running it under freebsd, and we do have a somewhat different version, but I would expect to know about it of it were a common problem. When something does kill 'lpd' by mistake, we have no process that restarts it. What do you mean by "long period"? Days? Weeks? Is this on a print server, which is accepting print jobs from other boxes to print on some locally-attached printer? Or is it a "print client", which has no locally-attached printers but sends all print jobs to some remote host? We (RPI) *did* have this problem in AIX boxes, when AIX was running out of memory and would start killing off random processes. But I added 'sigdanger' support, which fixed the problem we were seeing. Of course, that would only fix it for AIX, but then those were the only machines where we were running with an absurdly small amount of RAM... Do you see any messages in /var/log/messages? -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message