See my rather long-winded post:
http://www.mail-archive.com/jboss-user%40lists.sourceforge.net/msg07745.html
Start order is critical. This is set by the S/K code numbers chosen for
use with Debian's "update-rc.d" or Red Hat's "chkconfig." I cannot speak
to what works or does not work on a Red Hat system because we are using
Debian, but David Ward's excellent work is referenced by my message and
you should be able to figure out what to do between us. (If "/etc/rc.d"
exists, I assume you must be on Red Hat.)
If you are connecting to a back-end database, then you must make sure in
your startup configuration that you wait until that back-end is up and
running before you start jBoss. You can do quite a lot of tricks in a
Debian startup script that you cannot do in a Red Hat startup script, and
Debian provides some handy tools to do those tricks, so you may find
yourself writing a lot more shell code on Red Hat.
-- Mike
On 2001-06-26 at 18:57 -0700, Richard Bottoms wrote:
> Anybody running JBoss at startup on their Linux server?
>
> I've tried getting it to go from an /etc/rc.d/rc3.d link to an init.d file.
> I can start the server if I do it manually, but it doesn't work during the
> startup process.
>
> r.b.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
