KChildLock doesnt appear to affect login

[Johnfm3]

KChildlock is a GUI KDE app for KDE4 which is accessed from the desktop control panel. I have been looking for solutions for time restrictions for my kids computers (paid an not) when I found this. Unfortunately, it does appear to be working even though the service shows running.

I am currently running 12.3 64bit on all my machines, an the newest version KChildLock was planned for was 12.2 64bit.

Is there that much difference between the 2 versions that this will not work?

I could really use some assistance troubleshooting this.

My other option is to locate another solution, any suggestions?

John

[Johnfm3]

Ok, so a basic function of what I am looking for is to make use of pam_time. But after making the change in /etc/pam.d/login where I added "account required pam_time.so", an added a deny all 24x7 on a account in /etc/security/time.conf, I am still able to login via console, I have not even bothered testing kde yet.

Any thoughts on this?

John

[Johnfm3]

Ok, so I got pam_time.so to work allowing all users to login between 7am an 9pm. An I have a cron entry to kill all kde sessions at 10pm in the evening.

This is not a ideal solution as I had to set this up for each user. Where KChildLock can be set to a group. Also KChildLock an limit amount of time a user can run a application.

So I am paritally there, but would like to dig deeper into this.

John

[Johnfm3]

So after much fighting with this, I have rolled back to OpenSuse 12.2 64 bit to get KChildLock to work. As sad as I am to have rolled back from 12.3, I am glad I did. The app is worth it.

As a result of this, I have made a feature request in OpenFATE. If this topic is important to you, please seak it out an vote for it.

John

[chief_sealth]

So after much fighting with this, I have rolled back to OpenSuse 12.2 64 bit to get KChildLock to work. As sad as I am to have rolled back from 12.3, I am glad I did. The app is worth it.

As a result of this, I have made a feature request in OpenFATE. If this topic is important to you, please seak it out an vote for it.

John

12.2 will be end of line in a few months. Instead of reverting to this you night try one of the unstable packages. I see three people are maintaining it on OBS for 12.3. These aren't tested as thoroughly as the stable repos (they may just be tested on the maintainers' systems), so YMMV.

software.opensuse.org:

[Johnfm3]

12.2 will be end of line in a few months. Instead of reverting to this you night try one of the unstable packages. I see three people are maintaining it on OBS for 12.3. These aren't tested as thoroughly as the stable repos (they may just be tested on the maintainers' systems), so YMMV.

software.opensuse.org:

On my personal machines I would if it was necessary. For my kids, I only use stable applications. Until then, I will stick with 12.2 for them an look forward to 13.1 for myself.

Again, this would be a great feature to add to the OS it self.

John

[debosh]

On my personal machines I would if it was necessary. For my kids, I only use stable applications. Until then, I will stick with 12.2 for them an look forward to 13.1 for myself.

Again, this would be a great feature to add to the OS it self.

John

kchildockdaemon is logical depends from consolekit. It interacts with him over dbus (ex. for geting uid of active session). In 12.3 dbus query from consolekin does not return of needed data. It must be changed for query to logind.
May be same changes are needed for termination of session.