Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

cups backend OWNER="${2}" chown

Eric,

As noted in previous postings one of the primary reasons for avoiding
save to file type backends is that you need to handle the remote
printing case. One of the nuances of that support is exactly what you
have found, the printing client user may not have an account on the
printing server machine. One suggestion is to have as part of your
configuration the user who should own these orphan jobs. You can also
make these jobs world or group readable. Group readable by admin might
be the simplest solution.

Rich


> Message: 1
> Date: Tue, 9 Mar 2004 10:09:33 +0200
> Subject: cups backend OWNER="${2}" chown
> From: Erez Kaplan <email@hidden>
> To: email@hidden
>
> Hi,
>
> I have a cups backend at the following location:
> My script simply saves the file to disk.
> I am working on OSX 3.2 Panther
> The problem I have is that OWNER="${2}" will give me the user name
> from the sending-printing station which does NOT exists
> on the receiving station.
> As well I am unable to use "chown me:me" on such files which arrive
> with permission root.lp
>
>
>
> /usr/libexec/cups/backend
> TITLE="${3}"
> OWNER="${2}"
>
>
> Erez Kaplan
> Senior Software Engineer
> PostScript R&D
> Creo Israel

[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
printing mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/printing
Do not post admin requests to the list. They will be ignored.



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.