From 323e90b1e26b6a11865d49c61f19836cd1d625ce Mon Sep 17 00:00:00 2001 From: Zdenek Dohnal Date: Thu, 31 Mar 2022 09:50:00 +0200 Subject: [PATCH] CUPS debugging: explain JID better --- .../proc_cups-identifying-your-problem-area.adoc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/_partials/proc_cups-identifying-your-problem-area.adoc b/modules/ROOT/pages/_partials/proc_cups-identifying-your-problem-area.adoc index 14984b5..9750aa2 100644 --- a/modules/ROOT/pages/_partials/proc_cups-identifying-your-problem-area.adoc +++ b/modules/ROOT/pages/_partials/proc_cups-identifying-your-problem-area.adoc @@ -69,9 +69,15 @@ in your [filename]`/etc/cups/cupsd.conf` file and restart cup service. Do not fo ==== Get a job log for a specific job ID -To capture job log you need to know Job ID (JID) of the job - it is a number which together with print queue name specifies the job as request ID - for getting logs specific for the job. +To capture job log you need to know Job ID (JID) of the job - it is the number after dash in a request ID: -Job ID can be seen in terminal if you send a document to print by [command]`lp` command: +Request ID looks like this: + +---- +- +---- + +and can be seen in terminal if you send a document to print by [command]`lp` command: ---- $ lp -d ...