3.0.12 ignoring HUP (No files changed), albeit changes in passwd-file?
Hello, I´m running 3.0.12 and use the passwd-module of 3.0.13 (because of "notfound") After changes in the passwd-file, the server receives a HUP. This worked in 2.0.2 3.0.12 will give me
Info: HUP - No files changed. Ignoring
I can confirm, that the passwd-file has changed, since the server has started. What am I doing wrong? (Found some entries in the mailing list, that this was a problem in older versions but should have been fixed since 3.0.10?) Is it better to change to 3.0.13 completely? Is it stable? Thank you very much.
On Feb 13, 2017, at 9:15 AM, macservo via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I´m running 3.0.12 and use the passwd-module of 3.0.13 (because of "notfound") After changes in the passwd-file, the server receives a HUP. This worked in 2.0.2
3.0.12 will give me
Info: HUP - No files changed. Ignoring
I can confirm, that the passwd-file has changed, since the server has started.
The server checks only the main configuration files, not ones which have been read by the modules.
What am I doing wrong?
In v3, you can use radmin: radmin> hup passwd to HUP *just* the password module. This is the recommended approach. Alan DeKok.
Hi,
I´m running 3.0.12 and use the passwd-module of 3.0.13 (because of "notfound") After changes in the passwd-file, the server receives a HUP.
dont do that - just compile 3.0.12 with the code changes that were put into the 3.0.x HEAD to fix your issue
Is it better to change to 3.0.13 completely? Is it stable?
well, 3.0.13 is what will come form HEAD next. unless people are trying it, we wont know of any other issues. use HEAD, if all okay, then the next release will be okay. people think that theres some huge farm of servers with every conceivable configuration on dealing with millions of auths to ensure that every scenario and issue can be seen. there isnt and they wont ;-) alan
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
macservo