Hi Pete -
On Thu, 07 Oct 1999, Pete Black wrote:
> >%_This is good, although we require that at the end of the month all
> existing records that don't have a stop record at the turn of the month
> get truncated at 00:00h the next day.
>
> Would it be possible to have some sort of hook that intercepted the
> incoming acct packet, then check if it's start record is in the previous
> month, create the truncated record, create a new Start record at the
> beginning of the month and then put down the modified Stop record?
>
I'm not sure that you would want to do it that way.
You might do something like this:
<Handler ...>
AcctLogFileName %L/accounting.%m.%Y
AcctLogFileFormat .....
......
</Handler>
This will write to a file called "accounting.10.1999" for the month of October,
then at midnight on the 31st it will roll to "accounting.11.1999". Your
post-processing can then tidy up the loose ends at the beginning and end of the
month.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
