public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Protecting init.d files from auto-update
Date: Tue, 14 Jan 2025 11:28:21 +0000	[thread overview]
Message-ID: <2207251.irdbgypaU6@cube> (raw)

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'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?

-- 
Regards,
Peter.





             reply	other threads:[~2025-01-14 11:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 11:28 Peter Humphrey [this message]
2025-01-14 12:01 ` [gentoo-user] Protecting init.d files from auto-update Michael
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=2207251.irdbgypaU6@cube \
    --to=peter@prh.myzen.co.uk \
    --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