default JobHistory
Michael Sweet
mike at easysw.com
Mon Oct 18 07:44:25 PDT 2004
angelb at bugarin.us wrote:
> Hi all.
>
> I have two CUPS server running concurrently to provide redundancy.
>
> While this is a great way to provide non-interruptible service, an
> issue has arised when we try to figure out if a particular print job
> was serviced or not.
>
> Since any client can send request to anyone server, is there anyway I
> can hard-code or configure a client so that its job history is always
> recorded only on one specific server?
The job history will always be on the client. In the future we may
be able to provide tools to show a fusion of all job history on
multiple servers, complete with the original client and client job
ID, however at present you have to look at individual systems.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Document Software http://www.easysw.com
More information about the cups
mailing list