From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/radvd/
Date: Sat, 19 Aug 2017 10:11:59 +0000 (UTC) [thread overview]
Message-ID: <1503137515.564e4ed0715605dafe41568a3eb6690102cf6ca0.slyfox@gentoo> (raw)
commit: 564e4ed0715605dafe41568a3eb6690102cf6ca0
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 19 10:10:09 2017 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Aug 19 10:11:55 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=564e4ed0
net-misc/radvd: fix /run/radvd clobbering on systemd, bug #603106
Bug happens because systemd has two conflicting mechanisms
to create /var/run/:
Via .service file:
RuntimeDirectory=radvd
ProtectSystem=full
And via .tmpfilesd:
d /run/radvd 0755 radvd radvd
Systemd end up trying to start radvd in empty /var/.
The change removes tmpfiles.d entry completely.
Instead we rely on the following mechanisms to create /run/radvd:
- openrc: /etc/init.d/radvd creates it with 'checkpath -d -o radvd:radvd ${PIDFILE%/*}'
- systemd: radvd.service creates it with 'RuntimeDirectory=radvd'
Reported-by: Randy Barlow
Bug: https://bugs.gentoo.org/603106
Package-Manager: Portage-2.3.8, Repoman-2.3.3
net-misc/radvd/radvd-2.17-r1.ebuild | 66 +++++++++++++++++++++++++++++++++++++
1 file changed, 66 insertions(+)
diff --git a/net-misc/radvd/radvd-2.17-r1.ebuild b/net-misc/radvd/radvd-2.17-r1.ebuild
new file mode 100644
index 00000000000..ffd9ad165f0
--- /dev/null
+++ b/net-misc/radvd/radvd-2.17-r1.ebuild
@@ -0,0 +1,66 @@
+# Copyright 1999-2017 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+inherit systemd user eutils readme.gentoo-r1
+
+DESCRIPTION="Linux IPv6 Router Advertisement Daemon"
+HOMEPAGE="http://v6web.litech.org/radvd/"
+SRC_URI="http://v6web.litech.org/radvd/dist/${P}.tar.gz"
+
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~sparc ~x86 ~x86-fbsd"
+IUSE="kernel_FreeBSD selinux test"
+
+CDEPEND="dev-libs/libdaemon"
+DEPEND="${CDEPEND}
+ sys-devel/bison
+ sys-devel/flex
+ virtual/pkgconfig
+ test? ( dev-libs/check )"
+RDEPEND="${CDEPEND}
+ selinux? ( sec-policy/selinux-radvd )
+"
+DOCS=( CHANGES README TODO radvd.conf.example )
+
+pkg_setup() {
+ enewgroup radvd
+ enewuser radvd -1 -1 /dev/null radvd
+}
+
+src_configure() {
+ econf --with-pidfile=/run/radvd/radvd.pid \
+ --disable-silent-rules \
+ --with-systemdsystemunitdir=no \
+ $(use_with test check)
+}
+
+src_install() {
+ default
+
+ insinto /usr/share/doc/${PF}/html
+ doins INTRO.html
+
+ newinitd "${FILESDIR}"/${PN}-2.15.init ${PN}
+ newconfd "${FILESDIR}"/${PN}.conf ${PN}
+
+ systemd_dounit "${FILESDIR}"/${PN}.service
+
+ if use kernel_FreeBSD ; then
+ sed -i -e \
+ 's/^SYSCTL_FORWARD=.*$/SYSCTL_FORWARD=net.inet6.ip6.forwarding/g' \
+ "${D}"/etc/init.d/${PN} || die
+ fi
+
+ readme.gentoo_create_doc
+}
+
+DISABLE_AUTOFORMATTING=1
+DOC_CONTENTS="Please create a configuration file ${ROOT}etc/radvd.conf.
+See ${ROOT}usr/share/doc/${PF} for an example.
+
+grsecurity users should allow a specific group to read /proc
+and add the radvd user to that group, otherwise radvd may
+segfault on startup."
next reply other threads:[~2017-08-19 10:12 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 10:11 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-31 17:16 [gentoo-commits] repo/gentoo:master commit in: net-misc/radvd/ Robin H. Johnson
2024-12-31 6:40 Robin H. Johnson
2024-10-15 5:22 Sam James
2024-10-12 10:08 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 9:44 Michał Górny
2024-10-12 7:52 Michał Górny
2024-01-03 18:52 Arthur Zamarin
2023-12-06 16:01 Sam James
2023-03-15 13:50 Arthur Zamarin
2023-03-15 12:27 Arthur Zamarin
2023-03-15 12:18 Arthur Zamarin
2023-03-15 12:18 Arthur Zamarin
2023-03-15 12:18 Arthur Zamarin
2023-03-15 12:18 Arthur Zamarin
2023-02-28 15:47 Matthew Thode
2023-01-01 3:11 Sam James
2022-12-04 17:56 Arthur Zamarin
2022-12-03 12:14 Sam James
2022-12-03 12:14 Sam James
2022-12-03 12:14 Arthur Zamarin
2022-12-03 12:11 Arthur Zamarin
2022-12-03 12:11 Arthur Zamarin
2022-11-24 12:21 David Seifert
2022-09-13 14:34 Sam James
2022-09-12 19:42 Sam James
2022-07-29 4:17 Sam James
2022-04-12 21:04 Sam James
2022-01-04 3:29 Sam James
2021-09-27 22:05 Marek Szuba
2021-07-10 0:09 Conrad Kostecki
2021-07-10 0:09 Conrad Kostecki
2021-05-28 15:57 David Seifert
2021-04-27 18:09 Sam James
2021-04-27 18:09 Sam James
2021-04-27 18:02 Sam James
2021-04-27 18:01 Sam James
2021-02-22 22:40 Matthew Thode
2021-02-02 18:48 Ben Kohler
2021-02-02 16:40 Matthew Thode
2021-01-28 18:19 Matthew Thode
2020-11-27 16:28 Aaron Bauman
2020-05-06 19:58 Matthew Thode
2019-12-28 21:32 Georgy Yakovlev
2019-09-13 18:15 Mikle Kolyada
2019-09-01 21:32 Aaron Bauman
2019-08-31 12:27 Sergei Trofimovich
2019-08-30 18:39 Sergei Trofimovich
2019-08-30 13:18 Agostino Sarubbo
2019-08-30 7:57 Agostino Sarubbo
2019-03-10 18:12 Matthew Thode
2018-02-06 15:10 Thomas Deutschmann
2018-01-18 19:03 Markus Meier
2017-12-15 9:36 Jason Zaman
2017-12-09 1:36 Michael Weber
2017-11-18 9:41 Sergei Trofimovich
2017-11-18 9:21 Sergei Trofimovich
2017-11-15 23:22 Sergei Trofimovich
2017-07-18 4:07 Matt Thode
2017-02-01 10:02 Michael Weber
2017-02-01 10:02 Michael Weber
2016-11-13 8:43 Markus Meier
2016-10-01 14:55 Jeroen Roovers
2016-10-01 14:55 Jeroen Roovers
2016-09-27 21:58 Michael Weber
2016-07-23 19:39 Matt Thode
2016-06-06 16:15 Agostino Sarubbo
2016-05-31 19:23 Markus Meier
2016-04-23 15:36 Matt Thode
2016-04-03 19:04 Markus Meier
2016-03-26 16:39 Agostino Sarubbo
2016-02-28 6:43 Matt Thode
2016-02-23 19:56 Matt Thode
2015-10-04 15:26 Mike Gilbert
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=1503137515.564e4ed0715605dafe41568a3eb6690102cf6ca0.slyfox@gentoo \
--to=slyfox@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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