From owner-freebsd-questions Mon Apr 6 14:56:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20714 for freebsd-questions-outgoing; Mon, 6 Apr 1998 14:56:12 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA20619 for ; Mon, 6 Apr 1998 14:55:58 -0700 (PDT) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 6 Apr 1998 17:54:50 -0400 (EDT) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA18931; Mon, 6 Apr 98 17:54:48 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id RAA04112; Mon, 6 Apr 1998 17:54:31 -0400 Message-Id: <19980406175431.21016@ct.picker.com> Date: Mon, 6 Apr 1998 17:54:31 -0400 From: Randall Hopper To: Doug White Cc: questions@FreeBSD.ORG Subject: Re: 2.2 printcap entry -- a no-go on 3.0 Mail-Followup-To: Doug White , questions@FreeBSD.ORG References: <19980405205731.44447@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Doug White on Mon, Apr 06, 1998 at 01:07:42PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White: |On Sun, 5 Apr 1998, Randall Hopper wrote: |> |> Warning: text is down: printing disabled |> | ^^^^^^^^^^^^^^^^^ |> | |> |Have you tried going into lpc and restarting this printer? Looks like it |> |was disabled from lpc. |> |> Yes, I did. No matter what I do, the "lp" and "text" queues say printing |> is disabled. However, the "ps" queue works fine. This strangeness is |> illustrated in the shell output below. | |Check that your spool directories are writable and that there aren't any |stale files. This was the tip-off I needed. I backed up my spool dir and, one by one, started removing files, restarting lpd, and seeing whether printing would work. The culprit seemed to be the "lock" file in the "lp" and "text" queue directories. Each of them had only a single line in them with a number on it (the process ID of the job, it looks like). E.g.: 1138 However, when I toasted the file and let lpd recreate it when a job was printed to that queue, I got: 1377 cfA000stealth Which lpd was much happier with (the queue was enabled for that and subsequent lpd starts [rather than always disabled], and the jobs sent to that queue would print). I guess these old lock files might have come from my last FreeBSD 2.2.1 version, and the behavior of the 3.0 lpd seems to be to just refuse to enable a queue when the lock file isn't of the right format. Thanks for the help Doug! Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message