The following 'old-fashioned way' won't get you the convenience of using 'chkconfig', 'service', etc. but it does work.
Just add these two lines to the end of /etc/rc.d/rc.local: echo "Starting Jabber..." /path/to/jabberd & The above is quite optimistic - it doesn't check to see whether the server crashed - 'cos if it did jabber won't start until you delete the jabber.pid file. So I wouldn't do it this way on a production server, but it is a quick fix. HTH, -mike On Wed, 2002-03-27 at 05:44, Michel Oosterbeek wrote: > Hi All, > > I'm using Jabber 1.4.1 with Red Hat 7.2 and I have been trying to get > Jabberd to fire up on startup, but so far my attempts were unsuccessful. > Recently I read some messages of other people here, who were having the same > problem. Some scripts were offered, and I decided to give them a try, but > something strange is happening. So if the writer of these scrips is reading > this, please give me some advice? > ... > Now, on startup, I see the script is called: "Starting jabberd... [OK]", but > when I check it, there's nothing running at all. Though when I try to run > the script myself it works fine. So why won't it do that on startup? > > Thanks, > > Michel > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
