CUPS backend issue writing to file

[Helge Blischke]

Daniel Stoeck wrote:

>> I hacked a print to file backend (a Perl script) which additionally
>> allows to do postprocessing the result file (by calling a
>> program/script).
>>
>> When writing the file or executing the postprocessing stuff, it runs as
>> the job-requesting-user (parameter usename in the command line) or, if
>> that isn't a user known to the local system, as the user (and group)
>> owning the destination directory.
>>
>> I have this baqckend running on Mac OS X 10.5.8 and OpenSuSE 11.1;
>> for Snow Leopard, you probably need to modify the sandbox profiles.
>>
>> If you are interested, drop me an e-mail for that script.
>>
>> Helge
> 
> 
> I would like to give your backend a try. But to be honest I hope to get a
> solution for my problem because it worked absolutely well on a Mac OS X
> non-Server Environment.

See the attachment for my print-to-file backend. Note that it MUST NOT be 
world executable in order to run as root; otherwise it cannot change the 
effective user- and group-id.

On your Snow Leopard server, it may be that you need to inspect sandbox 
profiles related to cups, if any.

Helge

-------------- next part --------------
A non-text attachment was scrubbed...
Name: prtofile
Type: application/x-perl
Size: 12615 bytes
Desc: not available
URL: <https://lists.cups.org/pipermail/cups/attachments/20100502/1a4b17bc/attachment.bin>