Re: [RADIATOR] SIGHUP restart and AuthByRADSEC opens an additional socket

2013-07-14 Thread Heikki Vatiainen
On 07/10/2013 12:50 PM, Karl Gaissmaier wrote: a SIGHUP to a running radiator (Version 4.11) opens an additional socket for AuthByRADSEC: Fixed in the latest patches. Thanks for reporting this, Heikki -- Heikki Vatiainen h...@open.com.au Radiator: the most portable, flexible and

Re: [RADIATOR] SIGHUP restart and AuthByRADSEC opens an additional socket

2013-07-12 Thread Heikki Vatiainen
On 07/10/2013 12:50 PM, Karl Gaissmaier wrote: a SIGHUP to a running radiator (Version 4.11) opens an additional socket for AuthByRADSEC: Hello Charly, it should not be doing this and it's a general problem, not related to your setup. We have a fix for this and currently checking if there are

Re: [RADIATOR] SIGHUP restart and AuthByRADSEC opens an additional socket

2013-07-11 Thread Karl Gaissmaier
Hi, didn't get any response for this request: Am 10.07.2013 11:50, schrieb Karl Gaissmaier: Hi Radiator team, a SIGHUP to a running radiator (Version 4.11) opens an additional socket for AuthByRADSEC: before SIGHUP mizar:.../~# netstat -f inet -P tcp -n | grep 193.*2083 134.60.Y.X.45917

[RADIATOR] SIGHUP restart and AuthByRADSEC opens an additional socket

2013-07-10 Thread Karl Gaissmaier
Hi Radiator team, a SIGHUP to a running radiator (Version 4.11) opens an additional socket for AuthByRADSEC: before SIGHUP mizar:.../~# netstat -f inet -P tcp -n | grep 193.*2083 134.60.Y.X.45917 193.174.Y.X.2083 64128 0 128872 0 ESTABLISHED after SIGHUP mizar:.../~# netstat