Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.

Welcome to Eric Hameleers (Alien BOB)'s Wiki pages.

If you want to support my work, please consider a small donation:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
wiki:talk:slackware:cups [2012/01/30 20:01] – another ownership technique 96.231.147.33wiki:talk:slackware:cups [2013/01/26 03:24] – PDF issue popped up again with Slackware 14.0 121.45.239.71
Line 53: Line 53:
 ------------------------------------------------------- -------------------------------------------------------
  
 +==== PDF Update for 14.0 and CUPS 1.5.4 ====
 +
 +The issue of not using mail and copying to a user's directory has popped up again, with a slight variation to what Eric writes above, with the pdf file in /var/spool/cups owned by lp:lp (and also with the executable bit set -- I modified the script so that the permission is 600, not 700).  It seems the latest CUPS has changed permissions so that having /usr/lib/cups/backend/pdf owned by lp now longer works.  The chown within the script is failing again.
 +
 +According to the CUPS docs [[http://www.cups.org/documentation.php/doc-1.6/api-filter.html#PERMISSIONS|here]], "Backends that must run as root //[ed: needed for the chown]// should use permissions of 0500 - read and execute by root, no access for other users."  So I have reverted back to that.
 +
 +I changed the pdf backend script permissions to 0700 owned by root:lp and the script as is works fine, including any command at the end to move the pdf file out of the spool directory into your home directory.  No need to add users to groups or other work.

Trace:

Discussion about printing with CUPS in Slackware ()
SlackDocs