Search results

Jump to navigation Jump to search
  • Check exit code on forked process
    135 bytes (19 words) - 08:52, 21 December 2011
  • foreach signal {SIGHUP TERM EXIT} { ns_atexit heard_signal EXIT
    3 KB (362 words) - 19:32, 7 February 2009
  • ...ipt and optional arg are concatenated together and added to the list of at-exit callbacks. The scripts are executed in the global scope in LIFO (last in,
    601 bytes (90 words) - 19:32, 7 February 2009
  • exit 1 exit 0
    2 KB (264 words) - 15:02, 30 July 2007
  • *exit -- Exit the control port.
    3 KB (471 words) - 16:50, 5 January 2012
  • ;[[Conf/Parameters/checkexitcode|checkexitcode]] :Check exit code on forked process
    2 KB (206 words) - 20:47, 21 December 2011
  • ...ns_critsec, except that later threads do not wait for the first thread to exit the script?
    3 KB (368 words) - 14:44, 27 June 2006
  • ...The default is 100 milliseconds which should be ample time for a graceful exit unless the process is hung executing a very long, misbehaving script, resul ...communicate with the proxy process due to a timeout or unexpected process exit are also communicated back to the parent interpreter as Tcl exceptions. To
    9 KB (1,398 words) - 19:03, 7 February 2009
  • ...a list of all registered startup, pre-startup, shutdown, server shutdown, exit, and SIGHUP signal procs (e.g. scripts registered for SIGHUP with ns_atsign ::{540 {read exit} nscp {127.0.0.1 9999}}
    6 KB (920 words) - 18:47, 12 October 2009
  • Patch to NsHandleSignals to actually exit on Linux if a SIGSEGV is received.
    4 KB (661 words) - 13:17, 24 March 2006
  • ns_param checkexitcode false ;# Check exit code on forked process
    25 KB (3,070 words) - 10:08, 26 December 2011