Seems like a bug to me, lpsched essentially keep crashing and restarting. if you have coreadm turn on, you should see that core file. I remember a similar bug such as this in the s10 U3 time frame, it was the fixed.
What releases of S10 d you use? cat /etc/release -Ghee Paul Parsons wrote: > I'm trying to set up printing for the first time on a Solaris 10 system, but > I've never done it before. > > I've tried, but there seems to be a problem with lpsched. If I monitor the > lpsched process, its process ID keeps changing, so I guess it keeps dying and > being restarted or it's forking and dying. > > Can anybody help me to fix this please? I've tried reading the documentation > (lots of documentation!) but there's obviously something going wrong that I > don't understand. > > One of the many things I've tried is: > > bash-3.00# ps -ef | grep lpsched | grep -v grep > root 26549 1 0 15:30:57 ? 0:00 /usr/lib/lp/local/lpsched > bash-3.00# ps -ef | grep lpsched | grep -v grep > root 26605 1 0 15:31:00 ? 0:00 /usr/lib/lp/local/lpsched > bash-3.00# lpshut > Print services stopped. > bash-3.00# ps -ef | grep lpsched | grep -v grep > bash-3.00# svcadm enable application/print/server > bash-3.00# svcs application/print/server > STATE STIME FMRI > online 15:33:37 svc:/application/print/server:default > bash-3.00# ps -ef | grep lpsched | grep -v grep > root 28942 1 0 15:34:11 ? 0:00 /usr/lib/lp/local/lpsched > bash-3.00# ps -ef | grep lpsched | grep -v grep > root 29008 1 0 15:34:14 ? 0:00 /usr/lib/lp/local/lpsched > > Notice that the lpsched process's ID is still changing. > > Thanks for any help you can give me, > > Paul > > > This message posted from opensolaris.org > _______________________________________________ > printing-discuss mailing list > printing-discuss at opensolaris.org >
