Oliver Zimmermann <[EMAIL PROTECTED]> wrote: > > The only thing radzap needs from the configuration files is the > > location of the radutmp file, and that can easily be specified on the > > command line of radzap. > > No, radzap from 0.7 had no directory-parameters:
Umm... I know that. It had the directory hard-coded in it. > And in radzap from 1.0.0 one can specify the general raddb dir: Because radzap reads radiusd.conf. > But that's all not the point. The point is, radzap from 1.0.0 does not work, > due to some socket related problems when a radiusd is running on the machine > (as Luiz Gustavo wrote). Yes, I know. The reason there are socket issues is that the "read radiusd.conf" code is there for radiusd, not for radzap. radzap should probably NOT be reading radiusd.conf, for a whole number of reasons. > And so did the previous versions i know (except 0.7), which makes me > wonder, that only a few people use radzap really. But to kill lost > sessions, radzap is really essential for us and the problem in the > C-code is documented in the beginning of thread. I understand. The longer term solution is to fix radzap so it takes the path to the radutmp file as a parameter, and calls radclient to send the packets. That way there's less code, and it doesn't need to read radiusd.conf. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
