Hello Dave -
On Wednesday 13 June 2001 06:08, Kitabjian, Dave wrote:
> We want to add some "Accounting" records of our own to log, for example,
> when and why users are rejected access. Because we already have a
> sophisticated system in place for collecting accounting data, parsing it,
> and making it available to our TSR's via VB, we want to use the same
> channel to collecting this new data.
>
> Using <AuthLog FILE> and a custom FailureFormat including %r, %0 and %1,
> this works very nicely :) The question is...
>
> Is it safe to write to the same file as AcctLogFileName? I guess another
> way of asking is, is the AuthLog FILE write operation atomic?
>
You are really asking two different questions. In answer to the first
question above, yes a single Radiator process opens, writes, and closes every
file it uses for every operation. Hence it is safe to rename, move, write to
from different clauses, etc.
> The reason I'm concerned is because now, for the first time, I'll have two
> processes accessing that file at once; and since our Authentication and
> Accounting are handled by separate Radiators, and the AuthLog is used by
> Authentication and the AcctLogFileName is used by Accounting, corruption
> could occur.
>
In answer to this second question, no Radiator does no file locking, so
having two processes writing to the same file could certainly cause problems.
In answer to your implied question, you should either use different files, or
you should use <AuthLog SQL> instead.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
