Hello, Thank you very much. In radzap.c, the main routine calls the read_mainconfig, and this routine exits the program if the port 1812 is not free.
I copied this routine to a new one, called read_mainconfig_zap, and it does not exit the program, so the radzap now zaps the user... But i have tried this in the release 0.9.1, and it seems to me that this old version did not have this bug... The radzap worked well... Luiz Gustavo > "Luiz Gustavo Anflor Pereira" <[EMAIL PROTECTED]> wrote: >> Are radzap and the radiusd server on the same machine? I have this >> situation, and it looks like they are cconcurring for the same port >> (1812). Is that correct? > > It's a bug in radzap. radzap shouldn't read "radiusd.conf", but > should get passed the name of the radutmp file directly. > > Alan DeKok. > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
