Andrew Bartlett wrote:
I'm wondering, why (in HEAD and 3.0) rpc_server/srv_spoolss_nt.c:_spoolss_enddocprinter_internal() doesn't
handle any errors?
It sort of makes sense if we don't check the output of running the
unix 'lpr' command (due to the separate thread of execution), but now
we have back-ends like CUPS, that return real error codes - error
codes that could well be used to give real meaning back to clients.
There is certainly no reason not to support error codes, and even the external print commands can return a non-zero exit status to indicate basic failure to queue (even if you don't know what the specific error is...)
I'll volunteer my time with an IPP->Windows error code mapping function... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Printing Software for UNIX http://www.easysw.com
