On Sun, 2003-01-26 at 10:40, Tracy S. Ruggles wrote:
> My webware servers were dying, too, without a mention of it in the
> error logs, and only when I wasn't watching. It turned out that I had
> a stack size limit, too, of 24K and my server was slowly growing in
> size (I have a bug somewhere
My webware servers were dying, too, without a mention of it in the
error logs, and only when I wasn't watching. It turned out that I had
a stack size limit, too, of 24K and my server was slowly growing in
size (I have a bug somewhere that I haven't found yet). And, if my
pages ever raised an
Sent: Saturday, January 25, 2003 8:13 PM
To: Webware discuss
Subject: Re: [Webware-discuss] Keeping Webware running.
They might have a daemon that kills long-running processes too. Might
want to check with them on that.
On Sat, 2003-01-25 at 18:29, Ben Logan wrote:
> Thanks to everyone
They might have a daemon that kills long-running processes too. Might
want to check with them on that.
On Sat, 2003-01-25 at 18:29, Ben Logan wrote:
> Thanks to everyone for your responses. I do have cron access on the
> server, so I'll give that method a shot. I hadn't considered that
> appser
Thanks to everyone for your responses. I do have cron access on the
server, so I'll give that method a shot. I hadn't considered that
appserver might be dying because they've limited my cpu time, so I ran
'ulimit -a' on the server, and my cpu time is unlimited. However, the
stack size is limited
On Sat, 2003-01-25 at 08:30, Hancock, David (DHANCOCK) wrote:
> I hope someone chimes in with a better idea, because my ideas involve some
> work...
Sadly there's not a much better solution included with Webware or that
I've used, though someone else may have a solution.
> If you have sufficient
Ben Logan wrote:
> Hi, everyone.
>
> I am running Webware on a shared Linux web server (I don't have root
> priveleges), and am wondering what I can do to make certain that it
> stays running. I've been starting the appserver by logging in via
> ssh, and running 'nohup Appserver &', and that work
I hope someone chimes in with a better idea, because my ideas involve some
work...
If you have sufficient rights to have cron jobs, consider writing a little
monitor that runs via cron. It just needs to look for the appserver
process, or retrieve a page using wget or lynx -dump, and if it can't g
