topic Re: lpsched problem in Operating System - HP-UX

lpsched problem

Joyce Suganthy — Sun, 16 Nov 2003 21:33:51 GMT

Hi,

I have a problem in some serves. The lpsched is always down when the machine is rebooted, and i have to manually bring it up. When i check the /etc/rc.log the starting up of the /lpsched is SKIPPED. Please advice

regards
Joyce

Re: lpsched problem

Michael Tully — Sun, 16 Nov 2003 21:38:02 GMT

Hi,

Make sure that the /etc/rc.config.d/lp file has a '1' instead of a '0'. Having a zero tells the script to skip starting the daemon. See my example below.

#!/sbin/sh
# @(#)B.11.11_LR
# LP spooler configuration
#
# LP: Set to 1 to start LP spooler
#
LP=1

Regards
Michael

Re: lpsched problem

Joyce Suganthy — Sun, 16 Nov 2003 21:48:32 GMT

Michel.

I have checked the setting is set to 1. Please advice

Regards

Re: lpsched problem

Michael Tully — Sun, 16 Nov 2003 21:56:17 GMT

okay, what commmand(s) do you use to manually start the spooler?

what happens when you use?
# /sbin/init.d/lp start

What is in the output in /etc/rc.log when the spooler has attempted to start. Here is a snippet from mine.

Start print spooler
Output from "/sbin/rc2.d/S720lp start":
----------------------------
scheduler is running
line printer scheduler started

Re: lpsched problem

Joyce Suganthy — Sun, 16 Nov 2003 22:15:24 GMT

Hi

This is what I encountered in /etc/rc.log

Start print spooler
Output from "/sbin/rc2.d/S720lp start":
----------------------------
"/sbin/rc2.d/S720lp start" SKIPPED

regards
joyce

Re: lpsched problem

Patrick Wallek — Sun, 16 Nov 2003 22:20:05 GMT

What happens if you do an:

# ll /etc/rc.config.d/lp*

Do you have more than one lp file? Maybe an lp.bak or an lp.old? If so, remove it. You never want to keep any backup files in /etc/rc.config.d as they can thoroughly mess up your box when it boots.

Re: lpsched problem

Joyce Suganthy — Sun, 16 Nov 2003 22:29:38 GMT

Hi,

I don see any files except this

-r--r--r-- 1 bin bin 108 Nov 14 2000 /etc/rc.config.d/lp

Please advice

Joyce

Re: lpsched problem

Bill Hassell — Sun, 16 Nov 2003 22:37:03 GMT

Start by running the lp startup script in trace mode:

sh -x /sbin/init.d/lp start 2>&1 | more

The 2>&1 redirects the trace output to stdout and more gives you a chance to look at the results. Or you can simply change |more to > /var/tmp/somefile so you can paste the results here. There are two conditions required in the script to start:

$LP must be 1 and -s /var/spool/lp/pstatus which means pstatus must exist and not be zero length.

Re: lpsched problem

T G Manikandan — Sun, 16 Nov 2003 22:49:01 GMT

The problem is with the /var/spool/lp/pstatus equal to 0 which will not start the services.

check this doc

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062942437

Re: lpsched problem

Joyce Suganthy — Sun, 16 Nov 2003 23:32:31 GMT

hi TG Manikandan,

I will try the solution given .

Thanks again

Regards
Joyce

Re: lpsched problem

Bill Hassell — Mon, 17 Nov 2003 21:24:38 GMT

Just a logic note: if pstatus is zero length, then there are no printers defined and there is no reason for lpsched to run. So until you define a printer, the lp spooler will not be started at bootup.

Re: lpsched problem

Joyce Suganthy — Mon, 17 Nov 2003 21:30:11 GMT

hi,

I have another question, that option given by Manikandan is to create a dummy printer...

Well I have checked with my admin here locally that the lpsched would not start at boot if there is no defined printer in the server. Creating a dummy printer would be an option

But is there any doc that supports this?

Thanks

Regards

Re: lpsched problem

Bill Hassell — Tue, 18 Nov 2003 08:02:42 GMT

Sure. The startup script /sbin/init.d/lp clearly documents this behavior. If the pstatus file is missing or zero length, lpsched is not started. (pstatus is the list of installed printers) Is it documented in the manuals? I doubt it. It's more of a common sense feature...why would you want to start lpsched if there are no printers defined?