[freeradius 3.0.14] Issue on close and reopen file at reload

[Geaaru]

Yeah thanks. Now from log I see correctly info about Reloaded module
but so, the right question is why is not called hup automatically from
main  SIGHUP ?

FWIS there is a check about type of the module and linelog correctly
has flag RLM_TYPE_HUP_SAFE so I don't understand why I don't find log
about reloading of the module?

Could be related with a problem to handle multiple module linelog
(needed in my case to log same packets with different line log)?

radmin> show module list
auth_log (detail)
reply_log (detail)
pre_proxy_log (detail)
post_proxy_log (detail)
reject (always)
fail (always)
ok (always)
handled (always)
invalid (always)
userlock (always)
notfound (always)
noop (always)
updated (always)
cache_auth (cache)
cache_ip (cache)
chap
detail
delayed.acct1 (detail)
dynamic_clients
expr
log_accounting (linelog)
log_auth2proxy (linelog)
log_auth_resp (linelog)
log_block_resp (linelog)
log_acct_resp_from_proxy (linelog)
pap
radutmp
IPASS (realm)
suffix (realm)
realmpercent (realm)
ntdomain (realm)
replicate
sql (sql)
sql_cache (sql)
sqlippool
sradutmp (radutmp)
utf8
radmin>

Obviously, in my case is needed radmin -e "hup log_accounting" , etc.

Thanks again for this clarification.

G.

On Thu, 2017-08-24 at 06:57 -0400, Alan DeKok wrote:
> On Aug 24, 2017, at 4:56 AM, Arran Cudbard-Bell <a.cudbardb at freeradiu
> s.org> wrote:
> > 
> > Maybe that’s a bit of a major change for v3.0.x. What’s the core
> > team’s opinion an implementing an extra method for modules to deal
> > with SIGHUP?
> 
>   It's already there.
> 
> $ radmin -e "hup linelog"
> 
>   Alan DeKok.
>