From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Protecting init.d files from auto-update
Date: Tue, 14 Jan 2025 09:18:51 -0500 [thread overview]
Message-ID: <b4f369f7357f3c26583449aa4aca5e337f522ae5.camel@gentoo.org> (raw)
In-Reply-To: <2207251.irdbgypaU6@cube>
On Tue, 2025-01-14 at 11:28 +0000, Peter Humphrey wrote:
> Greetings,
>
> How can I prevent portage from auto-updating /etc/init.d/boinc?
>
In this case the init script is using a custom variable for the
timeout, and setting that variable unconditionally:
stop() {
local stop_timeout="SIGTERM/60/SIGTERM/30/SIGKILL/30"
...
}
What would be much nicer is if it
1. Used the standard $retry variable for this (man openrc-run)
2. Set $retry only if it's unset
Then you could simply provide your own $retry in boinc.conf. Going a
bit further, it could move the env_check into stop_pre(), and use
$pidfile instead of the custom $BOINC_PIDFILE. That would make the
entire stop() function redundant.
next prev parent reply other threads:[~2025-01-14 14:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 11:28 [gentoo-user] Protecting init.d files from auto-update Peter Humphrey
2025-01-14 12:01 ` Michael
2025-01-14 16:31 ` Peter Humphrey
2025-01-14 12:36 ` Arve Barsnes
2025-01-14 14:18 ` Michael Orlitzky [this message]
2025-01-14 16:28 ` Peter Humphrey
2025-01-14 16:53 ` Michael Orlitzky
2025-01-15 11:50 ` Peter Humphrey
2025-01-20 13:24 ` Peter Humphrey
2025-01-20 23:40 ` Alexis
2025-01-21 11:14 ` Peter Humphrey
2025-01-21 11:59 ` Alexis
2025-01-21 12:45 ` Michael
2025-01-30 15:50 ` Peter Humphrey
2025-01-30 15:47 ` Peter Humphrey
2025-01-31 2:53 ` Alexis
2025-01-31 14:24 ` Peter Humphrey
2025-01-31 14:34 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4f369f7357f3c26583449aa4aca5e337f522ae5.camel@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox