From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Protecting init.d files from auto-update
Date: Tue, 14 Jan 2025 12:01:02 +0000 [thread overview]
Message-ID: <1992899.PYKUYFuaPT@rogueboard> (raw)
In-Reply-To: <2207251.irdbgypaU6@cube>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
On Tuesday 14 January 2025 11:28:21 Greenwich Mean Time Peter Humphrey wrote:
> Greetings,
>
> How can I prevent portage from auto-updating /etc/init.d/boinc?
>
> I run BOINC on my machines, and /etc/init.d/boinc includes far too long a
> timeout on start-stop-daemon when stopping the program. The minimum time it
> will wait is 60s, which is a long time when you're waiting. On this machine
> I set 4, 2 and 1 seconds because I run only one BOINC project, to keep the
> heat down. My big machine runs 18 projects or more, and even there 60
> seconds is way over the top (I can see the project's activity in gkrellm).
>
> Anyway, what matter if a project is terminated abruptly and has to be
> restarted? It wouldn't be the end of the world.
I am not familiar with the BOINC application. Is the program taking a long
time to stop because it is completing whatever calculation it was processing
and then have to store/upload the result and its current status before it
shuts down? If not, then I agree 60 seconds is a long time to wait.
> I've tried adding the file to CONFIG_PROTECT in make.conf, to no avail. Any
> other ideas before I submit a bug report against sci-misc/boinc?
The existing CONFIG_PROTECT in /usr/share/portage/config/make.globals ought to
protect unwanted changes. Have you inadvertently set CONFIG_PROTECT_MASK
somewhere?
You can check what portage is configured to do with:
portageq envvar CONFIG_PROTECT
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-14 12:01 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 [this message]
2025-01-14 16:31 ` Peter Humphrey
2025-01-14 12:36 ` Arve Barsnes
2025-01-14 14:18 ` Michael Orlitzky
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=1992899.PYKUYFuaPT@rogueboard \
--to=confabulate@kintzios.com \
--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