[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

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

8802.0. "V3.2G, Lat printing goes to sleep" by NETRIX::"[email protected]" (Gary Kerrison) Wed Feb 12 1997 05:12

	Hello

	I've a few problems with printing on V3.2g.

	The queues seem to go to sleep and won't awake unless you
	do a lpc restart.

	are there any LAT or lpd funnies out there in 3.2g land?

	This IS intermittent. and we've tried to isolate the cause
	but to no avail.

	We're using DECserver 90TL and DECserver 900TMs.

	The printers are not using xon/xoff flow control. They're
	using dtr/dsr, and that is the setting on the terminal servers...

	this is getting serious as we're rolling this out onto 260+
	systems.

	any ideas?

	Gary

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
8802.1more infoNETRIX::"[email protected]"gkThu Feb 20 1997 12:1545

	Hi

	I've reproduced the problem in house (I think).

	the printer is on, and online, the TS is loaded and on.

	lpc stat 

	says "waiting for lp0 to become ready (offline?)"

	and it HAS been working.

	now i know (well on the customer sites it fixes it) that a lpc restart
	will cure the problem - I'd rather not do that for now.

	I've been in the Terminal servers notes file and ascertained that flow
	control between the TS and UNIX (on LAT) is done by "credits".

	Perhaps there is something a bit flaky around this area in some
	situations?

	Anything queued just sites there in the queue - and doesn't leave.

	No indication of any sort (LEDs for example) that data is getting to 
	the port on the TS for the printer.

	can we ascertain whether UNIX lat is waiting for something (a credit)?

	a reboot of the TS achieves nothing, and a power cycle of the printer
	nothing also. 

	Why would lat tell lpd not to send data?

	might it be a non-interaction between UNIX and the TS LAT sw versions?
	

	ideas please!

	ta

	Gary

[Posted by WWW Notes gateway]
8802.2nope not that, but this too!NETRIX::"[email protected]"grekWed Feb 26 1997 04:5127

Hmm

last reply was a red herring. someone blew up the terminal server and
replaced it - without changing the /etc/latstartup.conf entry!

however NOW we've seen problems on 3.2 NOT including lat.

on another customer site a HP5si with jetdirect card - set up as a
remote printer (from varoius machines I'm told) decided that it wasn't
going to print. Although it had been perfectly happy.

the printer wasn't particularly busy, but then decided it wasn't going to
print for a while - and then restarted when "it felt like it"...

any ideas? it too seems flow control-ish... 

so different network, printer, printcap

same lpd, same problem?

any ideas?

Gary

[Posted by WWW Notes gateway]