hi Patrick,
we had discussed this already further:
the behaviour of LPRng has changed, independent from the other 8
versions of lpstat
it may look like a small cosmetic thing but in large environments there
are 100's of scripts and,
even worse 100's of commercial applications depending on this behaviour.
E.g. Oracle application don't
print reports anymore because they perform a lpstat on the queue and get
irritated about the
additional 2 lines in the response. This leads me to stupid things like
installing wrapperscripts on
~1.200 UNIX machines. You asked me a few weeks ago to check your beta
release (3.7.1beta2) and there is still an additional line in the lpstat
response:
> > >>>printer pubps2 unknown state. enabled since Nov 09 11:12 2000. available
I'm looking forward to meet you at LISA perhaps we could talk about the
conditions for a support contract ...
regards Christoph
hi,
in former versions of lprng I was forced to use lpstat -p<printername>
to get the status. LPRng 3.6.26 is behaving different, I'm running into
big trouble with this behaviour, for ex Oracle doesn't print any
>reports
etc...
[pcx1839] ~ $ ~lp/bin/lpstat -ppubps2
printer pubps2 unknown state. enabled since Oct 26 16:53 2000. available
printer pubps2 unknown state. enabled since Oct 26 16:53 2000. available
Printer: pubps2@pcx1839 '2b_131_p2' (dest pubps2@spoolb)
Queue: no printable jobs in queue
Status: job 'chbeyer@pcx1839+165' removed at 11:25:40.639
Filter_status: sending to spoolb
Printer: pubps2@spoolb 'HP_8000DN PS_2 2 A4 p Operators, 3818,
A4/foil-automatic'
Queue: no printable jobs in queue
Status: job 'expo14@puls07+875' removed at 16:51:23
Filter_status: Oct26/16:51 Job finished with no problems: Ready
[pcx1839] ~ $ ~lp/bin/lpstat -opubps2
Printer: pubps2@pcx1839 '2b_131_p2' (dest pubps2@spoolb)
Queue: no printable jobs in queue
Status: job 'chbeyer@pcx1839+165' removed at 11:25:40.639
Filter_status: sending to spoolb
Printer: pubps2@spoolb 'HP_8000DN PS_2 2 A4 p Operators, 3818,
A4/foil-automatic'
Queue: no printable jobs in queue
Status: job 'expo14@puls07+875' removed at 16:51:23
Filter_status: Oct26/16:51 Job finished with no problems: Ready
[pcx1839] ~ $ ~lp/bin/lpstat pubps2
Printer: pubps2@pcx1839 '2b_131_p2' (dest pubps2@spoolb)
Queue: no printable jobs in queue
Status: job 'chbeyer@pcx1839+165' removed at 11:25:40.639
Filter_status: sending to spoolb
Printer: pubps2@spoolb 'HP_8000DN PS_2 2 A4 p Operators, 3818,
A4/foil-automatic'
Queue: no printable jobs in queue
Status: job 'expo14@puls07+875' removed at 16:51:23
Filter_status: Oct26/16:51 Job finished with no problems: Ready
regards Christoph
[EMAIL PROTECTED] schrieb:
>
> > From [EMAIL PROTECTED] Thu Nov 9 03:25:14 2000
> > Date: Thu, 09 Nov 2000 11:27:29 +0100
> > From: Christoph Beyer <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: LPRng: lpstat bug not fixed in 3.7.1beta2
> >
> > hi,
> >
> > the lpstat still got a 'wrong' or unexpected line in it (tried version
> > 3.7.1beta2):
>
> lpstat has 9 different versions from various manufacturers and returns
> at least 4 different formats. Which version are you using?
>
> I know, I know - it is as bad as 'lpq' status formats.
>
> >
> > [pcx2441] ~lp/sbin # /tmp/LPRng-3.7.1beta2/src/lpstat -ppubps2
> > >>>printer pubps2 unknown state. enabled since Nov 09 11:12 2000. available
> > Printer: pubps2@spoolb 'HP_8000DN PS_2 2 A4 p Operators, 3818,
> > A4/foil-automatic'
> > Queue: 1 printable job
> > Server: pid 25511 active
> > Unspooler: pid 25512 active
> > Status: processing 'dfA104h1desy03.desy.de', size 19562855, format 'f',
> > IF filter 'lpr2unisap' at 11:10:36
> > Filter_status: Nov09/11:10 Job started : Transmitting data.
> > Rank Owner/ID Class Job Files Size
> > Time
> > active martynia@h1desy03+104 A 104 /tmp/Acrob07197 19562855
> > 11:10:36
> >
> >
> > regards C. Beyer
>
> -----------------------------------------------------------------------------
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
>
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body. For the impatient,
> to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
> with: | example:
> subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems, send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------
--
/* Christoph Beyer | Office: Building 2b / 23 *\
* DESY | Phone: 040-8998-2317 *
* - IT - | Fax: 040-8998-4060 *
\* 22603 Hamburg | http://www.desy.de */
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
