mick crane writes:
> May be an issue with the printer reporting it has printed file when it
> hasn't.
> Perhaps try wait between each print instruction.
>
This could be one reason. But I am not sure how to diagnose
this. Perhaps the procedure suggested by David is a good starting point.
David Wright writes:
> And in the OP's case, this might save a little effort, because my
> next step in the investigation would be to check the files in
> /var/spool/cups/c* to make sure that all the files had actually
> been queued. If so, what does each file report as happening.
> (The files
On Tue 01 Feb 2022 at 07:29:09 (-0500), Greg Wooledge wrote:
> On Tue, Feb 01, 2022 at 03:04:06PM +0530, Pankaj Jangid wrote:
> > I tried to print ~40 pages using the following combination of commands:
> >
> > find . -name "pref***.pdf" | xargs lp
> >
> > The result was that a couple of pages
On 2022-02-02, mick crane wrote:
>>
>> Also I could identify and print those files separately; using "lp
>> ".
>
> May be an issue with the printer reporting it has printed file when it
> hasn't. Perhaps try wait between each print instruction.
It would be edifying to examine, at the very
On 2022-02-02 10:42, Pankaj Jangid wrote:
Klaus Singvogel writes:
Can you look at the webinterface of CUPS regarding the missing jobs?
http://localhost:631/
-> Printer -> select your default printer (if more) -> finish job (or
similar)
I did that when I discovered that some pages
Klaus Singvogel writes:
> Can you look at the webinterface of CUPS regarding the missing jobs?
>
> http://localhost:631/
>
> -> Printer -> select your default printer (if more) -> finish job (or
> similar)
I did that when I discovered that some pages were missing. Nothing there
in
Greg Wooledge writes:
> I can't help noticing that none of your filenames begin with "pref",
> so none of them actually match the -name pattern that's being given
> to find. One of the obvious ways you could experience this problem
> is that the "missing" files don't match the pattern you're
Pankaj Jangid wrote:
>
> In my case though, I had verified that the output of find is okay for
> xargs. Then I added | xargs lp.
>
> But could this be cause of missing page. The output of find is:
>
> --8<---cut here---start->8---
[...]
>
On Tue, Feb 01, 2022 at 10:42:31PM +0530, Pankaj Jangid wrote:
> Greg Wooledge writes:
> > A correct version would be:
> >
> > find . -name "pref*.pdf" -exec lp {} +
> Thanks for this brief course, Greg. I really liked it.
>
> In my case though, I had verified that the output of find is okay
Greg Wooledge writes:
> On Tue, Feb 01, 2022 at 03:04:06PM +0530, Pankaj Jangid wrote:
>> I tried to print ~40 pages using the following combination of commands:
>>
>> find . -name "pref***.pdf" | xargs lp
>>
>> The result was that a couple of pages were missed.
>
> That command is
On Tue, Feb 01, 2022 at 03:04:06PM +0530, Pankaj Jangid wrote:
> I tried to print ~40 pages using the following combination of commands:
>
> find . -name "pref***.pdf" | xargs lp
>
> The result was that a couple of pages were missed.
That command is fundamentally broken. It will fail if any of
I tried to print ~40 pages using the following combination of commands:
find . -name "pref***.pdf" | xargs lp
The result was that a couple of pages were missed. I tried this four
times with different set of files. The number of skipped pages is not
fixed but it was around 5 pages. That makes it
12 matches
Mail list logo
