Hmm, good question: [r...@web01 ~]# find /etc -name "*james*" /etc/rc.d/rc6.d/K05james /etc/rc.d/rc5.d/S80james /etc/rc.d/rc3.d/S80james /etc/rc.d/rc2.d/S80james /etc/rc.d/rc4.d/S80james /etc/rc.d/rc1.d/K05james /etc/rc.d/init.d/james /etc/rc.d/rc0.d/K05james
Seems the start scripts are in the right place, correct? =Don On Thu, Jul 16, 2009 at 11:28 PM, Eric MacAdie <e...@macadie.net> wrote: > What do you get when you run find /etc -name "*james*"? > > Eric MacAdie > > > Don Smith wrote: > >> I realize this might be more of a linux question, but my problem is only >> with James, so I'm wondering if there is something James specific I'm >> missing. I've added James to initd via the chkconfig --add james command. >> >> [r...@web01 ~]# chkconfig --list | grep james >> james 0:off 1:off 2:on 3:on 4:on 5:on 6:off >> >> I did the virtually the same thing with Jetty, a web app server: >> >> [r...@web01 ~]# chkconfig --list | grep jetty >> jetty 0:off 1:off 2:off 3:on 4:off 5:off 6:off >> >> >> The difference is that on boot Jetty is started up, but James isn't. And >> there is nothing in the James or Phoenix logs indicating there was even an >> attempt to start up. Has anyone else had success getting James to start on >> boot on Linux, like Centos5? Did you do anything different than what I've >> done? >> >> Thanks, >> >> Don >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > >
