[comp.unix.xenix.sco] Trouble with Line Printer Spooler under XENIX

meyer@mimsy.umd.edu (John R. Meyer) (11/24/90)

Hello --

	I am having problems with a newly-installed XENIX-386 2.3.2
system.  The line printer spooler system is not working properly.
I used "mkdev lp" to assign a default printer named "printer" to
device /dev/lp0 and used lpr to spool a file.  The file got spooled
and lpstat shows it, but the file does not get printed.  I know it's
not the hardware because I can send the file directly to the /dev/lp0
device.

	Anyone have any suggestions?  What else should I be looking
for?

					Thanks,

						John
-- 
John R. Meyer				Domain: meyer@mimsy.umd.edu
10208-C Ashbrooke Ct.			Path:   uunet.uu.net!mimsy!meyer
Oakton, VA 22124 USA			Phone:  (703) 802-1872 (O)
Disclaimer:  The views expressed are my own.	(703) 281-5157 (H)

ralfi@pemstgt.PEM-Stuttgart.de (Ralf Holighaus) (11/27/90)

Do you have the lp scheduler running? And is the printer enabled?
You can check both by the
	lpstat -t
command...

If the scheduler is NOT running, start it as root with /usr/lib/lpsched.
IF it stops running eagain, there might be some configuration problem,
which you may be able to find out by checking the /usr/spool/lp/logfile.

rgds
ralf h.
-- 
Programmentwicklung fuer    Microcomputer |         Ralf U. Holighaus
PO-Box 810165        Vaihinger Strasse 49 |         >> PEM Support <<
D-7000 Stuttgart 80          West Germany | holighaus@pemstgt.PEM-Stuttgart.de
VOICE: x49-711-713045 FAX: x49-721-713047 |      ..!unido!pemstgt!ralfi 

aris@tabbs.UUCP (Aris Stathakis) (11/30/90)

In <1990Nov26.210113.2874@pemstgt.PEM-Stuttgart.de> ralfi@pemstgt.PEM-Stuttgart.de (Ralf Holighaus) writes:


>Do you have the lp scheduler running? And is the printer enabled?
>You can check both by the
>	lpstat -t
>command...

I didn't catch the original article here, but there is a replacement print
spooler for SCO Xenix 2.3.2 which fix's some minor bugs.  Just ask SCO
or your distributor for the free Support Level Supplement xnx142 .

Aris

-- 
 Aris Stathakis | Bang: ..!uunet!ddsw1!olsa99!tabbs!aris or aris@tabbs.UUCP
-                                                                          -
-    I'd rather have a bottle in front of me, than a frontal lobotomy.     -

paulz@sco.COM (W. Paul Zola) (12/18/90)

In article <27952@mimsy.umd.edu> meyer@mimsy.umd.edu (John R. Meyer) writes:
}Hello --
}
}	I am having problems with a newly-installed XENIX-386 2.3.2
}system.  The line printer spooler system is not working properly.
}I used "mkdev lp" to assign a default printer named "printer" to
}device /dev/lp0 and used lpr to spool a file.  The file got spooled
}and lpstat shows it, but the file does not get printed.  I know it's
}not the hardware because I can send the file directly to the /dev/lp0
}device.
}
}	Anyone have any suggestions?  What else should I be looking
}for?
}
}					Thanks,
}
}						John
}-- 
}John R. Meyer				Domain: meyer@mimsy.umd.edu
}10208-C Ashbrooke Ct.			Path:   uunet.uu.net!mimsy!meyer
}Oakton, VA 22124 USA			Phone:  (703) 802-1872 (O)
}Disclaimer:  The views expressed are my own.	(703) 281-5157 (H)

Here are some suggestions on your problem from the SCO IT database.
I hope these help.

################## cut here ################ cut here ##################

Jobs spool up but they don't print out under SCO XENIX Release 2.3

RELEASE:  SCO XENIX 386 Operating System Release 2.3

PROBLEM:  I'm having problems keeping the spooler running under SCO XENIX
          386 Operating System Release 2.3.  What can I do to correct this?

SYMPTOMS: (1) When printing to the default printer, jobs spool up but never 
	  print out.  If you change the default printer to something else, 
	  all jobs for the old default printer start printing.  

	  (2) Jobs to all printers spool up and never print out.  'lpstat -t'
	  shows that the printers are enabled and accepting requests, and
	  that the scheduler is running, but nothing prints out.

SOLUTION: Here are some solutions for spooler problems in SCO XENIX 386 
	  Operating System Release 2.3.  You will need to log in as root
	  to implement any of these fixes.


  (1) When the scheduler hangs, perform a directory listing of the
  /usr/spool/lpd directory.  If there are files in the directory, remove all 
  of them.  Removing these lock files should cause the scheduler to start up 
  again.

  (2) Change directories to /usr/spool/lp/interface.  Each printer that you 
  have configured will have a corresponding file with the same name in this 
  directory.  Edit each file with your favorite text editor.  Find the line
  that reads:
	
      exit 0
      
  Typically, this is the last line in the file.  Insert a new line
  immediately above this one, so that the file now reads:

      stty -hupcl 0<&1
      exit 0

  Reboot your system.  Your queued jobs should start printing out at this
  time.

  (3) Use lpinit or mkdev lp to create a printer with the name 'bogus'.  Set 
  up the printer so that the device associated with the printer is 
  "/dev/tty012", and that the printer uses the "dumb" interface.  Then use 
  the 'Reconfigure' option of 'mkdev lp' to associate the printer 'bogus' 
  with the device "/dev/null".  
  
  Next, edit the file /etc/profile and add the following lines:

      LPDEST=printername
      export LPDEST

  where 'printername' is the name of the printer to be used as the actual 
  default printer.

  Next, add the following line in /etc/cshrc:

      setenv LPDEST printername

  where 'printername' is the name of the printer to be used as the actual 
  default printer.

  Finally, set up the printer 'bogus' as the system default printer.  Your
  queued jobs should start printing out at this time.

################## cut here ################ cut here ##################
-
Paul Zola			Software Support Engineer 
				paulz@sco.COM 
We only know in theory what we are doing.   - Kate Bush
    DISCLAIMER: I speak for myself, and not for SCO.