Hi guys, I currently have Radiator setup using Auth::Emerald to authenticate against a MS-SQL server. Radiator is running on a Linux box and I'm using DBD::Sybase and the free Sybase drivers. If the MS-SQL server goes away (say, for example, we unplug the machine from the network) how long will it take before Radiator times out and goes on to the next AuthBy? We tested this, and after waiting a couple of minutes without it dropping to the next AuthBy we plugged the server back into the network. Can anybody recommend any timeouts we can tweek? (I'm tempted to modify the code so that if the SQL Server times out Radiator waits 10 minutes before trying it again...) Cheers! Andrew Ruthven Actrix Networks Limited At Work: [EMAIL PROTECTED] At Home: [EMAIL PROTECTED] === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
