Re: [Help-gnu-radius] multiple radius servers feeding in to one postgres db

[Andrew Kohlsmith]

> Not quite so. Never copy radstat. First, it is not needed for the
> utilities and secondly it is mmapped to the memory when radiusd is
> running. Replacing it will have disastrous effects. Copying radutmp
> and radwtmp will allow radping, radwho and radlast to work. Before
> copying radutmp, apply exlusive write lock on it, so it won't disturb
> the operation of the daemon. When the file is copied, remove the lock.
> You can use radlock/rad_unlock from radlib/util.c to do that.

Ok.  So this can be done one of two ways:

1. cron script to create radutmp and append to radwtmp
Advantages: don't need to do anything to the radius utility programs, don't 
need to link libpostgres, etc.
Disadvantages: your data is only as recent as your last pull, and high update 
rate causes excessive network usage

2. edit the utility programs to contact the database directly instead of look 
at radutmp/radwtmp
Advantages: network traffic only when you use the utilities, 
'up-to-the-second' data, radutmp/radwtmp can eventually be removed or used as 
a cache if network is down
Disadvantages: excessive network traffic if the utilities are run frequently, 
more work to be done on the utility programs, util programs require the 
database libraries, no data cacheing

Sound about right?

Regards,
Andrew