queue radius message when resource is in use
kabilius at gmail.com
Sat Sep 18 17:20:23 CEST 2010
>> If your program can't wait that long to access the data, use a database.
I think that will solve my problem.
Thank you for the helpful answers.
On Fri, Sep 17, 2010 at 10:50 PM, Alan DeKok <aland at deployingradius.com>wrote:
> kabilius smith wrote:
> > I have configured the FreeRadius server to write to a file c:\test.log,
> > and one of our programs reads contents from c:\ test.log as well.
> > When our program is reading c:\ test.log, we open it with “deny write”
> > permission, so the I saw the error message “Error: rlm_detail: Couldn't
> > open file c:/test.log: Device or resource busy” in Radius.log.
> So... don't do that. Your program is *wrong*. It is breaking the
> RADIUS server.
> > Can FreeRadius be configured to “delay write”? meaning, if it is unable
> > to access c:\test.log, could it queue the message, and write to the file
> > at a later time?
> No. It the responsibility of *your* program to ensure that it doesn't
> break the RADIUS server.
> The "detail" module can be configured to write new detail files every
> hour. If your program can't wait that long to access the data, use a
> > My 2^nd question:
> > When FreeRadius receive a radius message, can it redirect the message to
> > another TCP or UDP link? If it is possible, then we will just setup a
> > TCP or UDP link to listen for the message from the FreeRadius server.
> In some unspecified format.. ?
> The answer is no.
> Alan DeKok.
> List info/subscribe/unsubscribe? See
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Freeradius-Users