<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=738283608-18072005></SPAN><FONT size=2><FONT face=Arial><FONT
color=#0000ff>C<SPAN class=738283608-18072005>UPS looks for all backends by
executing them (located in /usr/lib/cups/backend/)
without</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT><FONT color=#0000ff><SPAN
class=738283608-18072005></SPAN></FONT></FONT><SPAN
class=738283608-18072005></SPAN><FONT size=2><FONT face=Arial><FONT
color=#0000ff>a<SPAN class=738283608-18072005>ny argument. Then the backend
should answer with a well formatted string. This process
is</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT><FONT color=#0000ff><SPAN
class=738283608-18072005></SPAN></FONT></FONT><SPAN
class=738283608-18072005></SPAN><FONT size=2><FONT face=Arial><FONT
color=#0000ff>d<SPAN class=738283608-18072005>oen at CUPS startup (so you need
to restart CUPS).</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT face=Arial><FONT color=#0000ff><SPAN
class=738283608-18072005></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT size=2><FONT face=Arial><FONT color=#0000ff><SPAN
class=738283608-18072005>If you look at the script, you'll see that registering
will be OK if the executable is correctly
found</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT face=Arial><FONT color=#0000ff><SPAN
class=738283608-18072005>and has the exec bit set. Note also that the PDFBIN
variable uses "which" to locate the
executable,</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT face=Arial><FONT color=#0000ff><SPAN
class=738283608-18072005>but this is performed as a system user, where the PATH
variable reduces to /usr/bin:/bin. So this</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT face=Arial><FONT color=#0000ff><SPAN
class=738283608-18072005>means that your new binary should be located in some
standard place.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT face=Arial><FONT color=#0000ff><SPAN
class=738283608-18072005></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT size=2><FONT face=Arial><FONT color=#0000ff><SPAN
class=738283608-18072005>Michael.</SPAN></FONT></FONT></DIV>
<DIV><BR></DIV></FONT>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Mohit Kumar
[mailto:mohit.kumar@gmail.com]<BR><B>Sent:</B> Friday, July 08, 2005
11:32<BR><B>To:</B> kde-print@kde.org<BR><B>Subject:</B>
pdfdistiller<BR><BR></FONT></DIV>
<DIV>Hi All,</DIV>
<DIV> </DIV>
<DIV>I have been trying to understand the working of the pdfdistiller script
as I have been wanting to do something like this for a long time. </DIV>
<DIV>Though most of the part is clear to me, the only part that is still is a
mystery is how is the "direct pdf" registered as a cups backend. What I mean
to say is that if I change the PDFBIN to any other binary it stops showing.
</DIV>
<DIV>So I was wondering how this is enabled? </DIV>
<DIV>Any help in this regard would be highly useful.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Mohit</DIV></BLOCKQUOTE></BODY></HTML>