(RADIATOR) Current Logged in Users

[Rolando Riley]

When I say 'fairly accurate' - if your NAS fails to deliver a STOP record to
radiator, the user will not be removed from the online users database.


The above  seems to be very common to happen. That is

1) hanged users which can't auth  because of a Max Sessions reached and no
STOP record sent by the NAS has been taken
2) Sometimes hanged RADIUS. That still happens to us when we change all the
auths to LDAP. And it is due to the same cause in point 1)

My question is:
1) what is the accurate way to use scripts like scripts like
goodies/cleanup.txt or checksessiondb.txt
2) do you know what are the frequent causes that  make NAS don't send the
STOP record ?


  ----- Original Message -----
  From: Shane Malden
  To: radiator at open.com.au
  Sent: Monday, February 11, 2002 2:59 PM
  Subject: (RADIATOR) Current Logged in Users


  Does anyone know any simple way of seeing who is logged on, using the logs
from Radiator? We do receive start and stops from our gear. We are running
ver 2.19 on a NT Server. Any help would be appreciated.

  Regards,
  Shane
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20020211/85776273/attachment.html>