Summary: | net-im/openfire-3.7.1: does not start after reboot with baselayout-2.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Timo Rothenpieler <timo> |
Component: | [OLD] Server | Assignee: | Sergei Trofimovich (RETIRED) <slyfox> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | net-im, timo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Timo Rothenpieler
2012-06-24 17:16:51 UTC
(In reply to comment #0) > With baselayout-2.1, /var/run is a symlink to /run, which is a tmpfs, which > is gone after a reboot. > In the openfire init script, start-stop-daemon is told to write a pidfile to > /var/run/jabber/openfire.pid, which fails on a fresh tmpfs, as there is no > jabber subdirectory. > So, after every reboot, openfire does not come up. Nice catch! Reproduced here as well. Pushed as: >*openfire-3.7.1-r1 (26 Jun 2012) > > 26 Jun 2012; Sergei Trofimovich <slyfox@gentoo.org> +openfire-3.7.1-r1.ebuild, > -openfire-3.7.1.ebuild, files/openfire-initd: > Create /var/run/jabber at startup if missing (tmpfs case). Thanks to Timo > Rothenpieler who found and analyzed issue in bug #423367. Thanks for the detailed report, Timo! |