I am using ubuntu 10.10 and I was looking for something using which I could specify login time for my siblings.

Ubuntu comes with PAM so if you add "account required pam_time.so" to /etc/pam.d/login and then edit /etc/security/time.conf to your liking ('man pam_time; man time.conf;') you should be able to deny users at specified times. If you want to enforce logouts too you should run a logout daemon, application or script to present a warning and (gracefully) kill user processes.

1 members found this post helpful.

First Thanks for looking into my prob. .I did went to '/etc/security/time.conf' but I could not find any thing that grants a set no of hours e.g. 2 hours, one per day, at any time of the day. All examples there, were of a specified Interval. Thanks

You could use squid as a proxy server
http://www.linuxhomenetworking.com/w...ess_with_Squid
Or look here:
https://www.linuxquestions.org/quest...-linux-521665/

Kind regards

OK but "specify login time" is not the same as "limit session duration". Anyway. On user login (UID >= 500) you could create a task that runs in the background warning the user say ten minutes before closing the session allowing the user to save data and exit cleanly and finally kills the session. For this to work you want to run the 'at' service (rarely mentioned best way to run unattended jobs in the background), pam_script (to start the job on login), Xdialog or equivalent (to display a warning to the user) and a shell script (to Rule Them All).

@unSpawn: I have tried many tutorials but I am unable to achieve this. Possibally because of my lack of experiance. Could you please provide me with a sort of site which explains this process in detail and also describe how to create a script to do this sort of task. and add it to startup.


Regards

Please don't say that. Show it. Trying stuff means you've got URI's of sites you visited, software you installed, steps you took and errors you got. You posted nothing of that.


When you know a wee bit of how your distribution works, read the documentation that comes with the software (and actually follow instructions ;-p) and practice you will never have to say that again.


Uh. I guess that's LQ ;-p Get the pam_script tarball from http://freecode.com/projects/pam_script, install the gcc compiler and PAM development library if you need to, then compile and install pam_script. Check the README inside libpam-script_0.1.12.tar.gz. Create /etc/security/onsessionopen with contents:
and make certain the file is owned by user and group root, mode 0755. Locate /etc/pam.d/gdm and add a line in the "session" section:
For testing change the "now + 1 hour" to read "now + 1 minute" or you'll be waiting too long. Test by logging in as an unprivileged user and run 'atq' in a terminal window. it should show one job. This job can be killed by the user ('at -d %jobspec'). If you don't like that add "runas=root" to the "session required" line then test again. Running 'atq' as root user should now show ('atq; at -c %jobspec') the logout job.

The following things are asserted:
- you use GNOME as Desktop Environment and GDM as greeter. For KDE-3 use something like 'dcop --all-sessions --user ${LOGNAME} ksmserver default logout 0 0 0', for KDE-4 you have to fiddle with 'dbus' or see if you have 'kdehalt'. For XFCE there is 'xfce${VERSION}-session-logout',
- the 'at' service is running and unprivileged users may execute at jobs (see 'man at.allow'),
- none of your $subjects or $serfs should have Sudo, wheel, su, 'ssh root' or equivalent rights,
- you realize killing sessions is a punitive measure and only addresses one symptom: treating the cause would be preferable.

1 members found this post helpful.