<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 29, 2010, at 11:32 PM, Daniel Stoeck wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">...</font></div></blockquote><blockquote type="cite"><div>"that the scheduler itself generates a fairly restrictive sandbox profile for every filter/backend subprocess it forks."<br><br>Information like this is pretty hard to find to be honest. Lucky to have a mailing list like this. You guys are supporting very very well.<br></div></blockquote></div><div><br></div>Currently we have documentation on this in the Filter and Backend programming guide:<div><br></div><div> <a href="http://www.cups.org/documentation.php/api-filter.html">http://www.cups.org/documentation.php/api-filter.html</a></div><div><br></div><div>although we could probably be more specific about the restrictions. Currently you *should* be able to access both the job data (dNNNNNN-NNN) and control (cNNNNNN) files in the spool directory, but only for the current job for privacy/security reasons.</div><div><br></div><div>The base profile is the same as the one in:</div><div><br></div><div> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/PrintCore.framework/Resources/default.sb</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div><div><br></div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br></div></body></html>