Should be trivial to do, after doing an `ebuild .. install` I see a systemd unit in ${S}/startup/default-service. I've run-tested it as nagios.service, seems to work fine.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea33afbdeaa8a6d2aa86bdfeddc8dbb45818e875 commit ea33afbdeaa8a6d2aa86bdfeddc8dbb45818e875 Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2021-02-24 00:32:38 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2021-02-24 00:33:01 +0000 net-analyzer/nagios-core: new revision to install systemd service. Closes: https://bugs.gentoo.org/771774 Package-Manager: Portage-3.0.13, Repoman-3.0.2 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> ...-core-4.4.6-r1.ebuild => nagios-core-4.4.6-r2.ebuild} | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)
Lemme know if the -r2 works for you.
(In reply to Michael Orlitzky from comment #2) > Lemme know if the -r2 works for you. Works for me! Sorry it ended up a bit more complex than a simple systemd_newunit, but thanks!
(In reply to John Helmert III (ajak) from comment #3) > > Sorry it ended up a bit more complex than a simple > systemd_newunit, but thanks! It really wasn't. The service scripts for every init system are always built -- I only forced the init system to "unknown" as a micro-optimization to keep it from poking around the system looking for stuff that we're going to ultimately ignore anyway.
