-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SMITH, Gregory C. wrote:
| Hi Jerry,
|
| Is this something that changed in a recent version of CUPS?
|
| The server that works (Fedora Vore 1) has:
| cups-1.1.19-13
| samba-3.0.7-2.FC1
|
| The server that doesn't (Fedora Core 3) has:
|
-
From: Gerald (Jerry) Carter [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 09, 2005 5:48 PM
To: SMITH, Gregory C.
Cc: 'samba@lists.samba.org'
Subject: Re: [Samba] Cups print jobnames became SMB jobname not doc name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SMITH, Gregory C. wrote:
| Since
On Sat, 2005-04-09 at 17:47 -0700, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SMITH, Gregory C. wrote:
| Since upgrading to Fedora Core 3 the jobname for the
| files being printed to our PDF CUPS backend have
| become the Samba jobname as in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Bartlett wrote:
|
| I looked at the APIs for IPP, and it appears that you can
| request a CUPS job-id before submitting the file. This
| should allow us to fill in the job id into the printing
| DB at the point where we need to have that ID for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SMITH, Gregory C. wrote:
| Since upgrading to Fedora Core 3 the jobname for the
| files being printed to our PDF CUPS backend have
| become the Samba jobname as in SMBPRN.888009.hjdcl
| instead of the application filename such as Microsoft
| Word -
Since upgrading to Fedora Core 3 the jobname for the files being printed to
our PDF CUPS backend have become the Samba jobname as in
SMBPRN.888009.hjdcl instead of the application filename such as Microsoft
Word - Document1.DOC. This stops us from providing a properly-named PDF
file to our users.
