Hello Christian, (thanks for all the support you give here!)
users@sogo.nu (Christian Mack), 2016.11.22 (Tue) 10:01 (CET): > Am 21.11.2016 um 18:05 schrieb Marcus MERIGHI (mcmer-s...@tor.at): > > Hello, > > > > users@sogo.nu (Christian Mack), 2016.11.21 (Mon) 16:42 (CET): > >> Am 21.11.2016 um 11:57 schrieb G??tz Reinicke - IT Koordinator > >> (goetz.reini...@filmakademie.de): > >>> Hi, > >>> > >>> where/how set I the time out for a web session? Is that possible for > >>> single users individually? > >>> > >> > >> You set it in your sogo cron job. > >> Check /etc/cron.d/sogo > >> There is a line with > >> "... /usr/sbin/sogo-tool expire-sessions ..." > >> Normally you want to run this every minute. > > > > is there a guarantee the job doesn't take longer than a minute? > > > > No, there is no guarentee, but we have between 1000 and 3000 active > sessions and it never took longer than milliseconds. thanks for the real-world usage report! > It actually doesn't do that much. > It only has to get the current unix timestamp, subtract the max session > lifetime, then check the c_lastseen column for entries smaller than that > and delete those rows. > That is what databases are made for. Unix admin experience tells that a cron job running every minute has some potential to bring things down. I've now tested what I should have tested before posting... Without database/sogod up and running the job finishes even faster than when doing it's job correctly. Thanks, Marcus > >> The number at the end defines the time in minutes a session can exist. > >> > >> This works for all users. > >> If you want to kill the session of one user only, you have to go to the > >> session table defined by OCSSessionsFolderURL and delete the entry for > >> that user by hand. > >> > > > -- > Christian Mack > Universit?t Konstanz > Kommunikations-, Informations-, Medienzentrum (KIM) > Abteilung Basisdienste > 78457 Konstanz > +49 7531 88-4416 > > !DSPAM:5834097c165291322311114! -- users@sogo.nu https://inverse.ca/sogo/lists
