ClearBox Server™ v1.2 Developer's Guide


When server extension calls this method and passes it an array of RADIUS attributes found in the RADIUS Accounting-Request packet (although this type of packets is not restricted), then server logs these attributes to the accounting logfile.

This method differs from LogPacket in the way that server extension is responsible for creating and managing the file passed to this method, while LogPacket uses log files automatically managed by the server.

Server extension may call SetLoggingOptionsEx before calling this method to set extra logging parameters, such as autoFlush and logInterim. Other parameters are ignored.

HRESULT LogPacketEx(
	[in] unsigned long attributesNum,
	[in] RADIUS_ATTRIBUTE* inpAttributes,
	[in] long fileHandle);


[in] Number of elements in the array pointed by inpAttributes. Should not be 0.
[in] Array of RADIUS attributes elements that server should log as a separate log unit. Generally, these attributes are those passed to server extension's IRADIUSAccounting::ProcessAccounting implementation as inpAttributes parameter. Should not be NULL.
[in] Server extension should cast this parameter as HANDLE of the file were accounting data is logged. This must be valid handle of opened file with write access.

Return Values

This method may return E_INVALIDARG if attributesNum=0, inpAttributes=NULL.

Thread Safety

This method can be called from any thread.

Memory Management

Server extension should allocate and free memory for inpAttributes parameter. If server extension uses inpAttributes parameter passed to IRADIUSAccounting::ProcessAccounting implementation, then this memory is managed by the server.



See Also

ILivingstonAccounting, Server services, SetLoggingOptionsEx, LogPacket

© 2001-2003 XPerience Technologies.

Created by chm2web html help conversion utility.