In jabber.rc6-r[56] jabber stopped using killall. I think using start-stop-daemon and pid-file is a better solution. For using this following changes are required: 1. Creating directory /var/run/jabber with jabber:jabber ownership. 2. Changing line in multiple.xml <pidfile>./jabber.pid</pidfile> to <pidfile>/var/run/jabber/jabberd.pid</pidfile> 3. In each jabber transport config (aimtrans.xml, jit.xml, etc.) adding line like this: <pidfile>/var/run/jabber/jabberd.aimtrans.pid</pidfile> 4. Changing /etc/init.d/jabber to use start-stop-daemon After those changes it's also possible to split init-script into more simplier scripts for each jabber component. Adding new component that does not use jabberd (like jit and janchor) will be very easy in this case.
I personally like the idea. Because it also helps with some other things i was thinking (like jabberd2). I will try to work this out.
I did a small script for the msn transport it is in cvs but i will post it here. Also ALL transports need to have such a script before I start to change the ebuilds.
Created attachment 27636 [details] msn-transport.init
Created attachment 27640 [details] msn-transport-20040228.ebuild Updated ebuild for msn that will install the new service. Also there is an update to the version of the transport"
Created attachment 27643 [details] msnt.xml Updated msnt.xml to creat the pid necessary to kill the service. This makes it all for msn-transport. Next is aim. Also please note that jabber will be the last to be made because that service will have to know if it will start a jabberd1.4 or a jabberd2 and i still have some doubts on the proper way to do that.
Created attachment 27644 [details] aim-transport.init
Created attachment 27645 [details] aimtrans.xml
Created attachment 27646 [details] aim-transport-20040131-r1.ebuild
Created attachment 27657 [details] mu-conference-0.6.0-r1.ebuild
Created attachment 27658 [details] muc-transport.init
Created attachment 27659 [details] muctrans.xml
Created attachment 27661 [details] mu-conference-0.6.0-r1.ebuild Missing einfo
Created attachment 27663 [details] yahoo-transport-2.3.0-r2.ebuild
Created attachment 27664 [details] yahoo-transport.init
Created attachment 27665 [details] yahootrans.xml
Created attachment 28166 [details] jit-1.1.6-r3.ebuild
Created attachment 28167 [details] jit-transport.init
Created attachment 28168 [details] jit.xml
Created attachment 28217 [details] jabber.rc6-r7
Created attachment 28218 [details] jabber-conf.d
Created attachment 28219 [details] multiple-xml-patch-01
Created attachment 28220 [details] jabberd-1.4.3-r3.ebuild With this the main work is done. I will start adding this to portage (hard masked) in a few days, after i have the time to test it in a new box that i am setting up.
Created attachment 31828 [details] /etc/init.d/jabber moved 'kill' line down Hi, In /etc/init.d/jabber I moved line with killing 1.4 jabberd down 1 line, so now I do not get the following error message when restarting jabber: mail3 conf.d # /etc/init.d/jabber stop * Stopping main Jabber Component... /sbin/runscript.sh: line 1: /var/log/jabber/jabberd14.pid: No such file or direc tory kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec]
Created attachment 31829 [details, diff] /etc/init.d/jabber moved 'kill' line down Hi, In /etc/init.d/jabber I moved line with killing 1.4 jabberd down 1 line, so now I do not get the following error message when restarting jabber: mail3 conf.d # /etc/init.d/jabber stop * Stopping main Jabber Component... /sbin/runscript.sh: line 1: /var/log/jabber/jabberd14.pid: No such file or direc tory kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec]
All this is portage for some time so i guess it is time to close. Thanks to all involved.
