I am working with coova-chilli 1.4 and I am using radius in order to provide chilli confinguration.
The problem I am facing is linked to coovachilli restart.
When I restart chilli and the configuration from radius is not changed chilli restarts without problems.
But when I change options from radius-side (also a single parameter), chilli is not properly restarted, but it is blocked at:
Starting chilli: Hangup
File conf has the new parameters, but chilli is stopped (if I want chilli in running status I have to restart it again).
Looking at the code, in functions.in I found that the blocking command is:
killall -HUP chilli 2>/dev/null >/dev/null
Indeed it looks like that covachilli is not able to manage the hangup signal HUP and the process is only killed and not restarted.
I am working with coova-chilli 1.4 and I am using radius in order to provide chilli confinguration. The problem I am facing is linked to coovachilli restart. When I restart chilli and the configuration from radius is not changed chilli restarts without problems. But when I change options from radius-side (also a single parameter), chilli is not properly restarted, but it is blocked at:
Starting chilli: Hangup
File conf has the new parameters, but chilli is stopped (if I want chilli in running status I have to restart it again). Looking at the code, in functions.in I found that the blocking command is:killall -HUP chilli 2>/dev/null >/dev/null
Indeed it looks like that covachilli is not able to manage the hangup signal HUP and the process is only killed and not restarted.