CBFS Filter 2020 Python Edition

Questions / Feedback?

on_notify_delete_file Event

Fires when a file or directory has been deleted.

Syntax

class CBMonitorNotifyDeleteFileEventParams(object):
  @property
  def file_name() -> str: ...
  @property
  def result_code() -> int: ...
  @result_code.setter
  def result_code(value) -> None: ...

# In class CBMonitor:
@property
def on_notify_delete_file() -> Callable[[CBMonitorNotifyDeleteFileEventParams], None]: ...
@on_notify_delete_file.setter
def on_notify_delete_file(event_hook: Callable[[CBMonitorNotifyDeleteFileEventParams], None]) -> None: ...

Remarks

This event fires when the file or directory specified by FileName has been deleted. More specifically, this event is queued for delivery after the final IRP_MJ_CLOSE IRP has been processed by the filesystem (i.e., after the last handle to the file or directory is closed and the file or directory is gone).

Note: This event is not fired when a virtual file is deleted; please refer to the Virtual Files topic for more information.

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

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) 2022 Callback Technologies, Inc. - All rights reserved.
CBFS Filter 2020 Python Edition - Version 20.0 [Build 8317]