| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 938.1 |  | KERNEL::COFFEYJ | La Feline Flooz - a unix cat | Mon Apr 21 1997 13:02 | 1 | 
|  | Copy of /etc/printcap'd help......
 | 
| 938.2 | specific parameter ?? | 51513::H_ANDERSSON |  | Mon Apr 21 1997 14:43 | 8 | 
|  |     
    Is there a specific parameter you want ??
    
    The que is working fine except when there is a 30
    min delay between two printjobs. After power off/on
    the printer prints the queued jobs.
    
    /Hakan
 | 
| 938.3 | which parameter - all of them for that printer. | KERNEL::COFFEYJ | La Feline Flooz - a unix cat | Tue Apr 22 1997 11:39 | 34 | 
|  |   >Is there a specific parameter you want ??
  
No not really but when asking for help 
it usually makes it easier for those trying to 
help if they have all the data. 
With printing calls the /etc/printcap entry for 
that printer is the very basic starting point 
to make sure there's nothing very basic/blatantly 
obviously wrong in the setup. 
Also you say remote queue. 
If you really mean remote there'll only be about 
4 parameters set anyway. If what you actually 
mean is a network printer then every parameter 
is relevant. 
If it's set up as remote your problem is very likely 
with the printer. 
Still you've reminded me I still haven't logged the 
QAR begging and grovelling for proper debugging like we 
had in Ultrix to be put into digital Unix's lpd. 
Life became so much harder as a unix printing support 
person when that was all stripped out and suddenly the 
incantation "dee bee hash nine" no longer worked magic... 
<sigh>
Ultrix Lover :-) 
 | 
| 938.4 | Re: DECLaser 3500 problem. | NNTPD::"[email protected]" | Richard Hart | Mon May 12 1997 20:43 | 17 | 
|  | Here are a couple of other things that might help:
1. What does the little status window say? Is the printer ONLINE and Idle, or
in some other state?
2. Do you have software anywhere else trying to connect to the printer? These
symptoms sound a bit like someone else getting a connection to the printer and
then hanging on to it.
Also, if you are using V4.0{A, B, or C}, you might want to try the tcp/ip
connection method which was introduced in V4.
And for the Ultrix lovers, some Ultrix style debugging features are being
planned and implemented, as I type, for the next major release..
Richard Hart
[Posted by WWW Notes gateway]
 | 
| 938.5 | I have the same problem | VAXRIO::MIRIAM | Unix Group - CSC/Brazil | Wed May 28 1997 19:24 | 76 | 
|  |     
     Hi,
    
      I'm facing a similar problem. The customer uses the printer with no
    problem. After 3 or 4 hours without using the printer it doesn't print
    any job, doesn't answer any ping and only a reset solves the problem.
    The customer har 3 different printer and the problem happens with all
    of them. There are ten Digital UNIX systems printing on them using nic
    filter. One of these systems is a Pathworks server and has a service
    defined for each printer. The printer affected by this problem are:
       il001air   (laser1  for Pathworks)                              
       il002air   (laser2  for Pathworks)                              
       il003air   (laser3  for Pathworks)
     The status shown in the printer display is "IDLE"
                                  
     Here is the customer's printcap:
       #
       il001air|lp|NICprinter1|il001air:\
               :if=/usr/nic/infilter:\
               :lp=/dev/nic/il001air:\
               :of=/usr/nic/outfilter:\
               :sd=/usr/spool/il001air:\
               :sh:
       #                             
       #
       il002air|lp|NICprinter2|il002air:\
               :if=/usr/nic/infilter:\
               :lp=/dev/nic/il002air:\
               :of=/usr/nic/outfilter:\
               :sd=/usr/spool/il002air:\
               :sh:
       #                             
       #
       il003air|lp|NICprinter3|il003air:\
               :if=/usr/nic/infilter:\
               :lp=/dev/nic/il003air:\
               :of=/usr/nic/outfilter:\
               :sd=/usr/spool/il003air:\
               :sh:
       #                           
       lmxnul:\
               :lf=/usr/net/servers/lanman/logs/lplogs/lmxnul:\
               :sd=/usr/spool/lmxnul:\
               :xf=/usr/lbin/xf:\
               :if=/usr/lbin/lpf:\
               :of=/usr/lbin/lpf:\
               :lp=/dev/null:      
       lmxone:\
               :lf=/usr/net/servers/lanman/logs/lplogs/lmxone:\
               :sd=/usr/spool/lmxone:\
               :xf=/usr/lbin/xf:\
               :if=/usr/lbin/lpf:\
               :of=/usr/lbin/lpf:\
               :lp=/dev/null:                           
       laser1:\              
               :lf=/usr/net/servers/lanman/logs/lplogs/laser1:\
               :lp=/dev/null:\
               :if=/usr/lbin/pcsaclass:\                                
               :sd=/usr/net/servers/lanman/spool/laser1:
       laser2:\              
               :lf=/usr/net/servers/lanman/logs/lplogs/laser2:\
               :lp=/dev/null:\
               :if=/usr/lbin/pcsaclass:\                                
               :sd=/usr/net/servers/lanman/spool/laser2:
       laser3:\              
               :lf=/usr/net/servers/lanman/logs/lplogs/laser3:\
               :lp=/dev/null:\
               :if=/usr/lbin/pcsaclass:\                                
               :sd=/usr/net/servers/lanman/spool/laser3:
    
      Any ideas?
    
      Thanks in advance,
    
        Miriam
        CSC/Brazil
 |