"Rob Hartzenberg (iCabs)" <[EMAIL PROTECTED]> wrote:
> Well, see, I tried and failed. The Group command works fine with the MySQL
> module on some of the other solutions I have setup, but I have not managed
> to get it to work nicely with the system groups.
The Group attribute is intended to be
Hey
>
> Huh? Why not just use the "Group" attribute, which does
> Unix group checking for you?
>
> Alan DeKok.
>
Well, see, I tried and failed. The Group command works fine with the MySQL
module on some of the other solutions I have setup, but I have not managed
to get it to work nicel
"Rob Hartzenberg (iCabs)" <[EMAIL PROTECTED]> wrote:
> To get freeradius to work with the system groups of "users / 100" and "email
> / 200"
> I searched around the new archives until I came up with a solution that uses
> Exec-Program-Wait function.
Huh? Why not just use the "Group" attribute,
>
> My Question here is, What sort of system load can I expect from doing
this?
> We currently have 200+ users on the box and all seems well, but what
happens
> when we get to 1000+ etc, will it still hold up? Is it a potential
> bottleneck, or is it clean enough?
for me, considering RDBMS, yes.
Hi there,
We are using FreeRadius on a RedHat 9.0 machine. All users are added as
system users with group membership if either "users" or "email". Users in
the "users" group have full internet access, and users in the "email" group
are restricted via a filter to only enable email access.
To get f
5 matches
Mail list logo