Transient scope creation should allow for resource management
I love that gnome now creates new systemd scopes for launched apps/processes!
To fully use these scopes, however, it would be great to allow for extensibility of their properties. Systemd unfortunately doesn't allow for .scope files. Further, the scope name created in libgnomedesktop includes the PID, so is unpredictable.
What would be the ideal design for a world where you can set each app's resource limits independently?
I can see two main paths:
- Don't do anything permanent, manage the scopes' resource limits entirely via extensions/runtime daemons/etc. This would allow you more inputs (e.g. which window is on top) but at the expense of out-of-the-box functionality.
- Allow for resource control property ingestion from known paths (perhaps also removing the PID from the scope, so all instances share the same resources). This seems particularly fraught with complexity, especially if it has to live in this library.
Thoughts?