From: jon <jon.murphy@ipfire.org>
To: development@lists.ipfire.org
Subject: Change to collectd.conf and collect.custom
Date: Mon, 16 Jan 2023 22:10:36 -0600 [thread overview]
Message-ID: <28C93A89-EA8C-4183-8139-257A7268C8A3@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
All,
I’d like to make a change to the `/etc/collectd.conf` to remove a few monitored processes. The items appear in the <Plugin processes> section of the config file. And the processes appear at the bottom of the https://ipfire.localdomain:444/cgi-bin/services.cgi WebGUI page.
Why you ask? Mostly because smbd, nmbd, squidguard, qemu, or mpd are not used (at least by me!). And so the users of those items are not left out, I’d like to move those items to a `collect.custom`.
So overall idea is the core processes would be in `collectd.conf` file. And the add-on processes will be in `collect.custom`.
This is a snip of the plugin process section of the `collectd.conf` file:
```
<Plugin processes> <Plugin processes>
Process “sshd" to Process "sshd"
Process “smbd" this Process "squid"
Process “nmbd” ---> Process "charon"
Process "squid" Process "openvpn"
Process “squidguard" </Plugin>
Process “charon"
Process “openvpn"
Process "qemu"
Process "mpd"
</Plugin>
```
The items removed from the `collectd.conf` file would move to `collect.custom`.
<Plugin processes>
Process "smbd"
Process "nmbd"
Process "squidguard"
Process "qemu"
Process "mpd"
</Plugin>
But the problem is I don’t want to overwrite the `/etc/collectd.custom` file incase an admin has modified it for their own use.
The big question
================
So how do I change the `collectd.custom` file in `ipfire-2.x/config/collectd` AND not overwrite the admin’s `/etc/collectd.custom` file?
next reply other threads:[~2023-01-17 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 4:10 jon [this message]
2023-01-17 13:50 ` Bernhard Bitsch
[not found] <25DFEBB1-D081-4B3C-8F6B-8A12C93A5C59@ipfire.org>
2023-01-20 16:19 ` Michael Tremer
[not found] <23C86CDC-6C30-4940-B263-37E2EC06007E@ipfire.org>
2023-01-26 14:34 ` Michael Tremer
2023-01-26 15:25 ` Bernhard Bitsch
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=28C93A89-EA8C-4183-8139-257A7268C8A3@ipfire.org \
--to=jon.murphy@ipfire.org \
--cc=development@lists.ipfire.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