gdm and radius accounting

[Alan DeKok]

sub wrote:
> I tried putting the line in the session section and it really works.
> the server received an accounting request of "start" at the user login
> and an accounting-request "stop" at logout.

  So it is receiving accounting packets.  That's how accounting works.

> it's ok but what I really need is accounting because I can't wait for
> the user action to save informations in the db.

  This sentence makes no sense.

  You want... some kind of accounting which is independent of user login
and logout?  What kind of magic accounting is that?

> In the page of the project (http://www.freeradius.org/pam_radius_auth/) I see
> "This is the PAM to RADIUS authentication module. It allows any
> PAM-capable machine to become a RADIUS client for authentication and
> accounting requests."
> so I think that the pam_radius_auth module shoud support acconting :-p

  It does.  You verified that it does.  It sends accounting stop/start
messages.  That is what accounting *means*.

> furthermore at this page we've an example of the pam configuration file.
> http://www.freeradius.org/pam_radius_auth/USAGE
> 
> some help?

  Perhaps you could explain what you mean by "what I really need is
accounting"... and why the existing, standards-compliant accounting in
the module isn't sufficient for your needs.

  Or maybe you're thinking of something else other than accounting?

  Alan DeKok.