On 6/5/07, Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
[Ritesh Raj Sarraf]
> I have cups installed for printing related work.
>
> I've CONCURRENCY=shell in my /etc/init.d/rc script.
>
> With these settings, on boot, my box doesn't send a command to the
> printer when I request for a print. I'm manually required to
> restart cupsys to be able to print.
This sound to me like a bug in the boot ordering, and that
init.d/cupsys using the "wrong" order number, ie it can not start at
the same time as those with the same order number as itself, and need
to be moved to a higher order number.
On system startup, the cupsys daemon is started as reported by the
status command.
When using CONCURRENCY=shell, all init.d scripts with the same
sequence number must be able to start at the same time.
I'll look into the initscript to see if it has any dependency on other services.
Ritesh
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
"Stealing logic from one person is plagiarism, stealing from many is research."
"The great are those who achieve the impossible, the petty are those
who cannot - rrs"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
