We have one week on the sessions, 5 minutes on the heartbeat.  Shutting
down/rebooting is the usual reason for losing the heartbeat and starting
back up is a perfectly reasonable time to have to log back in - and if
you were rebooting because your system was behaving oddly, rerunning the
SmartEnforcer checks is probably a good idea.

If a big vulnerability or virus was hitting actively, we would put up a
requirement to check for whatever the fix was, then kick everybody off
right away and make them log in again - but we haven't had to do that so
far, knock on wood.

-Anne

--
Anne H. Bower
Computing Support Analyst, Student Services
Information Technology Services, Davidson College
[log in to unmask]


-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List
[mailto:[log in to unmask]] On Behalf Of John Rocchio
Sent: Tuesday, November 09, 2004 12:59 PM
To: [log in to unmask]
Subject: session and heartbeat timers

On our Residential network we are using a 3-hour heartbeat timer and no
session timers.  We are getting a lot of negative feedback from our
users.

What settings are others using?

John Rocchio
ResNet Manager
UC Santa Cruz