Re: rlm_detail and locking

Personally, I would just backport the "fcntl-only" commit - that way you know you're getting fcntl locking:

That looks perfect, thank you. I had another thought: would it be sane to get rlm_detail to write to a named pipe? I guess the problem then is it could block if the listener goes away. You could use a second freeradius instance as file reader / pipe writer. But reading the file directly and using fcntl locking sounds a much better solution anyway. Cheers, Brian.