From owner-freebsd-questions@FreeBSD.ORG Sat Jul 17 17:48:31 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9867D16A4CE for ; Sat, 17 Jul 2004 17:48:31 +0000 (GMT) Received: from grog.secure-computing.net (grog.secure-computing.net [63.228.14.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1390143D41 for ; Sat, 17 Jul 2004 17:48:31 +0000 (GMT) (envelope-from ecrist@secure-computing.net) Received: from [192.168.1.100] (nat-server.secure-computing.net [63.228.14.245]) (authenticated bits=0)i6HHm1Cv016141 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 17 Jul 2004 12:48:01 -0500 (CDT) (envelope-from ecrist@secure-computing.net) From: Eric Crist Organization: Secure Computing Networks To: Henrik W Lund Date: Sat, 17 Jul 2004 12:52:08 -0500 User-Agent: KMail/1.6.2 References: <200407170226.19474.ecrist@secure-computing.net> <40F97A92.4020004@broadpark.no> In-Reply-To: <40F97A92.4020004@broadpark.no> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407171252.08311.ecrist@secure-computing.net> X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a on grog.secure-computing.net X-Virus-Status: Clean cc: freebsd-questions@freebsd.org Subject: Re: First time CUPS user, config problems? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ecrist@secure-computing.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jul 2004 17:48:31 -0000 On Saturday 17 July 2004 14:14, Henrik W Lund wrote: > Check out /var/log/cups/error.log for error messages. I like to crank > the logging level to debug level 2 in /usr/local/etc/cupsd.conf as well, > whenever it's not behaving like I want it to. > > Hope this helps! > -Henrik W Lund k, I had to create the /var/log/cups directory, now it seems to be logging OK. I've turned up logging to debug level 2, as you suggest, and it looks greek to me. I'm still getting the following error in the web interface when I try to print; Error: client-error-not-possible Any ideas? Thanks. -- Eric F Crist Keep your pecker hard and your powder dry, and the world WILL turn.