[JDEV] Probs w/ Jabberd 1.4.1 and Scripts

[Matthew Miller]

Sorry for not responding sooner.  For some reason, work always seems to get
in the way... (-:

Anyways, somehow the problem solved itself.  I don't know what the deal is,
though.  I tried (from the script) to run jabberd in debug (-D), and it ran
fine.  When I removed the -D flag, it seems to still work correctly.

It appears that jabberd wanted to hang onto a tty, but now it doesn't.  I
haven't had the time to dive into the server code yet, so I can't give a
better explanation at this time.

Besides, it has come to my attention that it's probably better to run
jabberd using "daemontools" (http://cr.yp.to/daemontools.html).  That's
going to be my next attempt.

Sorry to bother you guys, but thanks for the help.

______________
|\/| /\ |  |


-----Original Message-----
From: Thomas Muldowney [mailto:temas at box5.net]
Sent: Tuesday, May 29, 2001 11:12 AM
To: jdev at jabber.org
Subject: Re: [JDEV] Probs w/ Jabberd 1.4.1 and Scripts


Got any debug output for us?

--temas

On Tue, May 29, 2001 at 08:52:42AM -0700, Matthew Miller wrote:
> Hello all,
> 
> I am having some problems with jabberd (version 1.4.1).  Specifically, I
> cannot (for the life of me) get it to continue executing from within a
> script.  I will execute (from CLI):
> jabberd -h localhost -H /usr/jabber/ -c /usr/jabber/jabber.xml &
> 
> And run just fine.  But if I put this line into a script, it fails.  I
went
> through the FAQ's, and found that note about the previous versions needing
a
> connected TTY in order to stay running, but this is (supposed to be) fixed
> in 1.4.1...
> 
> If anyone can give me a clue here, it'd be great.  The server platform
> (currently) is a K6-II (300 MHz) w/ 64 MB RAM and a 30 GB HDD, running
> Redhat 7.1 (linux kernel 2.4.2-2).
> 
> Thanks,
> 
> ____________
> |\/| /\  |    |
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev