From 1cc8b3c7c55662a146f739e4b5398f965c1c58d1 Mon Sep 17 00:00:00 2001 From: Bertrand Jacquin Date: Fri, 21 Apr 2006 00:22:03 +0200 Subject: ejabberd: initd was wrong --- net-im/ejabberd/files/ejabberd-1.0.0.initd | 2736 +--------------------------- 1 file changed, 52 insertions(+), 2684 deletions(-) diff --git a/net-im/ejabberd/files/ejabberd-1.0.0.initd b/net-im/ejabberd/files/ejabberd-1.0.0.initd index 430f156b..d762311d 100644 --- a/net-im/ejabberd/files/ejabberd-1.0.0.initd +++ b/net-im/ejabberd/files/ejabberd-1.0.0.initd @@ -1,2692 +1,60 @@ - - - - Bug 101708 - ejabberd-1.0.0 (version bump) +#!/sbin/runscript +# Copyright 1999-2005 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: $ +opts="${opts} reload" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -First - Last - Prev - Next -    - No search results available - -     Search page -     Enter new bug - -
- - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Bug#: - - 101708 - -
- Product: - - -  
- - - Component: - - - -  
- - Status: - - ASSIGNED
- - Resolution: - - -
- - Assigned To: - - Gentoo net-im Herd <net-im@gentoo.org>
- - 		- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Hardware: - - -  
- OS: - - -  
- Version: - - -  
- Priority: - - -  
- Severity: - - -  
- 		- - - - - - - - - - - - - - - - - - - -
- Reporter: - - Stian B. Barmen <stian@barmen.nu> -
- Add CC: - -
- CC: - - -
- Remove selected CCs -
-
- -
- - - - - - - - - - - - - - - - - - - - - - - - -
- - URL: - - - -
- Summary: - - -
- Status Whiteboard: - - -
- - Keywords: - - - -
- 		- - - - -
-
-
- - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
AttachmentTypeCreatedSizeActions
- initial 0.8.9 ebuild. - text/plain - 2005-08-08 00:20 PST3.19 KB - Edit -
- initd startup script - text/plain - 2005-08-08 00:21 PST1.34 KB - Edit -
- inetrc, make ejabberd use srv records - text/plain - 2005-08-08 00:23 PST36 bytes - Edit -
- confd - text/plain - 2005-08-08 00:24 PST777 bytes - Edit -
- ejabberd (ejabberd internal start script) - text/plain - 2005-08-08 00:25 PST355 bytes - Edit -
- ejabberdctl - text/plain - 2005-08-08 00:26 PST199 bytes - Edit -
- New ebuild, include dep for sandbox 1.2.12 - text/plain - 2005-09-05 07:11 PST3.21 KB - Edit -
- ebuild with some additions - text/plain - 2005-09-11 07:21 PST3.89 KB - Edit -
- new ejabberd startup script - text/plain - 2005-09-11 07:22 PST348 bytes - Edit -
- new ejabberdctl script - text/plain - 2005-09-11 07:23 PST172 bytes - Edit -
- worked ebiuld - application/octet-stream - 2005-11-22 06:05 PST3.68 KB - Edit -
- ejabberd 1.0.0 ebuild - text/plain - 2005-12-16 02:17 PST3.89 KB - Edit -
- ejabberd-1.0.0.ebuild alt - text/plain - 2005-12-22 00:00 PST3.14 KB - Edit -
- ejabberd-1.0.0.ebuild (jabber-base compliant) - text/plain - 2006-01-18 21:16 PST3.59 KB - Edit -
- files/ejabberd-1.0.0.initd (jabber-base compliant) - text/plain - 2006-01-18 21:17 PST1.23 KB - Edit -
- ejabberd-1.0.0.ebuild - jabber-base compliant rev 2 - text/plain - 2006-02-24 07:03 PST4.87 KB - Edit -
- files\ejabberd-1.0.0.confd - text/plain - 2006-02-24 07:03 PST777 bytes - Edit -
- net-im/ejabberd - revision 3, with muc_log and stats patches - text/plain - 2006-02-28 02:32 PST5.38 KB - Edit -
- files/ejabberd_cfg.patch - - patch - 2006-02-28 02:34 PST1.46 KB - Edit - | Diff -
- files/ejabberd_web_admin.erl.statsdx.patch - - patch - 2006-02-28 02:35 PST9.07 KB - Edit - | Diff -
- files/muc_log_1.0.0_eightrev.patch - - patch - 2006-02-28 02:36 PST22.45 KB - Edit - | Diff -
- files\mod_statsdx.erl - text/plain - 2006-02-28 02:37 PST22.58 KB - Edit -
- files/mod_stats2file.erl - text/plain - 2006-02-28 02:37 PST9.97 KB - Edit -
- ejabberd-1.0.0-r1.ebuild - text/plain - 2006-03-05 14:07 PST3.22 KB - Edit -
- ejabberd-1.0.0-r1.confd - text/plain - 2006-03-05 14:07 PST671 bytes - Edit -
- ejabberd-1.0.0-r1.initd - text/plain - 2006-03-05 14:08 PST1.23 KB - Edit -
- dev-erl/pgsql-cvs-9999 - text/plain - 2006-03-06 09:15 PST1.04 KB - Edit -
- Create a New Attachment (proposed patch, testcase, etc.) - - View All -
-
- - - - - - - - - - - - - - -
Bug 101708 depends on:98452 - - - - Show - dependency tree - -
- Show - dependency graph -
Bug 101708 blocks:104779 - - -
- - - - -
- Additional Comments: (this is where you put 'emerge --info') -
- - - -
- -
- -
- - -
- - - - - - - - -
- - - - -
- - - -
- - - -
- - - -

- - - View Bug Activity -   |   - Format For Printing -   |   - Clone This Bug - - - - -

- - - -
-
- - - - - -
- Description:   - - Opened: 2005-08-08 00:18 PST -
- - - -
This is the ebuild for the latest version of ejabberd. It is based on
-Karl-Johan
-Karlssons ebuild, and har just been modified slightly. 
-
-The problem with this ebuild (or rather ejabberds installer) is that during the
-make of the binaries the installer goes out and installs files outside of the
-sandbox (erlang files) and this causes an access_wr error when emerging. 
-
-I have not found a way to circumvent this problem other than emerging without
-the sandbox. So if you are going to test this ebuild (I use it on my server, no
-problem) then you will have to install with "FEATURES="-sandbox" emerge
-ejabberd". 
-
-If anyone can modifiy the script so that this works I would be really happy! :)
-
-(also I still use the initd and confd from the 0.7.5 
-
-Reproducible: Always
-Steps to Reproduce:
-1.
-2.
-3.
-
-
-
-
- - ------- Comment - #1 From - Stian B. Barmen - 2005-08-08 00:20 PST - - - ------- - - - - -
Created an attachment (id=65393) [edit]
-initial 0.8.9 ebuild.
-
-Alert: Will not work in sandbox, emerge with:
-
-FEATURES="-sandbox" emerge ejabberd
-
-
-
- - ------- Comment - #2 From - Stian B. Barmen - 2005-08-08 00:21 PST - - - ------- - - - - -
Created an attachment (id=65394) [edit]
-initd startup script
-
-
-
-
- - ------- Comment - #3 From - Stian B. Barmen - 2005-08-08 00:23 PST - - - ------- - - - - -
Created an attachment (id=65395) [edit]
-inetrc, make ejabberd use srv records
-
-
-
-
- - ------- Comment - #4 From - Stian B. Barmen - 2005-08-08 00:24 PST - - - ------- - - - - -
Created an attachment (id=65396) [edit]
-confd
-
-
-
-
- - ------- Comment - #5 From - Stian B. Barmen - 2005-08-08 00:25 PST - - - ------- - - - - -
Created an attachment (id=65397) [edit]
-ejabberd (ejabberd internal start script)
-
-
-
-
- - ------- Comment - #6 From - Stian B. Barmen - 2005-08-08 00:26 PST - - - ------- - - - - -
Created an attachment (id=65398) [edit]
-ejabberdctl 
-
-
-
-
- - ------- Comment - #7 From - Albert Holm - 2005-09-05 06:32 PST - - - ------- - - - - -
Sandbox problems seem to be fixed from sandbox 1.2.12 and on. See also bug 
-#101433.
-
-
-
- - ------- Comment - #8 From - Stian B. Barmen - 2005-09-05 07:11 PST - - - ------- - - - - -
Created an attachment (id=67683) [edit]
-New ebuild, include dep for sandbox 1.2.12
-
-I added the check for sandbox 1.2.12 or later into the script so the sandbox
-problem goes away. 
-
-Could someone please submit to portage since this works now?
-
-
-
- - ------- Comment - #9 From - Ian P. Christian - 2005-09-07 03:04 PST - - - ------- - - - - -
trying to test this I have the following issue: 
- 
-# pwd 
-/usr/local/portage/net-im/ejabberd 
-# ebuild ejabberd-0.9.8.ebuild digest 
-!!! aux_get(): ebuild path for 'net-im/ejabberd-0.9.8' not specified: 
-!!!            None 
-!!! aux_get(): ebuild path for 'net-im/ejabberd-0.9.8' not specified: 
-!!!            None 
-doebuild(): aux_get() error reading net-im/ejabberd-0.9.8; aborting. 
- 
-Kind Regards
-
-
-
- - ------- Comment - #10 From - Stian B. Barmen - 2005-09-07 03:54 PST - - - ------- - - - - -
I cannot reproduce this error here. Does it download the tar file to
-/usr/portage/distfiles? Any other error? 
-
-What did you do exactly when you copied it in?
-
-
-
- - ------- Comment - #11 From - Ian P. Christian - 2005-09-07 05:15 PST - - - ------- - - - - -
user error. please ignore. Sorry about that. 
-make.conf has PORT_OVERLAY rather then PORTDIR_OVERLAY, and hence this ebuild 
-wasn't within a portage ebuild tree thing.
-
-
-
- - ------- Comment - #12 From - Stian B. Barmen - 2005-09-07 05:56 PST - - - ------- - - - - -
Good :)
-
-Please report if further tweaks are needed to get it to run. I know that some
-has had problems if they start ejabberd without using the init script cuz then
-the spool dir gets owned by root. :)
-
-
-
- - ------- Comment - #13 From - Albert Holm - 2005-09-11 04:30 PST - - - ------- - - - - -
I tried this but I just can't seem to get it to start with the init script. If
-I 
-manually run /usr/bin/ejabberd with sudo and a modified /usr/bin/ejabberd to
-set 
-directory and HOME it does work but I would like to run it with the init script 
-instead.
-
-I have the same problem on two different computers, with all available versions 
-of ejabberd. Both computers use ~x86 as their KEYWORD. The initscript writes [ 
-!! ] every time it is executed. If I downgrade baselayout to 1.11.13-r1 it 
-writes [ OK ] instead, but that is a lie as ejabberd dies right after start. 
-
-I manually verify the owner and group of files when changning between the 
-different versions and it seems to be ok.
-
-I did not have this problem when I installed 0.7.5 the first time and then I 
-upgraded baselayout (and most other packages) to new versions for a few months 
-without restarting the computer or ejabberd.
-
-
-
-
- - ------- Comment - #14 From - Aleksander Kamil Modzelewski - 2005-09-11 04:50 PST - - - ------- - - - - -
(In reply to comment #13)
-I can confirm that, on baselayout 1.12.0_pre8-r2
-And that's definetly not local to you. I have exaclty the same problem.
-Permissions are all OK. I tried to find the cause but failed miserably. After
-starting /etc/init.t/ejabberd the only ejabberd-related thing running is epmd.
-
-But it get's weirdier.
-
-After second init.d run (without killing the epmd), the ejabberd started. I
-telneted on 5223, wrote nothing, then killed telnet. ejabberd died. Next time I
-tested ejabberd by connecting with Gossip, then reconnected - it works just fine ;)
-
-Still, the init.d script claims that it has failed, probably the return codes
-from erl are unusual in some way.
-
-
-
-
- - ------- Comment - #15 From - Max Loparyev - 2005-09-11 07:21 PST - - - ------- - - - - -
Created an attachment (id=68175) [edit]
-ebuild with some additions
-
-I've added odbc flag to support ejabberd odbc backend, changed install part so
-now it creates dirs at emerge, and places ejabberd binary files to erlangs lib
-dir i.e. in /usr/lib/erlang/lib/<module-version>.
-So -pa option in ejabberd and ejabberdctl can be removed
-
-
-
- - ------- Comment - #16 From - Max Loparyev - 2005-09-11 07:22 PST - - - ------- - - - - -
Created an attachment (id=68176) [edit]
-new ejabberd startup script
-
-
-
-
- - ------- Comment - #17 From - Max Loparyev - 2005-09-11 07:23 PST - - - ------- - - - - -
Created an attachment (id=68177) [edit]
-new ejabberdctl script
-
-
-
-
- - ------- Comment - #18 From - Albert Holm - 2005-09-13 15:30 PST - - - ------- - - - - -
I have reinstalled the box I used as jabber server. The earlier configuration 
-was using keyword ~x86 but this time I go with "x86". I installed the ejabberd 
-from this bug with the modification to /usr/bin/ejabberd to use cd $HOME before 
-erl. After some database problems that made me purge all files and have ejabberd 
-recreate them I managed to get the init script to work. That is, it both says it 
-starts the daemon and it does work. Well, atleast so far. 
-
-Baselayout is 1.11.13-r1 but what I believe is more important is that I now use 
-erlang-1.20.0. Alot of my configuration has changed from the non-working setup 
-to this, but if I had a spare euro cent I would bet it on erlang. 1.20.0 is 
-marked ~x86 and 1.20.5 is stable, but I did not want Tk (because it has X 
-dependencies) so I went with the earlier version anyway. I believe I had 1.20.0 
-when I first installed ejabberd-0.7.5 and as far as I remember that worked out 
-of the box.
-
-I don't know if I want to ask anyone to downgrade erlang to an earlier version, 
-but if you have problems and have 1.12.5 it might be worth a shot to test it.
-
-
-
- - ------- Comment - #19 From - Kirill A. Korinsky - 2005-11-20 15:47 PST - - - ------- - - - - -
Why this ebuild don't add on official tree?..
-
-
-
-
- - ------- Comment - #20 From - Albert Holm - 2005-11-20 16:00 PST - - - ------- - - - - -
I guess this is not official because it depends on bug #98452. Also the next 
-release (currently beta upstreams) will depend on that bug. Converting this to 
-follow jabber-base now would probably speed up the addition of next upstream 
-version to Portage.
-
-
-
- - ------- Comment - #21 From - Stian B. Barmen - 2005-11-21 00:09 PST - - - ------- - - - - -
Also there will be a new version coming out very soon, I think when this comes
-out I will do some more testing and we will see if it will be accepted. I myself
-have no access to submit to portage, but maybe someone can take the job?
-
-
-
- - ------- Comment - #22 From - Kirill A. Korinsky - 2005-11-22 06:05 PST - - - ------- - - - - -
Created an attachment (id=73368) [edit]
-worked ebiuld
-
-It's worked ebuild. Im yusing it's on my jabber server :)
-
-
-
- - ------- Comment - #23 From - Albert Holm - 2005-11-22 06:41 PST - - - ------- - - - - -
That ebuild seems very similar to the 0.7.5 ebuild and to the 0.9.8 ebuild 
-posted previous but it does not solve the problem with jabber-base compliance.
-
-
-
- - ------- Comment - #24 From - Trejkaz Xaoza - 2005-12-14 15:49 PST - - - ------- - - - - -
Seems like version 1.0.0 is out now.
-
-
-
-
- - ------- Comment - #25 From - Stian B. Barmen - 2005-12-16 02:17 PST - - - ------- - - - - -
Created an attachment (id=74865) [edit]
-ejabberd 1.0.0 ebuild
-
-I just renamed Max's ebuild to the new version and upgraded my two servers
-without a hitch. Please report back about new installs if these works as they
-should. 
-
-Can anyone point out more informasjon about the jabber-base compliance? I have
-not found any specifications about this. If there is such a thing I would like
-to customize the ebuild to support these specifications.
-
-
-
- - ------- Comment - #26 From - Gustavo Felisberto - 2005-12-16 03:23 PST - - - ------- - - - - -
Info on jabber-base is in the ebuild:
-/usr/portage/net-im/jabber-base/jabber-base-0.00.ebuild
-
-Untill this is fixed to be jabber-base friendly i cannot add it to portage.
-
-
-
- - ------- Comment - #27 From - Stian B. Barmen - 2005-12-16 03:29 PST - - - ------- - - - - -
(In reply to comment #26)
-> Info on jabber-base is in the ebuild:
-> /usr/portage/net-im/jabber-base/jabber-base-0.00.ebuild
-> 
-> Untill this is fixed to be jabber-base friendly i cannot add it to portage.
-
-You want the ejabberd ebuild to depend on jabber-base and then use the dirs and
-settings that you specify in the ebuild. Do I understand you correctly then?
-
-
-
- - ------- Comment - #28 From - Albert Holm - 2005-12-16 03:42 PST - - - ------- - - - - -
You can also read bug #98542 for information about the directories. The pymsn-t 
-ebuild in portage depends on jabber-base, but the earlier versions did not. You 
-can compare the ebuilds in bug #88597 to the one in portage for some hints on 
-what has to change atleast.
-
-Also, can someone please update the summary to reflect the most recent version?
-
-
-
-
- - ------- Comment - #29 From - Stian B. Barmen - 2005-12-16 05:50 PST - - - ------- - - - - -
I will try to look at this over the weekend, if anyone want to contribute feel
-free :)
-
-
-
- - ------- Comment - #30 From - Max Loparyev - 2005-12-18 06:04 PST - - - ------- - - - - -
i disagree to share access rights with other jabber components to be secure as
-we can. There is authentication mechanizm between jabber components and no need
-to share access rights to filesystem. And why the hell I need rw access to my
-configs, even from the jabber server/component account?
-
-
-
-
- - ------- Comment - #31 From - Max Loparyev - 2005-12-18 06:05 PST - - - ------- - - - - -
previous post was about jabber-base if it is not clear
-
-
-
-
- - ------- Comment - #32 From - Asser - 2005-12-22 00:00 PST - - - ------- - - - - -
Created an attachment (id=75310) [edit]
-ejabberd-1.0.0.ebuild alt
-
-This is my ebuild for ejabberd. Some use-flags was added and changed (a-la
-jabberd). May be usefull for you.
-
-
-
-
- - ------- Comment - #33 From - Octavio Ruiz (Ta^3) - 2006-01-18 21:16 PST - - - ------- - - - - -
Created an attachment (id=77499) [edit]
-ejabberd-1.0.0.ebuild (jabber-base compliant)
-
-
-
-
- - ------- Comment - #34 From - Octavio Ruiz (Ta^3) - 2006-01-18 21:17 PST - - - ------- - - - - -
Created an attachment (id=77500) [edit]
-files/ejabberd-1.0.0.initd (jabber-base compliant)
-
-
-
-
- - ------- Comment - #35 From - Stian B. Barmen - 2006-01-30 04:49 PST - - - ------- - - - - -
The new ebuild works fine (thanks Octavio!), not very happy about the spool and
-run dir. Fine that they are accessed by the jabber user, but should they not
-continue to be named ejabberd? If we have the same spool dir there will be
-problems if we unmerge ejabberd and then emerge jabberd later, right? 
-
-Anyone agree or disagree? 
-
-For info, if you would like to test the newest ebuilds and have used the old
-ones before then you have to rename all dirs referenced in /usr/bin/ejabberd
-from ejabberd to jabber, and change owner of the files to jabber:jabber. Can be
-a little tricky but it seems to work fine here at least. 
-
-
-
-
- - ------- Comment - #36 From - Octavio Ruiz (Ta^3) - 2006-01-30 10:09 PST - - - ------- - - - - -
(In reply to comment #35)
-> The new ebuild works fine (thanks Octavio!)
-
-:)
-
-> not very happy about the spool and run dir. Fine that they are accessed by the jabber user, but should they not continue to be named ejabberd?
-
-What about /var/run/jabber/ejabberd (${JABBER_RUN}/${PN}) and
-/var/spooljabber/ejabberd (${JABBER_SPOOL}/${PN})
-
-
-> If we have the same spool dir there will be
-> problems if we unmerge ejabberd and then emerge jabberd later, right? 
-
-HUmmm.. yes, i think problems will happend. So, tell me where do you think is
-the best place?
-
-> 
-> Anyone agree or disagree? 
-
-I can't, it's my first time using jabber daemonds but I have experience making
-ebuilds, so discuss it here and I will do my best until some dev take it.
-
-> For info, if you would like to test the newest ebuilds and have used the old
-> ones before then you have to rename all dirs referenced in /usr/bin/ejabberd
-> from ejabberd to jabber, and change owner of the files to jabber:jabber. Can be a little tricky but it seems to work fine here at least. 
-
-Thanks for pointing that (I did'nt thinked about it) but, well that 'trick' is
-just for alpha-beta-bugzilla-ebuild-testers, in the tree we just have the 0.7.5
-so we need to think just in the migration from that to ejabberd-1.0.0.
-
-How is done? I don't know. At least to put someinfo about that in pkg_postinst.
-
-
-
-
- - ------- Comment - #37 From - Stian B. Barmen - 2006-02-01 06:25 PST - - - ------- - - - - -
> > not very happy about the spool and run dir. Fine that they are accessed by the jabber user, but should they not continue to be named ejabberd?
-> 
-> What about /var/run/jabber/ejabberd (${JABBER_RUN}/${PN}) and
-> /var/spooljabber/ejabberd (${JABBER_SPOOL}/${PN})
-
-I do not think that we should use PN cause the spool and run dirs will be
-automatically updated on upgrades. I think we should use
-/var/run/jabber/ejabberd and /var/spool/jabber/ejabberd. Alternatively leave
-them at /var/run/ejabberd and /var/spoool/ejabberd like before. 
-
-> Thanks for pointing that (I did'nt thinked about it) but, well that 'trick' is
-> just for alpha-beta-bugzilla-ebuild-testers, in the tree we just have the 0.7.5
-> so we need to think just in the migration from that to ejabberd-1.0.0.
-
-Yes, the migration from 0.7.5 to 1.0.0 will be a tricy one aswell. I might be
-able to reproduce this if you want help in making the upgrade happen. We will
-need to move the spool and run (.erlang.cookie is important!) to the new dirs,
-change the permissions. Then it ought to work. 
-
-Maybe if we decide on a dir, and start to make an upgrade for 0.7.5 I can set
-up a test server and the we try to upgrade it. 
-
-Do you want me to patch your script or do you want to rewrite it youreself?
-
-
-
-
- - ------- Comment - #38 From - Jay Knight - 2006-02-14 15:37 PST - - - ------- - - - - -
What's the hold up on this bug?  Are we waiting for some sort of finalization
-on jabber-base?  Or is it just a matter of fixing some problems with the
-attached ebuild?  If the latter... what still needs to be fixed?
-
-
-
-
- - ------- Comment - #39 From - Stian B. Barmen - 2006-02-24 07:03 PST - - - ------- - - - - -
Created an attachment (id=80601) [edit]
-ejabberd-1.0.0.ebuild - jabber-base compliant rev 2
-
-This is my edit of Octavios ebuild that was great! I just changed the spool so
-this will not conflict later (to /var/spool/jabber/ejabberd), I changed the ssl
-pem generating to only occur if the is no pem from before, also I added some
-warnings about use flags, and I also inserted a warning if it seemed the user
-was upgrading from 0.7.5 or one of the bugzilla ebuilds. 
-
-This should now be working 100%, from what I can gather. It starts and works
-fine here on my test machine, it is jabber-base compliant and should now be
-added to portage under ~ is my reccomendation, pretty please?
-
-The initd is not changed so use Octavios, but I added a confd, just renamed cus
-the old one was fine. 
-
-
-
-
- - ------- Comment - #40 From - Stian B. Barmen - 2006-02-24 07:03 PST - - - ------- - - - - -
Created an attachment (id=80602) [edit]
-files\ejabberd-1.0.0.confd
-
-
-
-
- - ------- Comment - #41 From - Lukáš Polívka - 2006-02-27 21:54 PST - - - ------- - - - - -
I'm really looking forward to this "bug" being resolved. ^_^
-
-In the meanwhile -- what about incorporating the patch for MUC HTML logging
-(assign some local USE flag for this?)
-
-http://www.jabber.ru/bugzilla/show_bug.cgi?id=10
-
-Just an idea. Keep the hard work. ^_^
-
-
-
-
- - ------- Comment - #42 From - Stian B. Barmen - 2006-02-28 00:31 PST - - - ------- - - - - -
Yes this is a great idea, the patch does not apply cleanly for 1.0.0 now so I
-will talk to badlop to get this sorted and then I will add this. But I think
-maybe the patch should just be default, and not with use flag. Also I think we
-should add mod_statsdx, I use this myselft and it is very stable, and maybe we
-should add a use flag for the mysql patch. 
-
-I will talk to badlop and see, if this ebuild comes into portage in the
-meantime we can make a new -r1 or something. :)
-
-
-
-
- - ------- Comment - #43 From - Stian B. Barmen - 2006-02-28 02:32 PST - - - ------- - - - - -
Created an attachment (id=80892) [edit]
-net-im/ejabberd - revision 3, with muc_log and stats patches
-
-New ebuild which adds support for mod_muc_log, statsdx and stats2file. The
-cfg.example has also been updated with this information. 
-
-
-
-
- - ------- Comment - #44 From - Stian B. Barmen - 2006-02-28 02:34 PST - - - ------- - - - - -
Created an attachment (id=80893) [edit]
-files/ejabberd_cfg.patch
-
-This patch updates the ejabberd.cfg.example with information for MUC logging,
-statdx and stats2file. 
-
-
-
-
- - ------- Comment - #45 From - Stian B. Barmen - 2006-02-28 02:35 PST - - - ------- - - - - -
Created an attachment (id=80894) [edit]
-files/ejabberd_web_admin.erl.statsdx.patch
-
-This patch adds the statsdx menu to the web admin of ejabberd. 
-
-
-
-
- - ------- Comment - #46 From - Stian B. Barmen - 2006-02-28 02:36 PST - - - ------- - - - - -
Created an attachment (id=80895) [edit]
-files/muc_log_1.0.0_eightrev.patch
-
-This patch adds logging capabilities to the muc module.
-
-
-
-
- - ------- Comment - #47 From - Stian B. Barmen - 2006-02-28 02:37 PST - - - ------- - - - - -
Created an attachment (id=80896) [edit]
-files\mod_statsdx.erl
-
-This is the statsdx module.
-
-
-
-
- - ------- Comment - #48 From - Stian B. Barmen - 2006-02-28 02:37 PST - - - ------- - - - - -
Created an attachment (id=80897) [edit]
-files/mod_stats2file.erl
-
-This is the stats2file module.
-
-
-
-
- - ------- Comment - #49 From - Gustavo Felisberto - 2006-02-28 07:19 PST - - - ------- - - - - -
This bug is a real mess with files and files. Can please someone send me a mail
-with a tar.gz of the portage files that they know work and maybe some fast
-notes on setting up ejabberd so that i can test/commit this?
-
-
-
-
- - ------- Comment - #50 From - Stian B. Barmen - 2006-02-28 08:53 PST - - - ------- - - - - -
Here is a tar.bz2 for all to test! :)
-
-http://www.jabber.no/ejabberd-1.0.0.tar.bz2
-
-
-
-
- - ------- Comment - #51 From - Nguyen Thai Ngoc Duy - 2006-03-03 02:47 PST - - - ------- - - - - -
 * Service ejabberd starting                                              [ !!
-]
- * ERROR:  ejabberd failed to start
-
-It actually started but reported as fail
-
-
-
-
- - ------- Comment - #52 From - Stian B. Barmen - 2006-03-03 03:38 PST - - - ------- - - - - -
You must provide more information. 
-
-The thing with ejabberd is that it uses ejabberdctl to start and stop en
-server. You need to try and kill the process and then start it again. The
-problem I often see is that you try and start the server as root and then the
-.erlang.cookie gets r for only root, and then you get a bad error from
-ejabberdctl. chowning jabber:jabber /var/run/jabber/.erlang.cookie is a good
-thing to try. 
-
-Please also try to run the start script from /usr/bin/ejabberd to see what the
-output is. Also do this as the jabber user. 
-
-
-
-
- - ------- Comment - #53 From - Nguyen Thai Ngoc Duy - 2006-03-04 03:06 PST - - - ------- - - - - -
I did once made the mistake causing erlang.cookie owned by root. But at the
-moment erlang.cookie is owned by jabber:jabber (600).
-What do you want me to run from jabber account? Running ejabberd without any
-parameter gives me an erlang shell. Don't know what to do from that.
-
-
-
-
- - ------- Comment - #54 From - Nguyen Thai Ngoc Duy - 2006-03-04 03:07 PST - - - ------- - - - - -
By the way, i had installed jabberd-2.0 before installing ejabberd, so
-jabber:jabber was created by jabberd not ejabberd
-
-
-
-
- - ------- Comment - #55 From - Lars Strojny - 2006-03-05 14:07 PST - - - ------- - - - - -
Created an attachment (id=81458) [edit]
-ejabberd-1.0.0-r1.ebuild
-
-Added fix for SRV-DNS (zeroconf), some QA issues, etc.
-
-
-
-
- - ------- Comment - #56 From - Lars Strojny - 2006-03-05 14:07 PST - - - ------- - - - - -
Created an attachment (id=81459) [edit]
-ejabberd-1.0.0-r1.confd
-
-
-
-
- - ------- Comment - #57 From - Lars Strojny - 2006-03-05 14:08 PST - - - ------- - - - - -
Created an attachment (id=81460) [edit]
-ejabberd-1.0.0-r1.initd
-
-
-
-
- - ------- Comment - #58 From - Lars Strojny - 2006-03-05 14:13 PST - - - ------- - - - - -
Sorry for the noise, saw to late, that there are sensible ebuilds now.
-
-
-
-
- - ------- Comment - #59 From - Lukáš Polívka - 2006-03-06 08:45 PST - - - ------- - - - - -
PostgreSQL support is currently BROKEN with the way the ebuild is now.
-
-We need postgresql module from http://jungerl.sf.net
-
-Unfortunately, it's apparently CVS-only code.
-
-See http://www.pgmillard.com/blog/?p=74
-
-
-
-
- - ------- Comment - #60 From - Octavio Ruiz (Ta^3) - 2006-03-06 09:15 PST - - - ------- - - - - -
Created an attachment (id=81533) [edit]
-dev-erl/pgsql-cvs-9999
-
-
-
-
- - ------- Comment - #61 From - Bertrand Jacquin - 2006-04-20 15:07 PST - - - ------- - - - - -
Doesn't one of ebuild above work somewhere ?
-
-I tried all and all build 50 % of things :
- - No ejabberd, ejabberdctl installed
- - No init.d/conf.d files
-
-Very strange.
-
-
- -
- -
-First - Last - Prev - Next -    - No search results available - -     Search page -     Enter new bug - -
- +# Work around a bug in /sbin/runscript.sh - it won't run our custom +# restart() unless it finds these two strings in the file. +# svc_start svc_stop +restart() { + ebegin "Restarting eJabberd" + if [ -z "$EJABBERD_NODE" ]; + then + EJABBERD_NODE="ejabberd@`hostname -s`" + fi + /usr/bin/ejabberdctl $EJABBERD_NODE restart + eend $? +} - - \ No newline at end of file +reload() { + ebegin "Reloading eJabberd" + if [ -z "$EJABBERD_NODE" ]; + then + EJABBERD_NODE="ejabberd@`hostname -s`" + fi + /usr/bin/ejabberdctl $EJABBERD_NODE reopen-log + eend $? +} -- cgit v1.2.3