In the immortal words of John Hebert (john at vedalabs.com):
> There is no inetd config associated with jabberd-1.2 in the default
> install. It could be configured that way, but inetd is normally used for
> services that are brought up when needed. Since you want jabberd to
> always be running, you need to start it at boot time with the rest of
> the init.d scripts. I've configured jabberd to start under
> /etc/rc.d/init.d/jabberd using jtournier's script, but note that this
> method is RedHat specific:
>
> #!/bin/sh
> # Script for starting jabber
> ###
> ### 2000 IDEALX S.A.S.
> ### author jtournier at idealx.com
> ###
As a counter-idea (not that there's anything wrong with the above, but
as usual there's More Than One Way To Do It), I recommend running
jabberd under Dan Bernstein's daemontools package:
http://cr.yp.to/daemontools.html
Specficially, I use svscan and supervise to ensure that jabberd and
all of the transport daemons stay up. I find it especially helpful
with managing the transports, as some of them will happily drop core
or otherwise abort if jabberd is restarted; supervise will just keep
restarting them until jabberd is back.
For a /service/jabberd/run init file, I use:
#!/bin/sh
exec env - PATH="/usr/local/jabber/bin:$PATH" \
setuidgid jabber \
/usr/local/jabber/jabber-1.2/jabberd/jabberd
For /service/aimtrans/run:
exec env - PATH="/usr/local/jabber/bin:$PATH" \
setuidgid jabber \
aimtrans -n aim.example.com \
-e aim.example.com -s yoursecret -p 7009
...adjust paths, ports and secrets to local custom and taste. You get
the idea. :)
-n
------------------------------------------------------------<memory at blank.org>
<sunshine> Dear Future Employer: Who's your daddy? Who's your daddy? I think
we know. Thanks! $100,000 a year, I'll be there on monday, please.
-chelleMarie
<http://www.blank.org/memory/>------------------------------------------------