From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 98CDD15813A for ; Tue, 14 Jan 2025 11:28:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D86AFE07EC; Tue, 14 Jan 2025 11:28:24 +0000 (UTC) Received: from smarthost01b.ixn.mail.zen.net.uk (smarthost01b.ixn.mail.zen.net.uk [212.23.1.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E45E3E07D8 for ; Tue, 14 Jan 2025 11:28:23 +0000 (UTC) Received: from [82.69.80.10] (helo=cube.localnet) by smarthost01b.ixn.mail.zen.net.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1tXf5q-00Fsqi-0U for gentoo-user@lists.gentoo.org; Tue, 14 Jan 2025 11:28:22 +0000 From: Peter Humphrey 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 Message-ID: <2207251.irdbgypaU6@cube> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-Originating-smarthost01b-IP: [82.69.80.10] Feedback-ID: 82.69.80.10 X-Archives-Salt: cad15f52-562a-4386-908e-f302119884c7 X-Archives-Hash: 39d77b907233c101e7262c3a0428c4f3 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.