Summary: | net-im/jabberd2: Stopping service kills all running transports | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Milko Krachounov <exabyte> |
Component: | [OLD] Server | Assignee: | Julian Ospald <hasufell> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | gentoo, marko.durkovic, net-im |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Milko Krachounov
2008-10-11 22:23:25 UTC
Oops, I'm sorry, I just noticed that this is due to (mis)configuration on my part. I'd made the decision to put the pid files of each transport in /var/run/jabber. If the behaviour of killing all services having pids in there is considered correct, my bug report seems to be invalid. :) Yes, this is intended behaviour. Quoting from the init script: stopJabberServices() { eindent for pidfile in /var/run/jabber/*.pid; do if [ -f "${pidfile}" ]; then service=$(basename ${pidfile} .pid) ebegin "Stopping ${service}" start-stop-daemon \ --stop \ --pidfile ${pidfile} eend $? fi done eoutdent } This isn't invalid. net-im/pymsn-t that is in portage puts its pid in /var/run/jabber (and so do most other transports), so the jabberd init script breaks them, resulting in what I described. Also killing all pids in the /var/run/jabber directory (regardless of where did they come from) is wrong behaviour. Putting the pid of a jabber related service in /var/run/jabber shouldn't be an error, and shouldn't cause problems like this. (In reply to comment #3) > net-im/pymsn-t that is in portage puts its pid in /var/run/jabber (and so do > most other transports), so the jabberd init script breaks them, resulting in > what I described. Also killing all pids in the /var/run/jabber directory > (regardless of where did they come from) is wrong behaviour. Putting the pid of > a jabber related service in /var/run/jabber shouldn't be an error, and > shouldn't cause problems like this. IMHO there are 2 possibilities to solve the problem: - prefix all jabberd2-pid-files (e.g. jabberd2-c2s.pid) - check if there is a valid config-file for pid-file Problem: The last one did not stop jabberd2 services if they will be removed from the config file. Any other suggestions? *** Bug 269010 has been marked as a duplicate of this bug. *** + 03 Nov 2013; Julian Ospald <hasufell@gentoo.org> jabberd2-2.2.17-r1.ebuild: + rename pid files wrt #241472 use etc-update or do it manually |