Hi all,
Mike has identified the problem as a NUL character being added to the password
coming from the SQLServer. The problem appears to be occuring in the DBD:Sybase
module. I modified some example ct-lib code that came with FreeTDS and it pulled
strings from the SQLServer fine - no NUL
Hi Chris,
On Feb 24, 4:24pm, Chris Hanes wrote:
Subject: Re: (RADIATOR) DBD::Sybase/FreeTDS/MSSQL7 Problems
Hi all,
Mike has identified the problem as a NUL character being added to the
password
coming from the SQLServer. The problem appears to be occuring in the
DBD:Sybase
module. I
Hello Rakesh,
Radiator 2.15 supports a new check items Cleint-Id and NasType. Using them, you
could set up Handlers for each type of NAS, or for each individual Client.
Handlers also allow you to specifiy the Realm as a regexp.
Therefore, you could set up a handler something like:
Handler
Hi guys,
If I have the same AcctLogFileName for two different handlers, will the
writing of the detail file be messed up by the two handlers writing to it at
the same time?
Andrew
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe
Hi Andrew,
On Feb 25, 11:42am, Andrew Pollock wrote:
Subject: (RADIATOR) Same AcctLogFileName for two handlers
Hi guys,
If I have the same AcctLogFileName for two different handlers, will the
writing of the detail file be messed up by the two handlers writing to it at
the same time?
No.
I am looking for some advice - my goal is to have users with separate
permissions for different clients based upon client name. I am using AuthBy PAM
(kerberos) for password authentication, and requiring AuthBy File for specifying
which users are valid and defining their return attributes.
I
