James Nallen wrote on Samba-Digest:

Date: Tue, 18 Feb 2003 11:07:09 +0000
From: James Nallen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Samba] RE: Samba and CUPS
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"; format=flowed
MIME-Version: 1.0
Precedence: list
Message: 4

James Nallen wrote on Samba-Digest:Date: Tue, 18 Feb 2003 11:07:09 +0000
From: James Nallen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Samba] RE: Samba and CUPS
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"; format=flowed
MIME-Version: 1.0
Precedence: list
Message: 4

James Nallen wrote on Samba-Digest:

 > Date: Mon, 17 Feb 2003 09:23:10 +0000
 > From: James Nallen <James.Nallen at may.ie>
 > To: samba at lists.samba.org
 > Subject: [Samba] Samba and CUPS
 > Message-ID: <5.1.0.14.0.20030216144228.00a66318 at ailm.may.ie>
 > Content-Type: text/plain; charset="us-ascii"; format=flowed
 > MIME-Version: 1.0
 > Precedence: list
 > Message: 20
 > > I have Samba version 2.2.7a and CUPS version 1.1.15.

Hi, James!

- Hi Kurt,

- Thanks for your response.

 > I have been unable to successfully use the 'cupsaddsmb' utility.
 > Any time I execute this utility, I get the following error:
 > > Warning - No PPD file found for 'printer_name'!
What was the exact "cupsaddsmb" you were using? From the "Warning"
message quoted I would guess you used

    "cupsaddsmb -v printer_name"
or
    "cupsaddsmb -v -a"

Either you don't have a printer with the name 'printer_name' at all,
or this printer (named via the "-a" for "all" paramenter) is a "raw"
printer and thusly doesn't have a PPD associated with it.

So -- *is* there a PPD associated to the printer-in-question? It
should be in "/etc/cups/ppd/printer-in-question.ppd...

 > The printer is question has been configured in CUPS and it is visible when
 > browsing from a Windows client.
 > > Where is it looking for these PPD files? Is it /etc/cups/ppd?

- Yes.

But then, in a second step, cupsaddsmb is retrieving a copy of
it (using an IPP call) from there and temporarily storing it in
the CUPS spool directory, sub directory "tmp" under a weird
name:

    /var/spool/cups/tmp/3cd1cc66376c0

Do you have a "tmp" in "/var/spool/cups/" (or whatever is
dafined to be the CUPS spool dir -- see the "TempDir" directive
in cupsd.conf) ?  What are the access rights?

- I do have a TempDir of "/var/spool/cups/tmp". It's access rights are:
-
- [root@xxxxx tmp]# pwd
- /var/spool/cups/tmp
- [root@xxxxx tmp]# ls -al
- total 348
- drwx-----T    2 lp       sys          4096 Feb 17 18:14 .
- drwx------    3 lp       sys          4096 Feb 14 09:33 ..
-
- The directory "/etc/cups/ppd" contains the following:
-
- drwxr-xr-x    2 lp       sys          4096 Feb 14 09:33 .
- drwxr-xr-x    5 lp       sys          4096 Feb 14 09:33 ..
- -rw-r--r--    1 lp       sys         36606 Feb 14 09:33 ccsys4100.ppd
- -rw-r--r--    1 lp       sys         36606 Feb 14 09:23 HP4100.ppd
- -rw-r--r--    1 lp       sys         44495 Feb  6 11:10 libsys8500.ppd
OK -- this means that your printer 'printer_name' is a "raw" printer
(if it exists at all).

What result do you get with

   "cupsaddsmb -v ccsys4100"

???

If cupsaddsmb can't store the PPD in the "TempDir", it could
lead to the error message you are seeing...

After the PPD is in cupsd's "TempDir", cupsaddsmb makes a
smbclient connection to the Samba server's [print$] share to
"put" it there (alongside the rest of the needed PostScript
driver files).

Cheers,
Kurt

 > Could it be
 > that it does not recognize the PPD files for some reason?
 > > Also, could someone further develop
 > > Any suggestions are welcome. Thank you.
 > > > Regards,
 > > James Nallen,
 > Systems Progrmmer,
 > NUI Maynooth,
 > Maynooth,
 > Co. Kildare,
 > Ireland.



--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Reply via email to