On Mon, Oct 29, 2001 at 12:46:50AM +0000, lance wrote: > On Mon, 29 Oct 2001, Andreas Faust wrote: > > > just set log_dir to syslog and it should work .. > > I tried that and it terminated straight away - I think it objects to > radutmp trying to go to syslog/radutmp or something ?? > > > > > its just a minor bug in freeradius which hasn't been fixed yet. > Are there many others ?? no, just some
> I am planning to use it in a production environment .... I do, as many others. There are no such major bugs that would be reason to change to another radiusd. We tested some radius servers and freeradius was the fastest one so far, so I recommend it actually. If you do very special things, you might encounter some major problems ( not mentioning that these specials would be only possible with hacking in new features into most other radius servers), which are mostly resolved within a couple of days. You should also generate a logdir2 directive, where you want to log radutmp stuff etc. Then change every "logdir"-statement in the radiusd.conf into logdir2 (except the one you changed to syslog, of course) (This is how I got radiusd to log on stderr) .. It should work then... cheers Andreas Faust P.S.: The FAQ is not in sync with the current behaviour in this subject - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
