← Back to branch summary

~ubuntu-branches/ubuntu/jaunty/freeradius/jaunty-updates

« back to all changes in this revision

Viewing changes to raddb/sites-available/copy-acct-to-home-server

  • Committer: Bazaar Package Importer
  • Author(s): Chuck Short
  • Date: 2008-09-22 08:42:02 UTC
  • mfrom: (1.1.12 upstream)
  • Revision ID: james.westby@ubuntu.com-20080922084202-eyjprg3z55481ha5
Tags: 2.1.0+dfsg-0ubuntu1
https://launchpad.net/bugs/261809
* New upstream release.
* Fixes FTBFS issue with new libtool.
* Fixes listen on random port. (LP: #261809)

Show diffs side-by-side

added added

removed removed

Lines of Context:
raddb/sites-available/copy-acct-to-home-server
21
21
#       That way, each server has the same set of information, and
22
22
#       can make the same decision about the user.
23
23
#
24
 
#       $Id: copy-acct-to-home-server,v 1.3 2008/04/26 15:23:43 aland Exp $
 
24
#       $Id$
25
25
#
26
26
######################################################################
27
27
 
29
29
        listen {
30
30
                type = detail
31
31
 
 
32
                ######################################################
 
33
                #
 
34
                #  !!!! WARNING !!!!
 
35
                #
 
36
                #  The detail file reader acts just like a NAS.
 
37
                #
 
38
                #  This means that if accounting fails, the packet
 
39
                #  is re-tried FOREVER.  It is YOUR responsibility
 
40
                #  to write an accounting policy that returns "ok"
 
41
                #  if the packet was processed properly, "fail" on
 
42
                #  a database error, AND "ok" if you want to ignore
 
43
                #  the packet (e.g. no Acct-Status-Type).
 
44
                #
 
45
                #  Neither the detail file write OR the detail file
 
46
                #  reader look at the contents of the packets.  They
 
47
                #  just either dump the packet verbatim to the file,
 
48
                #  or read it verbatim from the file and pass it to
 
49
                #  the server.
 
50
                #
 
51
                ######################################################
 
52
 
 
53
 
32
54
                #  The location where the detail file is located.
33
55
                #  This should be on local disk, and NOT on an NFS
34
56
                #  mounted location!