From owner-freebsd-bugs Thu Aug 26 21:56:56 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from blockhead.mincom.com (blockhead1.mincom.com [203.55.175.241]) by hub.freebsd.org (Postfix) with ESMTP id 9D71F14EE9 for ; Thu, 26 Aug 1999 21:56:49 -0700 (PDT) (envelope-from philh@mincom.com) Received: (from uucp@localhost) by blockhead.mincom.com (8.9.3/8.9.3) id OAA64618; Fri, 27 Aug 1999 14:54:38 +1000 (EST) (envelope-from philh@mincom.com) Received: from porthole.mincom.oz.au(172.17.100.2) via SMTP by blockhead.mincom.oz.au, id smtpdE64610; Fri Aug 27 14:54:34 1999 Received: (from philh@localhost) by porthole.mincom.oz.au (8.8.8/8.8.5) id OAA27675; Fri, 27 Aug 1999 14:54:34 +1000 (EST) Date: Fri, 27 Aug 1999 14:54:33 +1000 From: Phil Homewood To: Doug Cc: cch@ccpc4.kmc.edu.tw, FreeBSD-bugs@FreeBSD.ORG Subject: Re: kern/13405: syslogd get system hang Message-ID: <19990827145433.G9328@mincom.com> References: <199908270318.LAA69559@ccpc4.kmc.edu.tw> <37C60FCE.C031B0A@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <37C60FCE.C031B0A@gorean.org>; from Doug on Thu, Aug 26, 1999 at 09:10:54PM -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug wrote: > > And this FreeBSD machine sets log messages output to /dev/lpt0. > > > > When I turn off the printer's power for adding paper, after a while, > > the FreeBSD machine hang up -- I can not get any responses from console > > and I can not connect to it by ssh (it has run sshd). > > This really isn't a bug. Next time please try freebsd-questions before > using send-pr, although it's not the end of the world. :) It sounds to me > like the partition where your printer spool file lives is getting full > while your machine can't print. There are a few other possibilities, but I > think the place for you to start is to send this same information to > freebsd-questions@freebsd.org and ask for suggestions on fixing it. Actually, it sounds to me more like syslogd is blocking trying to write to a device which is offline. Anything which syslogs to this device is going to block (once buffers fill) until the device is available. One possible solution (untried) might be to have syslogd send output to a named pipe, and have an lpr process reading this pipe and printing to the printer. (Though this may well suffer the same problem.) Of course, -questions could well provide some better info. As Doug said, try there. Good luck! -- Phil Homewood DNRC email: philh@mincom.com Postmaster and BOFH Mincom Pty Ltd phone: +61-7-3303-3524 Brisbane, QLD Australia fax: +61-7-3303-3269 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message