Add an explicit message that the shutdown sequence is complete.
This is necessary because during a Windows OS shutdown, the service
is frequently killed prior to the memory mapped file is fully released.
Reviewed-on: http://gerrit.openafs.org/5053
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Reviewed-by: Jeffrey Altman <jaltman@openafs.org>
Tested-by: Jeffrey Altman <jaltman@openafs.org>
(cherry picked from
e91f16ebb704a431f9731bb39bf9b5621b7f6ad0)
Change-Id: I80685fae2b581171c580b039ae029ca69bea467c
Reviewed-on: http://gerrit.openafs.org/5132
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@openafs.org>
Tested-by: Jeffrey Altman <jaltman@openafs.org>
case MSG_SERVICE_INCORRECT_VERSIONS:
case MSG_SERVICE_RUNNING:
case MSG_SERVICE_STOPPING:
+ case MSG_SERVICE_STOPPED:
case MSG_SERVICE_ERROR_STOP:
case MSG_CRYPT_OFF:
case MSG_CRYPT_ON:
Busy call channel when communicating with server %1, retrying ...
.
+MessageId=
+Severity=Informational
+Facility=System
+SymbolicName=MSG_SERVICE_STOPPED
+Language=English
+OpenAFS Shutdown Complete.
+.
+
;#endif /* __AFSD_EVENTMESSAGES_H_ 1 */
/* Remove the ExceptionFilter */
SetUnhandledExceptionFilter(NULL);
+ LogEvent(EVENTLOG_INFORMATION_TYPE, MSG_SERVICE_STOPPED);
+
if (bRunningAsService) {
ServiceStatus.dwCurrentState = SERVICE_STOPPED;
ServiceStatus.dwWin32ExitCode = GlobalStatus ? ERROR_EXCEPTION_IN_SERVICE : NO_ERROR;