LP

[Vas Kathirvasan]

I have got many lpsched running on the server at the same time. no matter if you stop and start the lpsched it will have about 24 of them running at the same time?

[John Palmer]

lpsched spawns a copy of itself when it starts printing activity on a queue. Is it possible that you have got 24 active queues?

If not then ensure that you have the latest lpspool subsystem cumulative patch applied.

Hope this helps,

John

[CHRIS_ANORUO]

Do a 2ps -ef|grep lpsch*", check the start time of the process, owner(if not lp). If the start time is very old, you can kill the processes.

[Andreas Voss]

Hi,

with ps -fulp you can see the processes that are associated to the user lp.
Look for zombies/parent/child-processes of your lpsched's

Andrew

[Vincente Fernandes]

1. do lpshut, then kill all the other lpsched process. remove file "FIFO" & "SCHEDLOCK" from "/var/spool/lp" directory.
2. do lpsched.
3. If this doesn't solve, try installing the latest lpspool cumulative patch.

[Brian M. Fisher]

Have you turned on lpsched logging to look for any potential errors/problems? To do this:
1) lpshut
2) lpsched -v
3) monitor log file /var/adm/lp/log

I hope this helps,
Brian
<*(((>< er