(RADIATOR) kill -1 vs. kill / restart

[Mariano Absatz]

Hi,

I once commented on this and I recall that at some point Hugh said this was 
solved.

The point is, I make certain changes to the configuration file, I send the 
process a HUP signal (kill -1) and the changes are NOT taken into account.

If I stop the process (kill -15) and then start Radiator again, then changes 
take effect.

FTR: The problem was inside an <AuthBy SQL> and I had a syntax error in a 
query sent to Oracle: a missing "AND" in the WHERE clause, which gave me a 
"ORA-00933: SQL command not properly ended (DBD ERROR: 
OCIStmtExecute/Describe)" error.

I'm using Radiator 2.18.4, on a Sun Netra with Solaris 8 and Perl 5.6.1.

As a sidecomment:

When Radiator starts, if you take a look at a Trace 4, it does a couple of 
things before actually entering the main radius loop.

Apparently, it sends the message saying "Server started" when it is entering 
the main loop.

It would be nice to have (at least at Trace 4) a "Server starting" right at 
the beginning. The first time I saw messages between the "Server stopping" or 
"Server restarting" and the "Server started" message, I didn't know if they 
where coming from the server shutting down or coming back up again. If you 
use your brain (as I often do not) you can actually see that the messages in 
the log are from the server starting up and not from the one that's going 
down, anyway, I think a 
&log($LOG_DEBUG, "Server starting... $ident"); 
in radiusd right after the &NGetOpt or that neighborhood would be 
informative...



Thu Nov  8 11:07:44 2001: INFO: Server started: Radiator 2.18.4 on radius1--
Mariano Absatz
El Baby
----------------------------------------------------------
CCITT - Can't Conceive Intelligent Thoughts Today 


===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.