CreateHardLink Event

Fires when the OS wants to create a new hard link to an existing file.

Syntax

// CBFSCreateHardLinkEventArgs carries the CBFS CreateHardLink event's parameters.
type CBFSCreateHardLinkEventArgs struct {...}

func (args *CBFSCreateHardLinkEventArgs) FileName() string
func (args *CBFSCreateHardLinkEventArgs) LinkName() string
func (args *CBFSCreateHardLinkEventArgs) HandleInfo() int64
func (args *CBFSCreateHardLinkEventArgs) FileContext() int64
func (args *CBFSCreateHardLinkEventArgs) SetFileContext(value int64)
func (args *CBFSCreateHardLinkEventArgs) HandleContext() int64
func (args *CBFSCreateHardLinkEventArgs) SetHandleContext(value int64)
func (args *CBFSCreateHardLinkEventArgs) ResultCode() int32
func (args *CBFSCreateHardLinkEventArgs) SetResultCode(value int32)

// CBFSCreateHardLinkEvent defines the signature of the CBFS CreateHardLink event's handler function.
type CBFSCreateHardLinkEvent func(sender *CBFS, args *CBFSCreateHardLinkEventArgs)

func (obj *CBFS) GetOnCreateHardLinkHandler() CBFSCreateHardLinkEvent
func (obj *CBFS) SetOnCreateHardLinkHandler(handlerFunc CBFSCreateHardLinkEvent)

Remarks

This event fires when the OS wants to create a new hard link that points to the existing file specified by FileName. The LinkName parameter specifies the absolute path (including filename) of the link to be created.

This event only needs to be handled if the UseHardLinks property is enabled. To handle this event properly, applications should perform any actions needed to create an additional hard link to the specified file in their backend storage.

Please refer to the Hard Links topic for more information.

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 and HandleContext parameters are placeholders for application-defined data associated with the file and specific handle, 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.