Nick Freeman wrote:
However it never deletes or changes the detail.work file - so when I
send a second accounting packet, it will go into the detail file without
a problem (and will be the only packet in the file) but detail.work
seems to be locked with the first packet. No matter how many
Hi,
The below was added and recompiled with the same result - the virtual server
writing to the database stops at Ready to process requests.
Thanks,
Nick
--
It looks like it isn't noticing that it's finished reading the file.
I would suggest going to line 482 of src/main/detail.c, and
Nick Freeman wrote:
Hi,
The below was added and recompiled with the same result - the virtual server
writing to the database stops at Ready to process requests.
Thanks. I'll take a look at adding some more automated tests to check
for this.
Do you have a *minimal* configuration that
Hi - here's the config, it returns this:
+- entering group accounting
rlm_detail: Suppressing writes to detail file as the request was just
read from a detail file.
++[detail_rewrite] returns noop
} # server local_logger
It still stops after the first radclient packet, though. I commented out
I've done some more digging as to why the database only gets one
update..
With no detail or detail.work file, freeradius will wake up every 1
second to check for creation - when it gets updated, it puts it into the
database fine.
However it never deletes or changes the detail.work file - so
5 matches
Mail list logo
