Ben-Nes Michael,
If you wish to limit users to hours, I like
to do this in an SQL
database, and make the AUTHSELECT statement conditional, on their usage
being under their prescribed hours. It's amazing what one can do with SQL
:-). Here's my example. This returns their password in two different
sections.
<section1>
select password from userbase where (userbase.username = '%n' and ((select
sum(usage.sessiontime/3600) from usage where username = '%n') <=
userbase.hours))
OR
<section2>
(userbase.username = '%n' and restricted<>'yes')
1st. If they're usage is above their limit the first section does not
return their password
2nd If they're a non-restriced user the second section returns their
password
E.G
If username = Joe and his allowed 20 hours ONLY (i.e restriced user) and
he has used 25 hours. The first section works this out and does NOT return
the password. The second section checks to see if hes a restriced user, and
if he is, it does not return his password either. Hence joeb will be bumped
off
If username = joeb and his allowed 20 hours but can go over that and has
used 30 hours. The first section does not return his password because he is
over his limit. HOWEVER, the second section does as it checks that he is
NOT a restriced user, and returns the password.
Quite simple really :-). I mean this is only me, and I find things work
better when I can do this sort of NAS stuff in SQL for Radiator to check
:-). Much easier to manage - but hey, thats just me.
Cheers.
Aaron
-- Aaron Miles ([EMAIL PROTECTED])
-- System Administrator - Impact Creativity Centre.
-- HAVE: 1988 BMW 325i Executive.
-- NEED: 321Bhp E36 M3 / E39 M5 - whatever comes first :-)
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
