[JDEV] Re:One week of running jabberd 1.4

james rogers buckrogers1965 at go.com
Mon Feb 12 11:20:28 CST 2001

>> Message: 3
>> Date: Fri, 9 Feb 2001 19:14:02 -0600
>> From: Thomas Muldowney <temas at box5.net>
>> To: jdev at jabber.org
>> Subject: Re: [JDEV] One week of running jabberd 1.4
>> Reply after each section of comments...
>> Have you tried changing the <ip /> section in your jabber.xml? I use
>> <ip port=3D'5225' /> for a lot of my personal testing, works great, still d=
>> oes with final.

  Of course I tried changing the ip section of my configuration file, the pth
module doesn't work, because it is hard coded to the jabber ports.  Look at my
original posting to see the lines that contain the 5222 and 5269 ports.

>> I am the maintainer of the AIM Transport and I battled this for 3 hours and yes
>> it is a known problem =3D) I'll have a fix put together soon for it. In the
>> meantime you can compile it by going into the src directory and running the
>> compilation by hand, including all the .c files as well as those in the libfaim
>> subdirectory. I'm not going to support this method (read: don't ask me how),
>> so unless you understand how to use the compiler fully I would suggest against
>> trying.

I tried to compile it by hand and it blows up at the linking stage with the error
I gave.

>> Compilation in some cases can be a bear, and we're trying to cope with this
>> We're working on a tool called jbox. It will know how to compile, installand
>> configure different jabber packages. Watch for it soon.

Actually I finally used the absolute path to the jabberd directory in the yahoo
./configure set and it worked. Now my only problem is that the documentation hasn't
been updated to the 1.4 version. :)

>> Have you played with the jabber.xml settings for logging? They are decent and
>> provide a whole lot of options, although it sounds like you may need to write
>> a quick module to do some of the updates you are looking for.

Jabberd has logging?  Will each modules give a status every X number of minutes
telling me how many messages and the number of bytes processed since the last status

>> I'm sorry but I disagree, the jabber server is distributed as a system designed
>> to compile itself, not any random thing that people stick in it. If you are
>> developing a new component or module for the jabber server it is not difficult
>> to add it in to the build system, or have your own external build system. Again,
>> jbox will help solve some of these problems.

I am vaguely offended by your comment.  I am not sticking random things in the
directory, I am placing an authentication module that authenticates users against
a global registration system with several million entries using xml over http.  It
will make my life easier to simply place the module into the directory and have it
compile rather than have to edit two different make files each in a different directory
everytime I upgrade to a new project.  It is certainly not difficult, but it is somewhat
annoying, especially when it is trivial to fix the problem.

And what happens when I have 50 extra modules that different people have written that
I want to include, certainly you aren't even recommending that I hand edit two different
make files with 50 different entries every time jabber.org comes out with a new release?

>> It sounds like you want to be using xdb. Look at the xdb_get and xdb_set
>> functions.

No, if you add a new section to the jabber config file the system won't start because it
complains about the configuration file being wrong.  I can modify the configo function to
handle this, but I find doing this to be kinda annoying.  Ideally it would simply parse
unknown sections for retrieval by another module later.

>> It would seem that a lot of your problems come due to poor documentation.
>> That's always been a hard issue for us, as many of the developers do some of the
>> documentation, but we find ourselves spending most of our time on the core
>> system. As soon as the new website backend goes live (one of my current top
>> priorities) I plan to spend significant time doing documentation. Expect
>> status reports to the list.
>> --temas

Thanks, good documentation would be appreciated.

GO.com Mail                                    
Get Your Free, Private E-mail at http://mail.go.com

More information about the JDev mailing list