From f51e42f583073bde0bc8131887cb7220636c8855 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Wed, 20 Jul 2011 13:09:05 +1000 Subject: Terminate the log with one last message. Instead of just closing the log when everything is done, put one more message in stating that we're actually terminating. Users or scripts that look at the Xorg.log will then know that a) the server has terminated properly and b) why the server terminated (to some degree, given that most real-world errors will be caused by AbortServer()). Acked-by: Gaetan Nadon Reviewed-by: Daniel Stone Tested-by: Jeremy Huddleston Reviewed-by: Jeremy Huddleston Tested-by: Jon TURNEY Reviewed-by: Jon TURNEY Signed-off-by: Peter Hutterer --- doc/Xserver-spec.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/Xserver-spec.xml b/doc/Xserver-spec.xml index 7d7f9152c..b14e4897e 100644 --- a/doc/Xserver-spec.xml +++ b/doc/Xserver-spec.xml @@ -4680,8 +4680,8 @@ An Example implementation is miPushPixels() in Xserver/mi/mipushpxl.c. Shutdown Procedures
- void AbortDDX() - void ddxGiveUp() + void AbortDDX(enum ExitCode error) + void ddxGiveUp(enum ExitCode error)
Some hardware may require special work to be done before the server exits so that it is not left in an intermediate state. As explained -- cgit v1.2.3