More strangeness.
We setup a new 6.03 test server. It works dandy.
However, if we start it with:
cd /opt/lotus/data; server
The server starts, etc.
If we “close” the SSH/telnet session to the server, the HTTP task becomes unresponsive.
I realize we can use a startup script, but why does this happen? We are having “other” similar issues with HTTP and perhaps its related.
Subject: HTTP dies when exit console…
Yes, you’ll probably find the whole server has stopped. The session that started all those tasks has closed - this is UNIX thing, not a Domino thing. When you load the server, make sure to pass it off to the OS as a background task (can’t quite remember how to do this, but your Solaris admin should).
Subject: RE: HTTP dies when exit console…
Thanks…
yeah, it’s server&
the ‘&’ starts it as a backround task
however, other server products don’t seem to ‘die’ when the console is closed… they keep running, just with no output to a console window.
anyway, thanks.
my biggest problem no is figuring out why the server dies when its cluster sister shuts down… i thought this might be related, but apparently its not.
thanks!
D