Date: Wed, 03 May 2006 19:11:01 -0500 From: Eric Schuele <e.schuele@computer.org> To: "P.U.Kruppa" <root@pukruppa.de> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Cupsd strangeness.... Message-ID: <44594695.9090806@computer.org> In-Reply-To: <20060503224204.L968@www.pukruppa.net> References: <44576B3F.8020804@computer.org> <20060503224204.L968@www.pukruppa.net>
next in thread | previous in thread | raw e-mail | index | archive | help
P.U.Kruppa wrote:
> On Tue, 2 May 2006, Eric Schuele wrote:
>
>> Hello,
>>
>> While this should be of absolutely no real concern.... my lack of
>> ability to resolve it is causing me sleepless nights. I'm sure this
>> should be an easy one... I just can't seem to fix it.
>>
>> Everything cups related is working perfectly fine. However, my dmesg
>> shows the following:
>>
>> Starting cupsd.
>> Starting cupsd.
>> cupsd: Child exited with status 48!
>> Usage: cups {reload|restart|start|status|stop}
>>
>> And its driving me crazy! Cupsd is trying to start twice? and the
>> second time is giving an error.
>>
>> What have I done wrong here?
>> [~] % ls /etc/rc.d | grep cups
>> [~]
>> % ls /usr/local/etc/rc.d | grep cups
>> cups.sh.delme*
>> cups.sh.sample*
>> cupsd.delme*
>> cupsd.sample*
>> cupsd.sh*
> Nowadays all executable scripts in rc.d/ will be executed, not only
> those ending on .sh
Yes. That was it. Thanks.
However, I had thought that the behavior to be different. My man page
(from 6.0-RC?) reads:
The following key points apply to old-style scripts in
/usr/local/etc/rc.d/:
ยท Scripts are only executed if their basename(1) matches the shell
globbing pattern *.sh, and they are executable. Any other files or
directories present within the directory are silently ignored.
Has the behavior changed? It was my understanding that files with *.sh
or no extension (yet executable), would be run.
Thanks again.
>
> Regards,
>
> Uli.
>
>
>
>
>> [~] % grep cups /etc/rc.conf
>> cupsd_enable="YES"
>> #cups_enable="YES"
>>
>> Using FreeBSD 6.1-RC as of Sat some time... but had this problem quite
>> a while. I'm sure it started the last time I rebuilt the machine (two
>> month back maybe). And I'm sure its a config error on my part.
>>
>> Any help is appreciated.
>>
>> --
>> Regards,
>> Eric
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe@freebsd.org"
>>
>
>
>
> *********************************************
> * Peter Ulrich Kruppa - Wuppertal - Germany *
> *********************************************
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"
>
--
Regards,
Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44594695.9090806>