CBFS Filter 2020 Node.js Edition

Questions / Feedback?

NotifyUnlockAll Event

Fires when all locked byte ranges in a file have been unlocked.

Syntax

cbmonitor.on('NotifyUnlockAll', [callback])

Callback

The 'callback' is called when the 'NotifyUnlockAll' event is emited.

function(e){ }

The argument 'e' has the following properties:

e.fileName
e.status
e.resultCode

Remarks

This event fires when all locked byte ranges in the file specified by FileName have been unlocked.

Applications only need to handle this event if they've added a standard filter rule that includes the FS_NE_LOCK_CONTROL flag.

The Status parameter contains an NT status code that indicates the outcome of the operation; 0 indicates success. To convert this value to a Win32 error code, call the NtStatusToWin32Error method. Please note that this event won't fire for failed requests unless the ProcessFailedRequests property is enabled.

The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason, set it to a non-zero value to report an appropriate error. Note, however, that this event fires after the operation has already completed, so reporting an error won't actually affect the operation itself. Please refer to the Error Reporting and Handling topic for more information.

This event is fired asynchronously; please refer to the Event Types topic for more information.

 
 
Copyright (c) 2021 Callback Technologies, Inc. - All rights reserved.
CBFS Filter 2020 Node.js Edition - Version 20.0 [Build 7917]