[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
|
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
8710.0. "V3.2D-2, Print Jobs not getting printed in desired order..." by QCAV02::NRHEGDE (T&E or R&D !?) Wed Feb 05 1997 01:18
Hi !
On Digital Unix V3.2D-2 we have a problem in which print jobs created within
a short timeframe, for example within the same second, were not sorted by
print jobs and timestamps. This resulted in print jobs not being printed
in the desired order.
It is a network printer. (xerox 4230 remote printer)
There is a patch for digital Unix V3.2-D1 for such problems. Is there any
such patches for digital unix V3.2D-2. I searched in README file for
V3.2D-2 patches and could not find one for this problem.
Thx & regards
Nagaraj Hegde
(Following patch details for Digital Unix V3.2D-1)
============================ << START OF PATCH >> ==============================
PATCH ID: OSF360-350183 SUBSET(s): OSFPRINT350
********************************************************************************
SUPERSEDED PATCHES: OSF360-350172
PROBLEM: ( HPXQ846D7 ) (Patch ID: OSF360-350172)
********
This patch corrects a problem were printjobs cause existing jobs to be deleted
from the queue whenever the number of print queue entries exceeded 1000.
Example:
The cfA005bozo file in /usr/spool/lpxx exists.
The next print queue tries to create cfA005bozo.
After error message "Cannot create cfA005bozo" shows up, do
"ls -l /usr/spoo/lpxx/cfA005bozo". This file will be
deleted.
PROBLEM: ( MGO101607 ) (Patch ID: OSF360-350183)
********
This patch corrects a problem in which print jobs created within a short
timeframe, for example within the same second, were not sorted by print jobs
and timestamps. This resulted in print jobs not being printed in the desired
order.
Example: Prior to the fix
#ls -tr *.lis
users.lis users1.lis users2.ls users3.lis users4.lis
users5.lis
.
# foreach i (`ls -tr *.lis`)
? lpr -Pxxx $i
? end
.
# ls -lt /var/spool/xxx/cf*
-rw-rw---- 1 daemon daemon 132 Jul 11 10:07 cfA005osfmbh
.aui.dec.com
-rw-rw---- 1 daemon daemon 132 Jul 11 10:07 cfA007osfmbh
.aui.dec.com
-rw-rw---- 1 daemon daemon 132 Jul 11 10:07 cfA006osfmbh
.aui.dec.com
-rw-rw---- 1 daemon daemon 132 Jul 11 10:07 cfA004osfmbh
.aui.dec.com
-rw-rw---- 1 daemon daemon 132 Jul 11 10:07 cfA003osfmbh
.aui.dec.com
# lpq -Pxxx
Fri Feb 17 10:46:29 1995:
Rank Pri Owner Job Files Total Size
1st 0 bozo 3 users.lis 23
2nd 0 bozo 4 users1.lis 23
3rd 0 bozo 6 users3.lis 23
4th 0 bozo 7 users4.lis 23
5th 0 bozo 5 users2.lis 23
6th 0 bozo 8 users5.lis 23
As you can see, the file users2.lis has Job number 5 which is the 3rd Job
but gets ranked in the 5th position and will not be printed in the desired order
after the file user1.lis despite of the fact that all files had been created with the
same timestamp (eg. Jul 11 10:07).
Example: the order should be the following after the fix
# lpq -Pxxx
Fri Feb 17 10:46:29 1995:
Rank Pri Owner Job Files Total Size
1st 0 bozo 3 users.lis 23
2nd 0 bozo 4 users1.lis 23
3rd 0 bozo 5 users2.lis 23
4th 0 bozo 6 users3.lis 23
5th 0 bozo 7 users4.lis 23
6th 0 bozo 8 users5.lis 23
FILE(s):
/usr/lbin/lpd subset OSFPRINT350
CHECKSUM: 01343 96 RCS: lpd.c Revision: 4.2.17.2
lpdchar.c Revision: 4.2
/usr/bin/lpr subset OSFPRINT350
CHECKSUM: 12404 48 RCS: lpr.c Revision: 4.2.33.2
/usr/bin/lprm subset OSFPRINT350
CHECKSUM: 12245 40 RCS: lprm.c Revision: 4.2.6.2
/usr/bin/lpq subset OSFPRINT350
CHECKSUM: 61816 48 RCS: lpq.c Revision: 4.2.5.2
-----------------------------------------------------------------
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|