There is a way to do it with IIS. You need to configure the
application to run under the IWAM rather than IUSR account
but telling it to run as a separate process. If it crashes
it will not take down the rest of the server.
You can use the MetaBase editor (downloadable from Microsoft's
web site... do a search for "MetaEdit" in the knowledge base)
to configure the number of times it will be restarted in the
AppOopRecoverLimit key when it crashes (default is 5...
set it to something much higher if you'd like).
That said, take a closer look at your scripts. I find scripts
which use GD or which use DBI with a large LongRealLen value
are more crash prone. Also, scripts which use DBI and do not
properly finish statement handles are also crash prone,
especially if the SQL query sorts large amounts of data.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|