Comment 6 for bug 599501

> The package is installed by
> default though, so it would be nice to be able to have it as an option
> for a kiosk setup or when a friend needs to use the computer "real
> quick."

Your request makes sense, but I have my doubts about giving hidden
limits in configuration that simple or advanced users won't like. I'm
just a bit hasty, don't get me wrong -- I don't disagree that guest
session is not useful.

time.conf with guest also make sense.

But in the other limitation (per session), the limits and the way
timekpr runs would act differently for the actual user and for
"guest". What I mean:
- if you allow the user to run for 30 minutes per session, that
wouldn't affect the "guest".
- if you allow "guest" to run 30 minutes per session, that wouldn't
affect the user.
- the user could probably switch to guest and get another 30 minutes.
so he would get his limit + guest limit.

Also consider what happens when "guest" limit is up? The guest will be
locked for all other guests.

There are too many questions and far too many checks for me to
implement. I will however deeply think about it when the time comes.
:)