Starting services from rc.M

BerzinTehvs · 12-26-2012, 09:01 AM

Hi!

I have a problem starting all spam-fighting services from rc.M - currently I have issues with DCC and SpamAssassin - while it is possible to start both from console using provided or community start scripts, when I put them into rc.M (in a way like a lot of services there), the rc.M dies on either rcDCC or rc.spamd with no msg anywhere.

BCarey · 12-26-2012, 09:21 AM

It could be a syntax error. Could you post what you put into the rc.M file?

In general you should use /etc/rc.d/rc.local for starting services that you add to your system. That way your custom services will not get overwritten if and when rc.M gets updated. You also may be having a problem because services on which your custom service depends have not been launched yet. rc.local gets run last so if you put things there you are sure that the system is "ready" before your custom services get launched.

Brian

ml4711 · 12-26-2012, 09:23 AM

If you source your start script from rc.M,
and this start script have an exit command, rc.M is the one, that exits.

But why not start those services from rc.local or with the sysvinit system,
which both are sourced from rc.M

It seems those script you want to run, have an exit command somewhere.
I's good enough, but then you have to call it and NOT source it from
the calling script!

Enjoy

BerzinTehvs · 12-26-2012, 09:31 AM

P.S. starting spamassassin not by script (provided along with spamassassin) but by explicit command from rc.M works.

ml4711 · 12-26-2012, 10:03 AM

If you from rc.M call the start script like here

Code:

  /etc/init.d/slackware-rc-script.sh

it works, but if you call it in this way (you source it)

Code:

 . /etc/init.d/slackware-rc-script.sh

The "exit 0" at the end of slackware-rc-script.sh will terminate the rc.M script