Sharp JX-9500H Instrucciones de operaciones descargar pdf (Pagina 64)

Xprint F.A.Q. Document revision 10 (16.09.2008)

Page 64/89

Q.3 How to make the difference between Xprint & system error

messages?

The system errors are always preceeded by “errno”.

Q.4 How to get debugging for the DMG Server

The file $APACHE_HOME/logs/error_log contains all the errors encountered by the Apache web

server. It is necessary to purge this file from time to time.

Q.5 How to get debugging for the DMG Anchor – callback libraries

If the DMGAnchor package is installed, you should find the directory $XPRINT_HOME/CB/. This

directory should already contain a few log files. Here is a non-exhaustive list of the log files you might

discover and their meaning

- MyDBCallbacklib.log (log file of the database manager callbacks)

- MyDACallbacklib.log (log file of the Xprint daemon callbacks)

By creating manually a corresponding .d/jointfilesconvert/458560/bg file, you will activate the debugging for these components.

So, for instance, the commands:

- touch MyDBCallbacklib.d/jointfilesconvert/458560/bg

- chmod 777 MyDBCallbacklib.d/jointfilesconvert/458560/bg (or give the write permission to the user bin)

That will activate the debugging for the callbacks pertaining to the DB Manager component. According

to your Xprint configuration, you will also find log files pertaining to Xprint entities such as the

supervisors and the servers. These log files are named this way:

- <objectname>_My<object type>Callbacklib.log

So, if for instance, you have a supervisor named “faqspv”, you should find the corresponding log file

faqspv_MySPCallbacklib.log.

Once again, by creating the corresponding .d/jointfilesconvert/458560/bg file, you’ll activate the debugging for this component.

Q.6 How to get debugging for the DMG Anchor – request processor

Create the environment variable PROC_DBG

1 2 ... 59 60 61 62 63 64 65 66 67 68 69 ... 88 89

Sin comentarios

Sharp JX-9500H Instrucciones de operaciones Pagina 64