parental daemon is resource hungry

[kay van der Zander]

the daemon is resource hungry ( demanding cpu time) while it is a normal user and not a child.
it shouldn't be active on this user.

[Adam Bieńkowski (donadigo)]

Yes, I can confirm that the daemon now is checking for new processes every 1 second which is not any good for performance, however I found an interesting example (http://users.suse.com/~krahmer/exec-notify.c) which uses Linux kernel to receive new processes so we don't need to refresh every time but instead do it natively.

[kay van der Zander (kay20)]

Imo having a guard in plank, terminal and slingshot would be solid for normal users. This guard will prevent any unauthorized execution or show any unauthorized application. So no deamon needed. This part is session based.

System is not needed because only the childs users session should be protected from it.

Even de deamon can't prevent the boot/grub changes.

I think this because every parent i know changes the account them self. They make the pc ready to work in the childs protected environment.

[Adam Bieńkowski (donadigo)]

For me the daemon should restrict every way of running a program even if it's executable or .desktop. I don't want to have only restrict the "UI" part because some smarter children can figure out how to run a program and just cheat the system.

[kay van der Zander (kay20)]

It should only be running when a child is logged in. When a admin is logged in exit the daemon. No need to run. with systemd service it will auto start always

[kay van der Zander (kay20)]

Auto start from boot.