(In reply to comment #14) > I've done some changes to ebuild and init script. I hope this fix bug #241472 > (and #269010).
Your init-file may fail on my scenario...
jabberd.cfg: .. sm /etc/jabber/sm.xml sm /etc/jabber/sm-example.org.xml sm /etc/jabber/sm-example2.org.xml ..
pid-files: /var/run/jabber/sm.de.pid /var/run/jabber/sm-example.org.pid /var/run/jabber/sm-example2.org.pid
i have to change pid-filename in .xml when adding another sm by hand. as i see your init-file simply should ignore all other sm-processes :( the big problem is, that pid-files must be configured in xml-file ...
(In reply to comment #14)
> I've done some changes to ebuild and init script. I hope this fix bug #241472
> (and #269010).
Your init-file may fail on my scenario...
jabberd.cfg: sm-example. org.xml sm-example2. org.xml
..
sm /etc/jabber/sm.xml
sm /etc/jabber/
sm /etc/jabber/
..
pid-files: jabber/ sm.de.pid jabber/ sm-example. org.pid jabber/ sm-example2. org.pid
/var/run/
/var/run/
/var/run/
i have to change pid-filename in .xml when adding another sm by hand. as i see your init-file simply should ignore all other sm-processes :( the big problem is, that pid-files must be configured in xml-file ...