API: Shutdown - Revision history

F at 00:07, 27 August 2012

2012-08-27T00:07:10Z

← Older revision		Revision as of 00:07, 27 August 2012
Line 22:		Line 22:

	==Termination==		==Termination==
	:ServerGUI does a clean shutdown on <code>WM_QUIT</code>/<code>WM_CLOSE</code> (<code>SIGTERM</code> on *nix). ServerCLI ~~handles~~ Ctrl+C ~~and~~ Ctrl+Break ~~interrupts~~, but ~~quits abruptly~~ signals.		:ServerGUI does a clean shutdown on <code>WM_QUIT</code>/<code>WM_CLOSE</code> (<code>SIGTERM</code> on *nix). ServerCLI does a clean shutdown on Ctrl+C or Ctrl+Break, but does not handle signals. CLR does not provide a low-level way of handling signals/interrupts, but WinForms applications handle it internally, and call the Form.Closing event. Command-line applications just die.
	:CLR does not provide a low-level way of handling signals/interrupts, but WinForms applications handle it internally, and call the Form.Closing event. Command-line applications just die.

	[[Category:Dev]]		[[Category:Dev]]

F at 23:56, 26 August 2012

2012-08-26T23:56:30Z

← Older revision		Revision as of 23:56, 26 August 2012
Line 18:		Line 18:
	##Save and unload PlayerDB		##Save and unload PlayerDB
	##Save and unload IPBanList		##Save and unload IPBanList
			##Set Environment.ExitCode to the appropriate ShutdownReason code.
	##''Server.ShutdownEnded''		##''Server.ShutdownEnded''

	==Termination==		==Termination==
	:ServerGUI does a clean shutdown on <~~CODE~~>~~TERM~~</~~CODE~~>. ServerCLI ~~does not handle it at all~~.		:ServerGUI does a clean shutdown on <code>WM_QUIT</code>/<code>WM_CLOSE</code> (<code>SIGTERM</code> on *nix). ServerCLI handles Ctrl+C and Ctrl+Break interrupts, but quits abruptly signals.
	:~~<CODE>.NET</CODE>~~ does not provide a low-level way of handling signals/interrupts, but WinForms applications handle it internally, and call the Form.Closing event. Command-line applications just die.		:CLR does not provide a low-level way of handling signals/interrupts, but WinForms applications handle it internally, and call the Form.Closing event. Command-line applications just die.

	[[Category:Dev]]		[[Category:Dev]]

Hellenion: /* Termination */ typo

2012-08-26T18:36:16Z

Termination: typo

← Older revision		Revision as of 18:36, 26 August 2012
Line 21:		Line 21:

	==Termination==		==Termination==
	:ServerGUI does a clean shutdown on <CODE>TERM<CODE>. ServerCLI does not handle it at all.		:ServerGUI does a clean shutdown on <CODE>TERM</CODE>. ServerCLI does not handle it at all.
	:<CODE>.NET</CODE> does not provide a low-level way of handling signals/interrupts, but WinForms applications handle it internally, and call the Form.Closing event. Command-line applications just die.		:<CODE>.NET</CODE> does not provide a low-level way of handling signals/interrupts, but WinForms applications handle it internally, and call the Form.Closing event. Command-line applications just die.

	[[Category:Dev]]		[[Category:Dev]]

Hellenion: Section about program termination.

2012-08-26T18:35:20Z

Section about program termination.

← Older revision		Revision as of 18:35, 26 August 2012
Line 19:		Line 19:
	##Save and unload IPBanList		##Save and unload IPBanList
	##''Server.ShutdownEnded''		##''Server.ShutdownEnded''

			==Termination==
			:ServerGUI does a clean shutdown on <CODE>TERM<CODE>. ServerCLI does not handle it at all.
			:<CODE>.NET</CODE> does not provide a low-level way of handling signals/interrupts, but WinForms applications handle it internally, and call the Form.Closing event. Command-line applications just die.

	[[Category:Dev]]		[[Category:Dev]]

F at 02:04, 12 January 2012

2012-01-12T02:04:39Z

← Older revision		Revision as of 02:04, 12 January 2012
Line 19:		Line 19:
	##Save and unload IPBanList		##Save and unload IPBanList
	##''Server.ShutdownEnded''		##''Server.ShutdownEnded''

			[[Category:Dev]]

F: Created page with "When an fCraft server is being shut down, the following sequence of events takes place: #Server.Shutdown ##Cancels any previous shutdown attempt. ##Verifies ShutdownParams ##Ann..."

2012-01-12T01:51:28Z

Created page with "When an fCraft server is being shut down, the following sequence of events takes place: #Server.Shutdown ##Cancels any previous shutdown attempt. ##Verifies ShutdownParams ##Ann..."

New page

When an fCraft server is being shut down, the following sequence of events takes place:

#Server.Shutdown
##Cancels any previous shutdown attempt.
##Verifies ShutdownParams
##Announces shutdown and starts the countdown.

After the timer elapses, Server.ShutdownNow (internal) is called on a separate thread:

#Server.ShutdownNow
##''Server.ShutdownBegan''
##Scheduler clears the list of tasks, and prevents future tasks from being added. Current task is allowed to finish.
##Stop listening for connections
##Kick all players, allow 1000ms to deliver the kick packet
##Disconnect IRC
##Save and unload all worlds
##Scheduler waits for current task to finish (if it is still running).
##Save and unload PlayerDB
##Save and unload IPBanList
##''Server.ShutdownEnded''