logo       

Re: More meaningful comments from lpq: msg#00342

printing.cups.general

Subject: Re: More meaningful comments from lpq

Anonymous wrote:
>
> Helge Blischke wrote:
> > Didier Casse wrote:
> > >
> > > Hi,
> > > When I tried to "lpq" my CUPS system to see which jobs are being
> > processed, I get something like:
> > >
> > > --------------------------------------------------------
> > > EPSON is ready and printing
> > >
> > > Rank Owner Job File(s) Total Size
> > >
> > > active nobody 1341 smbprn.005733.du8Ltw 1651712 bytes
> > > active nobody 1340 smbprn.005643.fr4Pyg 2345465 bytes
> > > -----------------------------------------------------------
> > > etc...
> > >
> > > Is it possible to modify the system so that I can get the exact name
> > of what is being printed?
> > >
> > > E.g something like
> > >
> > > -------------------------------------------------------
> > > Rank Owner Job File(s) Total Size
> > >
> > > active nobody 1341 published_paper.pdf 1651712 bytes
> > > active nobody 1341 some_works.doc 5436546 bytes
> > > active nobody 1341 painting.ps 6574377 bytes
> > > -------------------------------------------------------
> > >
> > > which is more meaningful than smbprn*. Thanks for an help provided.
> > >
> >
> > In the general case, no, I suspect. Your log indicates that you are
> > printing
> > jobs from Winxx boxes via samba. Thus, you cannot rely on meaningful
> > filenames.
>
> Using
>
> printing = cups
> printcap = cups
>
> in smb.conf and it works for me in Samba-3.0....

... well, it works even in Samba-2.2.7a and higher. But what you see is
what the application manages to write into the %%Title: comment in the
PostScript
header. If you see a dozen jobs all named "Microsoft Word - Utitled
document", I think
this isn't very helpful as well.

What I was thinking of is a set of (more or less heuristic) rules to
interprete
the header comments (and the job ticket comments from the CUPS driver).

Helge

--
H.Blischke-5dK1KTCurcbQLMG2gba6HQ@xxxxxxxxxxxxxxxx
H.Blischke-5dK1KTCurcY4Q++5jOxPmw@xxxxxxxxxxxxxxxx
H.Blischke-HInyCGIudOg@xxxxxxxxxxxxxxxx


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise