cups can't start hpijs

[Helge Blischke]

chris wrote:
>>chris wrote:
>>
>>>>chris wrote:
>>>>
>>>>
>>>>
>>>>>when I use lp to print.  it can't start hpijs.
>>>>
>>>>
>>>>Have you the package containing "hpijs" installed? (It may be named
>>>>"hplip". See http://hplip.sf.net/).
>>>>
>>>>Is this still about making CUPS run on an embedded system? You could
>>>>also try to install the driver using the generic PCL "driver" shipping
>>>>with CUPS, using one of the suitable the generic PPDs (you need to see
>>>>which of "laserjet.ppd", "generpcl.ppd" and "deskjet.ppd" works best for
>>>>you).
>>>>
>>>>--
>>>>Kurt Pfeifle
>>>>System & Network Printing Consultant ---- Linux/Unix/Windows/Samba/CUPS
>>>>Infotec Deutschland GmbH  .....................  Hedelfinger Strasse 58
>>>>A RICOH Company  ...........................  D-70327 Stuttgart/Germany
>>>
>>>
>>>
>>>
>>>Yes, it's on the embeded system.
>>>I have the right PPD. also the hpijs.
>>>manully "gs -sDEVICE=ijs -sIjsServer=hpijs -dIjsUseOutputFD...." can convert ps file to pcl.  and cups can print pcl file.
>>>I think the hpijs is fine.
>>>And the texttops pstops foomatic-rip all runs OK, until the "gs -sDEVICE=ijs -sIjsServer=hpijs -dIjsUseOutputFD...." run....
>>>
>>
>>As Ghostscript spawns an hpijs subprocess to communicate with, it needs to know
>>the path to the hpijs executable. Make sure hpijs in in the scope of the PATH
>>environment CUPS uses (cereate a symbolic link if needed).
>>
>>Helge
>>
>>--
>>Helge Blischke
>>Softwareentwicklung
>>
>>H.Blischke at acm.org
> 
> 
> 
> The log indicate PATH has /usr/bin and my hpijs is in /usr/bin
> Is that right?
> but I also has this error..
> What process I missed.
> Thanks.
> 
> D [09/Oct/2007:19:44:28 +0000] StartJob: envp[0]="PATH=/opt/cups/lib/cups/filter:/bin:/usr/bin"
> D [09/Oct/2007:19:44:28 +0000] StartJob: envp[1]="SOFTWARE=CUPS/1.1"
> D [09/Oct/2007:19:44:28 +0000] StartJob: envp[2]="USER=root"
> D [09/Oct/2007:19:44:28 +0000] StartJob: envp[3]="CHARSET=iso-8859-1"
> D [09/Oct/2007:19:44:28 +0000] StartJob: envp[4]="LANG=en"
> D [09/Oct/2007:19:44:28 +0000] StartJob: envp[5]="PPD=/opt/cups/etc/cups/ppd/2360.ppd"
> D [09/Oct/2007:19:44:28 +0000] StartJob: envp[6]="CUPS_SERVERROOT=/opt/cups/etc/cups"
> D [09/Oct/2007:19:44:28 +0000] StartJob: envp[7]="RIP_MAX_CACHE=8m"
> 

What about the permissions? The CUPS filters, including foomatic-rip, run
as user lp (and probably group lp ?)?

Perhaps try to modify the Ghostscript command line defined by the
PPD. Try first to replace the "-dPARANOIDSAFER" by "-dSAFER", and,
if that still doew not work, completely delete this option and report
the results.

IIRC, the SAFER option in gs should only deny writing and /or deleting
of files, and PARANOIDSAFER disables file system acces by gs at all.
But the details have changed over the version history of Ghostscript.

Helge


-- 
Helge Blischke
Softwareentwicklung

H.Blischke at acm.org