ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: Sergey <a_s_y@sama.ru>
To: ALT Linux Community general discussions <community@lists.altlinux.org>
Subject: Re: [Comm] collectd и плагин ping
Date: Fri, 18 Oct 2019 10:54:28 +0400
Message-ID: <201910181054.28394.a_s_y@sama.ru> (raw)
In-Reply-To: <20191018064949.GH7986@imap.altlinux.org>

On Friday 18 October 2019, Michael Shigorin wrote:

> > Сам systemd как-то может влиять?
> 
> Например, загнать процесс в mount namespace.
 
Блин, в collectd.service даже написано:

# A few plugins won't work without some privileges, which you'll have to
# specify using the CapabilityBoundingSet directive below.
#
# Here's a (incomplete) list of the plugins known capability requirements:
#   ceph            CAP_DAC_OVERRIDE
#   dns             CAP_NET_RAW
#   exec            CAP_SETUID CAP_SETGID
#   intel_rdt       CAP_SYS_RAWIO
#   intel_pmu       CAP_SYS_ADMIN
#   iptables        CAP_NET_ADMIN
#   ping            CAP_NET_RAW
#   processes       CAP_NET_ADMIN  (CollectDelayAccounting only)
#   smart           CAP_SYS_RAWIO
#   turbostat       CAP_SYS_RAWIO
#
# Example, if you use the iptables plugin alongside the dns or ping plugin:
#CapabilityBoundingSet=CAP_NET_RAW CAP_NET_ADMIN

А теперь интересное. collectd.service лежит в /lib/systemd/system/.
Вопрос на засыпку, это конфиг, или оно обновится при обновлении пакета?
В спеке %_unitdir/collectd.service без %config(noreplace).

-- 
С уважением, Сергей.


  reply	other threads:[~2019-10-18  6:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 18:47 Sergey
2019-10-18  6:41 ` Sergey
2019-10-18  6:49   ` Michael Shigorin
2019-10-18  6:54     ` Sergey [this message]
2019-10-18  7:04       ` Michael Shigorin
2019-10-18  7:14         ` Sergey
2019-10-18  7:56           ` Igor Golubkov
2019-10-18  8:23             ` [Comm] systemd, переопределение параметров unit-файла (collectd и плагин ping) Sergey
2019-12-31  8:16 ` [Comm] collectd и плагин ping Sergey

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=201910181054.28394.a_s_y@sama.ru \
    --to=a_s_y@sama.ru \
    --cc=community@lists.altlinux.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

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git