The above fix I have written does what it is coded to, but does NOT create the required behaviour. If a user has a process that starts eating memory, then the entire session will be terminated, and the user will be booted back to the login screen.
The above fix I have written does what it is coded to, but does NOT create the required behaviour. If a user has a process that starts eating memory, then the entire session will be terminated, and the user will be booted back to the login screen.