[ naviserver-Bugs-1230150 ] ns_log Fatal does not shutdown server

[SourceForge.net <no...@so...>]

Bugs item #1230150, was opened at 2005-06-30 05:42
Message generated for change (Comment added) made by eide
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719006&aid=1230150&group_id=130646

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Tcl-API
Group: Current
Status: Open
Resolution: None
Priority: 5
Submitted By: Bernd Eidenschink (eide)
Assigned to: Nobody/Anonymous (nobody)
Summary: ns_log Fatal does not shutdown server

Initial Comment:
In nsd/log.c one noted side effect of the severity flag "fatal" given to 
ns_log is "WILL CAUSE AOLSERVER TO EXIT!".

AFAIK this does not work, e.g. in command mode NaviServer happily logs 
but does not exit.


----------------------------------------------------------------------

>Comment By: Bernd Eidenschink (eide)
Date: 2005-07-06 10:31

Message:
Logged In: YES 
user_id=197910

>I'm not sure whether it's a good idea for Tcl procs to 
>shutdown the server like that.  It should be prety difficult 
>to get into a 'Fatal' situation with Tcl... 
 
But they can already do 'ns_shutdown (-restart)'. And many, many 
more nasty things ;-) 
IMHO, without a general concept to disarm the developers and their 
scripts, it should  shutdown the server. At least it was always 
documented that way (in the ancient docs) and people believed it :-) 
 
Or we make it a config option: 
ns_param ShutdownAtFatal true ? 
 

----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-07-06 09:26

Message:
Logged In: YES 
user_id=87254

This comment goes with the function Ns_Fatal(), which does
indeed call _exit(1) which should shutdown the server  :-)

I'm not sure whether it's a good idea for Tcl procs to
shutdown the server like that.  It should be prety difficult
to get into a 'Fatal' situation with Tcl...



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719006&aid=1230150&group_id=130646