The pidfile mess is mostly my thought. Someone requested the feature last
minute and I put it in =). If you don't want pidfile support though, you
should be able to remove the tag and function correctly. It should be
cleaned up in the future.
--temas
On Wed, Mar 14, 2001 at 05:34:00PM -0600, [EMAIL PROTECTED] wrote:
> I understand that 'jabberd' checks for the existence of the pidfile, and
> refuses to run if it exists. This works fine as long as the previous
> execution of jabberd exited cleanly and removed it's old pidfile.
>
> Was there an intentional design decision made not to read the process ID
> stored in the pidfile, and if that process no longer exists, to overwrite
> the pidfile with the new process ID rather than exit with an error?
>
> I've worked around this by doing basically the same thing in my jabber
> startup script.
>
> Kevin
>
>
> > you can fix this problem by deleting the jabber.pid file created in
> > jabber-1.4 directory.
> >
> > run the server after deleting this file, it'll work fine.
> >
> > I get the following message everytime i try to re-start the server.
> >
> > "A pidfile already exists at the specified location. Check to ensure
> > another cop y of the server is not running, or remove the existing file. "
>
>
> _______________________________________________
> jdev mailing list
> [EMAIL PROTECTED]
> http://mailman.jabber.org/listinfo/jdev
PGP signature
