Summary: | net-analyzer/snort - install systemd unit | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alessandro Molari <molari.alessandro> |
Component: | Current packages | Assignee: | Patrick Lauer <patrick> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jstein, molari.alessandro, netmon, systemd |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 448882 | ||
Attachments: | snort.service |
Description
Alessandro Molari
2015-05-25 13:36:45 UTC
Created attachment 405680 [details]
snort.service
Fortunately adding one isn't particularly complicated - the one I've just attached ought to be able to handle everything the init.d script does. Please note there is no corresponding tmpfiles config file to manage /run/snort because it would appear that this directory is not needed when snort runs in non-daemon mode.
Well, ALMOST everything - it doesn't wait for MySQL (in any of its incarnations) or PostgreSQL to start. In principle After=mysql.service and After=postgresql.service ought to be enough, however as I haven't tested these two work (or indeed exist) I have omitted them from the attached ebuild file. (In reply to Marek Szuba from comment #2) > Well, ALMOST everything - it doesn't wait for MySQL (in any of its > incarnations) or PostgreSQL to start. In principle After=mysql.service and > After=postgresql.service ought to be enough, however as I haven't tested > these two work (or indeed exist) I have omitted them from the attached > ebuild file. Can you clarify your meaning here? the attached ebuild file I would expect an attachment that is an ebuild. It is an init script for /etc/init.d and therefore requires code to install it there, namely a patch for the ebuild. Are you assuming 'we' will just make it and add and commit? (In reply to Ian Delaney from comment #3) > It is an init script for /etc/init.d No. > Are you assuming 'we' will just make it and add and commit? Sounds trivial. inherit systemd; ...; systemd_install_serviced foo (In reply to Jeroen Roovers from comment #4) > > Sounds trivial. > > inherit systemd; ...; systemd_install_serviced foo Yes indeed. Now for a patch? Or do we just do it? As devs I thought we committed patches, not road maps The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6b906ae69c91c7a4ec841182fcc484e9494aa921 commit 6b906ae69c91c7a4ec841182fcc484e9494aa921 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2018-12-10 16:17:04 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2018-12-10 16:45:00 +0000 net-analyzer/snort: bump to v2.9.12 Closes: https://bugs.gentoo.org/550366 Closes: https://bugs.gentoo.org/618822 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> net-analyzer/snort/Manifest | 1 + .../snort/files/snort-2.9.12-snort.pc.patch | 11 + net-analyzer/snort/files/snort.tmpfiles | 1 + net-analyzer/snort/files/snort_at.service | 11 + net-analyzer/snort/metadata.xml | 5 + net-analyzer/snort/snort-2.9.12.ebuild | 258 +++++++++++++++++++++ profiles/arch/powerpc/ppc64/package.use.mask | 4 + 7 files changed, 291 insertions(+) |