The openfire ebuild should provide a systemd unit file, say /usr/lib/systemd/system/openfire.service. Reproducible: Always
+*openfire-3.8.2-r1 (11 Jan 2014) + + 11 Jan 2014; Pacho Ramos <pacho@gentoo.org> +files/openfire.service, + +openfire-3.8.2-r1.ebuild: + Add unit file (#497464) +
(In reply to Pacho Ramos from comment #1) > +*openfire-3.8.2-r1 (11 Jan 2014) > + > + 11 Jan 2014; Pacho Ramos <pacho@gentoo.org> +files/openfire.service, > + +openfire-3.8.2-r1.ebuild: > + Add unit file (#497464) > + It might be not enough to make thing run. init script has such a workaround: [ -d /var/run/jabber ] || mkdir /var/run/jabber I guess it also needs a tmpfiles.d bit (bug #423367)
tmpfiles should handle it indeed, anyway, I though /var/run/jabber was only needed for pidfile and, in that case, it is not needed for service file since we don't need to run "--background" like done in init.d script
(In reply to Pacho Ramos from comment #3) > tmpfiles should handle it indeed, anyway, I though /var/run/jabber was only > needed for pidfile and, in that case, it is not needed for service file > since we don't need to run "--background" like done in init.d script Oh, right. It's only pid file there. Sorry for the noise.
No problem :)