user/sven/openrc.git/etc/rc.conf, branch github/HEAD[no description]https://git.stealer.net/cgit.cgi/user/sven/openrc.git/atom?h=github%2FHEAD2023-04-18T04:53:18Zrc.conf: note SSD_* vars need exporting2023-04-18T04:53:18ZDoug Freeddwfreed@mtu.edu2023-04-13T20:06:06Zurn:sha1:002bcf0b67b14494fc94a176752610efad132a28init.d/rc.conf: make unicode default to yes2023-03-07T06:48:43ZWilliam Hubbsw.d.hubbs@gmail.com2023-03-07T06:48:26Zurn:sha1:b9241988a7c32f00ffd6d87f1666d7babfd705e5rc.conf: default to unicode console2023-03-07T03:41:36Zpsykosealice@ayaya.dev2023-03-06T23:15:24Zurn:sha1:5ae4d4edb55aa9d928e70557a70d024302495804
it's the high year of 2023, after all.
closes #607
netmount: add fuse.glusterfs2023-01-15T20:24:51ZMike Frysingervapier@gentoo.org2023-01-15T20:24:51Zurn:sha1:52dcb4aaa3ab1b9090e31545b38f495e551aaedc
Fixes #495.
add option for OOM score adjustment2021-12-22T16:01:14ZMatt Whitlockgentoo@mattwhitlock.name2021-07-31T21:41:57Zurn:sha1:fd1e4a384af44a8687b3a5369283f80f1cf29d84
This commit adds a new --oom-score-adj option to start-stop-daemon and
supervise-daemon, as well as an equivalent SSD_OOM_SCORE_ADJ environment
variable. If either of these are specified (with the command-line
option taking precedence), then the specified adjustment value is
written to /proc/self/oom_score_adj after forking but prior to exec'ing
the daemon (at the time when nice and ionice are applied).
Additionally, per a suggestion by Mike Frysinger, the suggested values
for the SSD_NICELEVEL, SSD_IONICELEVEL, and SSD_OOM_SCORE_ADJ variables
in the example config file are now given as zeros, which are the
kernel's default values of these process knobs for the init process at
boot. Note that uncommenting any of these zero-valued suggestions will
cause SSD/SD to set the corresponding process knob affirmatively to
zero, whereas leaving the variable unset (and the equivalent command-
line option unspecified) means SSD/SD will not change the corresponding
process knob from its inherited value.
See: https://github.com/OpenRC/openrc/pull/435#discussion_r688310672
This fixes #435.
Use cgroup.kill in cgroup_cleanup when possible2021-10-16T03:10:37ZAidan Harrisme@aidanharr.is2021-09-15T07:11:01Zurn:sha1:eaa42da9a62b55a26c7b866d4082c554a764b95f
The old code is moved to a cgroup_fallback_cleanup function and only
called if cgroup2_kill fails.
This fixes #454.
fix unified cgroups v2 setup2021-02-24T05:08:56ZWilliam Hubbsw.d.hubbs@gmail.com2021-02-24T05:08:56Zurn:sha1:4fb4674374931be2fa279692800185078f350d9f
The cgroups v2 setup required the rc_cgroups_controllers variable
to be set to the list of controllers to enable regardless of whether the
mode was hybrid or unified.
This makes sense for hybrid mode since the controllers can't be in both
the cgroups v1 and v2 hierarchies, but for unified mode we should enable
all controllers that are configured in the kernel.
rc.conf: typo fix2018-11-29T14:19:56ZWilliam Hubbsw.d.hubbs@gmail.com2018-11-29T14:18:06Zurn:sha1:ee41e444ad18192fa34f598464e3ac52f323e27e
X-Gentoo-Bug: 670874
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=670874
cgroups: add rc_cgroup_memory_use_hierarchy setting for cgroups v12018-02-26T20:33:15ZWilliam Hubbsw.d.hubbs@gmail.com2018-02-26T20:33:15Zurn:sha1:c6047f887a362cb8d96624fbd73484ca703acf53make the procedure for killing child processes of services configurable2017-09-14T21:17:20ZWilliam Hubbsw.d.hubbs@gmail.com2017-09-14T16:40:26Zurn:sha1:6a5ca2ab368d0a85f51bb559672dba2e3ffcc6be