acua modRec [-s]
<login> <expire> <timeLimit> [sessionLimit] [priority] {classLimit}
<login> <+|-><SMARTTIME>|<SSMARTTIME>|<TCSMARTTIME>| <SMARTBOOT>|<SSMARTBOOT>|<TCSMARTBOOT>| <ISMARTBOOT>|<WARNBOOT>|<EXPLAINBOOT>|<NOUNSUB>|<0-15>
<login> <maxLogins>|<maxDeduct> <+=|-=|=> <n>
<login> <idleLimit>|<PPPidleBytes>|<PPPidleMIn> <+=|-=|=> <n>
<login> <tLeft>|<tLimit>|<credit>|<sLeft>|<sLimit> <+=|-=|=> <minutes>
<login> <cLeft>|<cLimit> <class> <+=|-=|=> <minutes>
<login> <bTx>|<bRx>|<bTxLimit>|<bRxLimit>|<bLimit>| <bStxLimit>|<bSrxLimit>|<bSlimit> <+=|-=|=> <bytes>
<login> priority = <priority>
<login> ph_no = <ph_no>
<login> expire <+=|-=|=> <expire>
acua modRec modifies an ACUA user record.
The -s switch can be used to strictly enforce setting of "time left" fields within their corresponding limits. For example, if you set tLeft > tLimit, acua modRec will set tLeft = tLimit. This switch is mostly intended to support "time bank" functionality (see the HOWTO for more information).
In the first usage, directly change the expiry date and time limits of a user. See acua addRec for a description of the arguments.
In the second usage, flags are modified. Flags are asserted with + and de-asserted with -, as you might expect. The flags 0-15 are user-defined flags (meaning that you define their meaning/purpose). Currently, acua forEach and acua renew are capable of basing their actions on the value of user-defined flags.
The system-defined flags are:
- SMARTTIME - Don't deduct time unless the system is busy.
- SSMARTTIME - Don't deduct session time unless the system is busy.
- TCSMARTTIME - Don't deduct time in the current time class unless the system is busy.
- SMARTBOOT - If overall time runs out, the user may still be allowed to stay on the system provided it is not busy.
- SSMARTBOOT - If session time runs out, the user may still be allowed to stay on the system provided it is not busy.
- TCSMARTBOOT - If the user runs out of time in the current time class, they may still be allowed to stay on the system provided it is not busy.
- ISMARTBOOT - If there is an idle time limit in effect for the user which has been exceeded, they may still be allowed to stay on the system provided it is not busy.
- WARNBOOT - The user may be warned of imminent disconnection.
- EXPLAINBOOT - The user may be sent e-mail explaining the reason for disconnection.
- NOUNSUB - When the user is due to be unsubscribed, a script (usually /usr/sbin/acua_nounsub) will be executed instead. See the example script for more info.
NOTE: See the BusyTreshold section in acua.config for a description of when the system is considered to be busy.
In the remaining usages, specific fields are modified. Fields may be incremented (+=), decremented (-=), or directly changed (=). The fields are:
priority - Priority
maxLogins - Maximum allowed number of simultaneous logins
maxDeduct - Maximum number of minutes to deduct each minute (<= maxLogins)
PPPidleBytes, PPPidleMin - A PPP user is considered idle if they have transferred less than PPPidleBytes bytes in the last PPPidleMin minutes
tLeft - Time left
tLimit - Time limit
credit - Time credit
sLeft - Session left
sLimit - Session limit
cLeft - Class time left
cLimit - Class time limit
bTx - Bytes uploaded
bRx - Bytes downloaded
bTxLimit - Limit on bytes uploaded
bRxLimit - Limit on bytes downloaded
bLimit - Limit on bytes transferred
bStxLimit - Session limit on bytes uploaded
bSrxLimit - Session limit on bytes downloaded
bSlimit - Session limit on bytes transferred
NOTE: If a user has a subscription, any changes to their record made with acua modRec will be undone when the subscription expires.
Robert Davidson