(In reply to comment #20)
> (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...
If you use
--make-pidfile \
--pidfile /var/run/jabber/$(basename ${cfgfile%.xml}).pid \
instead of
--pid /var/run/jabber/$(basename ${cfgfile%.xml}).pid \
then init-script will create a pid-file. --pid seems to be wrong according to manpage
IMHO we should ignore pidfile in xml-config (comment it for default config in ebuild) and use pid-files created by init-script.
(In reply to comment #20)
> (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...
If you use jabber/ $(basename ${cfgfile% .xml}). pid \
--make-pidfile \
--pidfile /var/run/
instead of jabber/ $(basename ${cfgfile% .xml}). pid \
--pid /var/run/
then init-script will create a pid-file. --pid seems to be wrong according to manpage
IMHO we should ignore pidfile in xml-config (comment it for default config in ebuild) and use pid-files created by init-script.