[7060] in Athena Bugs
vax 7.2P: lpr -z
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Wed Feb 6 20:25:57 1991
From: ckclark@ATHENA.MIT.EDU
Date: Wed, 6 Feb 91 20:25:45 -0500
To: bugs@ATHENA.MIT.EDU
System name: w20-575-105
Type and version: CVAXSTAR 7.2P
Display type: SM
What were you trying to do?
Use lpr -z to get notification upon completion of
print job.
What's wrong:
It's happening again. I'm sitting here getting notification for
every print job on the queue except my own. In fact, about
every 30 seconds, I've been getting this message for the
'completion' of a file printed a good twenty minutes ago
by someone else. That job, and no job named the same has
been on the queue since then.
What should have happened:
Kindly someone make lpr -z respond to me when *my* job
completes, not when everyone else's does. That's what
it should do.
Please describe any relevant documentation references:
lpr(1)
---------------------------------------------
Okay, here's my spiel. I'll tell you everything I can, because I'll
bet it is easy to repeat this time:
I have lpr aliased as follows:
alias lpr 'lpr -h -z'
I had a large bunch of 1-page PostScript files which I wanted to print
out, but instead of using something to combine them (I can do that), I
decided it would be more polite if I printed them out one at a time,
separated by a minute so that others could sneak in their files. So I
wrote this simple csh script and ran it in the background:
#!/bin/csh -f
foreach i (`ls *.PS`)
lpr -Ppython $i
sleep 60
end
Okay, fine. Now if I notice them piling up too much, I can 'fg' the
script and then stop it until the queue clears up.
Anyway, the point is this: just as I had suspected, one or two other
people printed a file or two to 'python' and pretty soon I started
getting the zephyr notificatons for some (but not all) of their jobs.
There. That's more detail than necessary. If you can't repeat it,
I'll try storing all the (time-stamped) z-grams in an emacs buffer with
zwgc.el, and starting something up to do a periodic lpq so that you
can look at exactly what the timing is. I hope this won't be necessary,
but I just wanted to remind you that this bug still exists.
