On 08/12/2016 09:34 AM, Raymond Wooninck wrote:
On a multi-user system there will be process owned by those other users. If you're not root you can't shut those down either. If users could shit down other users' processes there would be chaos! Wouldn't this even be a very good argument to prevent kshutdown running as root ? That way an user only has to start kshutdown and he could kill other users processes and therefore create chaos.
What is it about this that you don't understand? Well, strangely enough the reasons you are bringing up to run kshutdown as root, seems more arguments to PREVENT running it as root.
if I run kshutdown as a normal user (so without your patch), then I can schedule a shutdown of my laptop and this is executed perfectly. I guess that kshutdown doesn't do anything else than using the standard desktop functionality.
What is it that you don't understand in the difference between a self-administered, self installed, self-configured single user machine such as your laptop and professionally administered, commercial service ISP running 24 cores on one Terabyte of memory and a 20,000 Terabyte RAID array supports over 18,000 accounts and over 400 actively logged on users? I have an account on an ISP of that order. The give one weeks warning, minimum, of a shutdown. -- Echelon appears to work very much like a Web search engine, except that instead of searching Web pages it searches through the world's phone and data network traffic in real time. -- Ross Anderson, _Security Engineering_ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org