In article <007301c1321a$c34349f0$0401a8c0@upk>,
Andrew Melnikov <[EMAIL PROTECTED]> wrote:
>I think that my problem is related to checkrad/checkrad.pl. The script uses
>portslave-dependent things. Now it doesn't work as expected because
>portslave is significally changed. So checkrad.pl definitely needs patching.
>
>First, my portslave is located at the same host with radiusd so really I
>don't need to run fingerd, local finger without hostname commandline
>parameter is enough.
Ah. That might be where your problem lies. The local 'finger' program
doesn't connect to the finger port on the local machine to get it's
info - it figures it all out by itself. A finger @host connects to
a remote server (which may be 'localhost') and prints out the output
it gets. That might be very very different, and _is_ with portslave.
Remember you need to install ctlportslave as fingerd and active
it on your machine to get this to work.
>Today I wanted to continue tracking this problem but found that now finger
>doesn't show portslave users at all. It shows only users locally logged in.
>So my patch have already become obsolete.
Makes sense with all the mixing up of local and remote fingering ..
>I think we should found a better solution than parsing output of finger or
>some other program like w/who/radwho.
Parsing the output of radwho is nonsense. Read README.simul to
see why.
>I say "we" because I post this message to both freeradius and portslave mail
>lists.
I read this through a news gateway, so the reply won't go to
the portslave mailinglist
Mike.
--
"Answering above the the original message is called top posting. Sometimes
also called the Jeopardy style. Usenet is Q & A not A & Q." -- Bob Gootee
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
