Comment 21 for bug 865158

(In reply to comment #19)
> Init script doesn't create pid file, it must be done by started proccess so
> valid path to pid should be configured in sm-foo.xml. Or we can rely on init
> scirpt, let them make pid file, in this case we should comment out pid file in
> foo.xml.

AFAIR this didn't work. Please try...

> (Parsing xml files from init script doesn't look to be easy).

maybe a simple grep with regex? but i'm not sure if its the right way of doing this...

> I'm not sure what did you mean "as i see
> your init-file simply should ignore all other sm-processes". If you add another
> sm with another sm-foo.xml to /etc/jabber/jabberd.cfg then sm-foo should be
> started as well as other services.

k, for my example... if you want to stop services you do

"grep -v "^ *#" "/etc/jabber/jabberd.cfg" | awk '{print $1}' | tac"

which results in:

sm
sm
sm

So you'll try to stop daemons on sm.pid multiple times instead of using sm.pid, sm-example.org.pid and sm-example2.org.pid