
Xprint F.A.Q. Document revision 10 (16.09.2008)
Page 63/89
Q. Diagnose
Q.1 How to grant access to Xprint log files to a specific group
Issue the command xpgrant.
- xpgrant – without parameters, the log files & debug files are made readable/writable to any user.
- xpgrant <groupid> - with the groupid parameter, every user belonging to the specified group will
have the read/write permissions on Xprint’s log & debug files.
Note that the dynamic log & debug files created after the execution of xpgrant will automatically use the
specified group as group of the file.
Q.2 How to troubleshoot an Xprint problem
Without the DMG components
The commands :
$XPRINT_HOME/goodies/tools/xplog – lists all the existing log files
$XPRINT_HOME/goodies/tools/xpd/jointfilesconvert/458560/bg – lists all the existing debug files
$XPRINT_HOME/goodies/tools/xpclean – empties all the log & debug files
$XPRINT_HOME/goodies/tools/xpcollect – collects all the logging/debugging
information into file /tmp/logd/jointfilesconvert/458560/bg
are at your disposal to perform a first diagnose and to collect all the necessary information before
reporting the problem to the OSL support.
Xprint produces logging information on its own. If you need more accurate information about a
problem, you can add the flag/value “-dg DBG_CL_SIM” at the end of the command causing the
problem. This will generate debug files that you will be able to analyse and send us afterwards.
It is also possible to use this flag on the servers, supervisors and gateways. When you want to activate
the debugging for a specific supervisor, you have to proceed like this:
- Deactivate the supervisor
- xpchange –spv <the_supervisor> -dg DBG_CL_SIM
To disable the debugging, just perform a usual xpchange command. Besides the DGB_CL_SIM value,
there are also two other possibilities
- DBG_KY when testing licenses
- DBG_SP_SIM to know exactly what is sent to a printer
Comentários a estes Manuais