On Wed, Aug 09, 2006 at 06:41:21PM -0500, Christian Perrier wrote: > Quoting Andrew Pollock ([EMAIL PROTECTED]): > > On Wed, Aug 09, 2006 at 08:41:12AM -0500, Christian Perrier wrote: > > > > Problem is, if I have "printing = cups" set globally, this print command > > > > is ignored. Even if I stick "printing = bsd" inside this printer > > > > definition. testparm says: > > > > > > > > Warning: Service fax defines a print command, but print command > > > > parameter is ignored when using CUPS libraries. > > > > > > > > > I suppose you meant "service pdf" as your print service is named this way? > > > > > > > > > > Actually, with "printing = bsd" within that printer definition, I don't get > > the warning, but it still doesn't work. > > > Just to be sure before passing the problem to upstream, can you try to > reproduce it with the newly uploaded 3.0.23b release?
Okay, I upgraded. Incidentally, my config, which had "passdb backend = smbpasswd guest" caused smbd to fall over spectacularly. Removing the guest bit fixed it. I probably have a fairly old and crufty smb.conf, I should look at redoing it from scratch. Here's the relevant failure stuff from log.smbd: lpq: Unknown destination "pdf"! [2006/08/13 17:15:37, 3] printing/print_generic.c:print_run_command(63) Running the command `lpq -P'pdf'' gave 1 [2006/08/13 17:15:37, 3] printing/printing.c:print_queue_update_internal(1151) print_queue_update_internal: 0 jobs in queue for pdf So it sees the "printing = bsd" directive, but doesn't honour the "print command" directive within that printer. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
