EnumerateHardLinks Event

Fires when the OS needs to enumerate a file's hard links.

Syntax

Remarks

This event fires when the OS needs to enumerate the hard links of the file specified by FileName (which will have been opened via OpenFile).

This event only needs to be handled if the UseHardLinks property is enabled. To handle this event properly, applications must return information about each of the file's hard links. Note that a file's "primary" name (i.e., the one contained in FileName) is itself one of the hard links that must be reported; please refer to the Hard Links topic for more information.

For each hard link, set LinkFound to true and supply the hard link's information using the following parameters:

  • LinkName: Set to the name of the hard link (not including its path).
    • The name must be copied to LinkName; set lenLinkName to the length of the copied string (measured in char/wchar_t, not including terminating nulls).
    • The length of the returned name must not exceed the value of the MaxFileNameLength property.
  • ParentId: Set to the unique Id of the directory the hard link resides in (this Id should not change over time). Always use 0x7FFFFFFFFFFFFFFF if the hard link resides in the root directory (\).

If there are no more hard links present, set LinkFound to false and leave the above parameters unchanged. When the OS is finished with the hard links enumeration, the CloseHardLinksEnumeration event will fire.

The HandleInfo parameter carries a handle to an object with information about the file handle. While within the event handler, it can be used to call any of the following methods: GetHandleCreatorProcessId, GetHandleCreatorProcessName, GetHandleCreatorThreadId, or GetHandleCreatorToken.

The FileContext, HandleContext, and EnumerationContext parameters are placeholders for application-defined data associated with the file, specific handle, and enumeration; respectively. Please refer to the Contexts topic for more information.

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 (e.g., a resource isn't available, security checks failed, etc.), set it to a non-zero value to report an appropriate error. Please refer to the Error Reporting and Handling topic for more information.

 
 
Copyright (c) 2020 Callback Technologies, Inc. - All rights reserved.
CBFS Connect 2020 C++ Edition - Version 20.0 [Build 7545]