[Bug 1197403] New: Add possibility to mark system would not be active used
http://bugzilla.opensuse.org/show_bug.cgi?id=1197403 Bug ID: 1197403 Summary: Add possibility to mark system would not be active used Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: slawek@lach.art.pl QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0 Build Identifier: Some process could be done only, when system is not actively used. For example, btrfs deduplication, compression, etc. Since deduplication is ram consuming, there is need to ran it only, when it would not prevent from normal computer usage. And that is hard to discover, when is right moment. Allow to select by user, clean my system (special app: console and GUI). Also, allow to set turn of system, when clean process are done. Maybe add special checkbox to shutdown menu, called clean before shutdown. In any case, user could stop clean procedure and select between do nothing or shutdown. During normal usage, only low-overhead process could be made, which aims to gather information to better clean system. Reproducible: Always What clean process could do: - Deduplicate - Compression based on how often files are used (more often used - less compression radio; Imagine download directory get compressed based on this information) - Data backup - Prefetch mechanism (like in Windows) based on data about how often some executables are executed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197403 http://bugzilla.opensuse.org/show_bug.cgi?id=1197403#c1 --- Comment #1 from S��awomir Lach <slawek@lach.art.pl> --- Also, maybe updates since Windows already allow to select time of not active usage. You can take other way and allow user: now it is time I have lunch, so you can clean yourself. Maybe integrate with screen lockers, but you must take care of each user have screen locker displayed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197403 http://bugzilla.opensuse.org/show_bug.cgi?id=1197403#c2 --- Comment #2 from S��awomir Lach <slawek@lach.art.pl> --- And of course, user (during installation process) must select system would not be used as server. When installing some server software, some message should been write to log to opt in system could been used as server, so some auto-cleanup features (like screen look integration) could been disabled. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197403 http://bugzilla.opensuse.org/show_bug.cgi?id=1197403#c4 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Andreas.Stieger@gmx.de Resolution|--- |WORKSFORME --- Comment #4 from Andreas Stieger <Andreas.Stieger@gmx.de> --- I believe the basic functionality from the feature request already exists. * Most of the background load topic is covered via systemd.resource-control * For "only when not on battery" see ConditionACPower * For "not when in use" conditions I think the correct implementation is already available ConditionMemoryPressure=, ConditionCPUPressure=, ConditionIOPressure= Individual service/timer owners should set appropriate defaults here, or the user can amend the package provided units to fit his needs. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com