Read the original more closely -- I specifically said 'not necessarily a
UI.' Apache does have a minimal scriptable management piece. It is called
apachectl.
Those signal hooks are great. We've been waiting for them since 1.0.
> Eric Hancock wrote:
>>
>> Right, but any product you roll out to a production environment needs some
>> kind of management interface. Not necessarily a UI, but hooks to get
>> information at runtime, and to shut down / take a server offline.
>>
>> I could help with this if people think it would be useful.
>>
>> E -
>
> I might agree we need a UI for some things, but Apache web server runs
> 60% of the web servers out there and you just kill that process. Many
> other UNIX services function this way as well. I might even agree that
> shutdown hooks would be useful, but I don't think "production
> environment" has anything to do with this. ;)
>
> On a somewhat related note, one of the nicest things I like in JDK 1.3
> is the ability to add shutdown hooks so even if someone hits Ctrl-C or
> does kill in UNIX, you can still fire some Java code to run before the
> JVM exits.
>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/>
> Problems?: [EMAIL PROTECTED]
>
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
