|
> Consider this exception record scenario...
> User JOE is excluded from say 6:00 to 18:00, idle limit *
> Next entry is JOE again, excluded from 18:01 to 5:59, idle limit 120
> Now, lets say JOE is idle from 17:00 on. From the test I did, it would appear
> that JOE user would be zapped at 20:00 rather than at 19:00. In other words
> the idle time accumulated is lost or reset crossing a time boundry.
As long as a user has an unlimited idle time limit (*), the process
can not accumulate idle time [This can be verified via the "REPORT"
function.] Therefore, at 18:00 JOE is "active" because of the unlimited
idle time limit. Idle time only starts to accumulate at 18:01, resulting
in the process being killed 120 minutes later (assuming it remains idle).
However, if what you want is to allow the user to accumulate idle time
during the 06:00 to 18:00 time frame, then what you want to do is:
1. Specifiy an idle time limit in the first entry.
2. Change the action to "LOG"
This will cause the user to accumulate idle time and be "logged" into
the history file when the time is reached. However, no other action
is taken. But when 18:01 rolls around, if the user has ALREADY reached
their idle time limit they will be killed IMMEDIATELY. If they are not
yet at their idle time limit, then idle time will continue to accumulate.
Example 1:
JOE becomes idle at 12:00. At 18:00 JOE has 360 minutes of idle
time. At 18:01 a new idle time limit is imposed of 120 minutes
and the new action "STOP" is immediately implemented. Note that
no warning messages were send, although the final logout message
will be displayed.
Example 2:
JOE becomes idle at 17:00. At 18:00 JOE has 60 minutes of idle
time. At 18:01 a new idle time limit is imposed of 120 minutes,
but because the new limit has not yet been reached, no action is
taken. Warning messages will be sent for the remaining 60
minutes of idle time and JOE will be "STOPPED" at 19:00.
> Would it make a difference if the second entry has a time range from
> from 00:00 to 23:59 instead of 18:01 to 5:59?
No, there is no difference. The "effective" time would remain 18:01
to 5:59 as long as the time specified covered at least that time.
You may not want user's immediatly killed as soon as 18:00 rolls around.
If you want to provide a "minimum" warning time of say 30 minutes, then
create the following series of rules:
1. User is immune (IDLE LIMIT = "*") from 06:00 to 16:30.
2. User is logged (ACTION = "LOG") from 16:31 to 18:00.
3. User is killed (ACTION = "STOP", IDLE LIMIT = "120") from
18:01 to 05:59.
This will result in the user having no more than 90 minutes of idle time
at 18:01 so that they will receive warnings.
I hope that this answers your questions.
Keith Maconi
|