(RADIATOR) BUG: After SIGHUP radiator doesn't proper reread the config file

1999-04-27 Thread Karl Gaissmaier

Hi,

when I change the config file from
Realm
...
...
\Realm

to

Handler NAS-IP-Address=X.X.X.X
...
...
\Handler

Handler NAS-IP-Address=Y.Y.Y.Y
...
...
\Handler

and send a SIGHUP to the radiator, he is still trying to handle
the requests with the Realm 'Realm=', even if there is no longer
ANY Realm Clause in the config.

See the trace Output after SIGHUP:

ue Apr 27 10:59:01 1999: NOTICE: SIGHUP received: restarting
Tue Apr 27 10:59:01 1999: DEBUG: Reading password file /etc/shadow
Tue Apr 27 10:59:04 1999: DEBUG: Reading group file /etc/group
Tue Apr 27 10:59:04 1999: DEBUG: Reading users file 
/usr/local/radiator/raddb/freeway-users
Tue Apr 27 10:59:04 1999: DEBUG: Reading users file 
/usr/local/radiator/raddb/ulmathome-users
Tue Apr 27 10:59:04 1999: INFO: Server started
Tue Apr 27 10:59:09 1999: DEBUG: Handling request with Handler 'Realm='
   ^
here is the problem, because I have no longer any Realm Clause in
the config file. If I kill the radiator and restart it, radiator
works okay, see the trace output(see SIGTERM in difference to SIGHUP!):

Tue Apr 27 10:59:25 1999: NOTICE: SIGTERM received: stopping
Tue Apr 27 10:59:29 1999: DEBUG: Reading password file /etc/shadow
Tue Apr 27 10:59:32 1999: DEBUG: Reading group file /etc/group
Tue Apr 27 10:59:32 1999: DEBUG: Reading users file 
/usr/local/radiator/raddb/freeway-users
Tue Apr 27 10:59:32 1999: DEBUG: Reading users file 
/usr/local/radiator/raddb/ulmathome-users
Tue Apr 27 10:59:33 1999: INFO: Server started
Tue Apr 27 10:59:33 1999: DEBUG: Check if Handler NAS-IP-Address=X.X.X.X should be 
used to handle this request
Tue Apr 27 10:59:33 1999: DEBUG: Check if Handler NAS-IP-Address=Y.Y.Y.Y should be 
used to handle this request
Tue Apr 27 10:59:33 1999: DEBUG: Handling request with Handler 'NAS-IP-Address=Y.Y.Y.Y'


Version 2.13.1, Patches applied.
OS=Solaris 2.6
Perl-Version: 5.005_03 built for sun4-solaris

regards
Charly
-- 
Karl Gaissmaier  Computing Center,University of Ulm,Germany
Email:[EMAIL PROTECTED]  Network Administration
Tel/Fax: ++49 731 50 22499/22471
pgp-key available: http://www.uni-ulm.de/urz/Netzwerk/uuca/keylist.html

===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



Re: (RADIATOR) BUG: After SIGHUP radiator doesn't proper reread the config file

1999-04-27 Thread Mike McCauley

Hi Karl,

You are tight. We found this problem recently. It is fixed for the next
release. In the meantime, you will need to restart you Radiator if you change
the Realms in your config.

Thanks for reporting it to us.

Cheers.

On Apr 27, 11:17am, Karl Gaissmaier wrote:
 Subject: (RADIATOR) BUG: After SIGHUP radiator doesn't proper reread the c
 Hi,

 when I change the config file from
 Realm
   ...
   ...
 \Realm

 to

 Handler NAS-IP-Address=X.X.X.X
   ...
   ...
 \Handler

 Handler NAS-IP-Address=Y.Y.Y.Y
   ...
   ...
 \Handler

 and send a SIGHUP to the radiator, he is still trying to handle
 the requests with the Realm 'Realm=', even if there is no longer
 ANY Realm Clause in the config.

 See the trace Output after SIGHUP:

 ue Apr 27 10:59:01 1999: NOTICE: SIGHUP received: restarting
 Tue Apr 27 10:59:01 1999: DEBUG: Reading password file /etc/shadow
 Tue Apr 27 10:59:04 1999: DEBUG: Reading group file /etc/group
 Tue Apr 27 10:59:04 1999: DEBUG: Reading users file
/usr/local/radiator/raddb/freeway-users
 Tue Apr 27 10:59:04 1999: DEBUG: Reading users file
/usr/local/radiator/raddb/ulmathome-users
 Tue Apr 27 10:59:04 1999: INFO: Server started
 Tue Apr 27 10:59:09 1999: DEBUG: Handling request with Handler 'Realm='
^
 here is the problem, because I have no longer any Realm Clause in
 the config file. If I kill the radiator and restart it, radiator
 works okay, see the trace output(see SIGTERM in difference to SIGHUP!):

 Tue Apr 27 10:59:25 1999: NOTICE: SIGTERM received: stopping
 Tue Apr 27 10:59:29 1999: DEBUG: Reading password file /etc/shadow
 Tue Apr 27 10:59:32 1999: DEBUG: Reading group file /etc/group
 Tue Apr 27 10:59:32 1999: DEBUG: Reading users file
/usr/local/radiator/raddb/freeway-users
 Tue Apr 27 10:59:32 1999: DEBUG: Reading users file
/usr/local/radiator/raddb/ulmathome-users
 Tue Apr 27 10:59:33 1999: INFO: Server started
 Tue Apr 27 10:59:33 1999: DEBUG: Check if Handler NAS-IP-Address=X.X.X.X
should be used to handle this request
 Tue Apr 27 10:59:33 1999: DEBUG: Check if Handler NAS-IP-Address=Y.Y.Y.Y
should be used to handle this request
 Tue Apr 27 10:59:33 1999: DEBUG: Handling request with Handler
'NAS-IP-Address=Y.Y.Y.Y'


 Version 2.13.1, Patches applied.
 OS=Solaris 2.6
 Perl-Version: 5.005_03 built for sun4-solaris

 regards
   Charly
 --
 Karl Gaissmaier  Computing Center,University of Ulm,Germany
 Email:[EMAIL PROTECTED]  Network Administration
 Tel/Fax: ++49 731 50 22499/22471
 pgp-key available: http://www.uni-ulm.de/urz/Netzwerk/uuca/keylist.html

 ===
 To unsubscribe, email '[EMAIL PROTECTED]' with
 'unsubscribe radiator' in the body of the message.
-- End of excerpt from Karl Gaissmaier



-- 
Mike McCauley   [EMAIL PROTECTED]
Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia   http://www.open.com.au
Phone +61 3 9598-0985   Fax   +61 3 9598-0955

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, external, etc etc on Unix, Win95/8, NT, Rhapsody
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.