public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] update.sh: clean out old collectd process statistics
Date: Sat, 30 Jul 2022 07:33:56 +0000	[thread overview]
Message-ID: <0ea84e2f-b296-7fe1-e753-51919eca57cf@ipfire.org> (raw)
In-Reply-To: <20220730022802.3653144-1-jon.murphy@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

Hello Jon,

thank you for submitting this. Regarding the "rm" calls, I have two comments:

(a) For transparency reasons, I have shifted to always adding "-v" argument to
     rm calls during a Core Update, so deleted files are logged. In case of
     troubleshooting, this should make (our) lives a bit easier since it is clear
     what has been deleted.

(b) This could have been one single rm call, i.e.:

rm -rvf \
	file A \
	file B \
	... \
	file N

     The update.sh script for Core Update 170 should feature such a (lengthy)
     rm call, if I am not mistaken.

Thanks, and best regards,
Peter Müller


> - processes-mysqld
> - processes-snort
> - processes-rtorrent
> - processes-asterisk
> - processes-java
> - processes-spamd
> 
> Signed-off-by: Jon Murphy <jon.murphy(a)ipfire.org>
> ---
>   config/rootfiles/core/170/update.sh | 14 ++++++++++++++
>   1 file changed, 14 insertions(+)
> 
> diff --git a/config/rootfiles/core/170/update.sh b/config/rootfiles/core/170/update.sh
> index cbac8572e..ec6c5ad09 100644
> --- a/config/rootfiles/core/170/update.sh
> +++ b/config/rootfiles/core/170/update.sh
> @@ -170,6 +170,20 @@ sed -i /etc/collectd.conf \
>   	-e "/LoadPlugin entropy/d"
>   /etc/init.d/collectd restart
>   
> +# Stop collectd Sevice
> +/etc/init.d/collectd stop
> +
> +# Cleanup old collectd statistics...
> +rm -rf /var/log/rrd/collectd/localhost/processes-mysqld
> +rm -rf /var/log/rrd/collectd/localhost/processes-snort
> +rm -rf /var/log/rrd/collectd/localhost/processes-rtorrent
> +rm -rf /var/log/rrd/collectd/localhost/processes-asterisk
> +rm -rf /var/log/rrd/collectd/localhost/processes-java
> +rm -rf /var/log/rrd/collectd/localhost/processes-spamd
> +#
> +# Start collectd
> +/etc/init.d/collectd start
> +
>   # Start services
>   /etc/init.d/rc.d/unbound start
>   /etc/init.d/rc.d/suricata start

  reply	other threads:[~2022-07-30  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30  2:28 Jon Murphy
2022-07-30  7:33 ` Peter Müller [this message]
     [not found] <B906BD41-A730-4BB0-B982-4EF559F7F561@gmail.com>
2022-08-02 15:17 ` Peter Müller

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=0ea84e2f-b296-7fe1-e753-51919eca57cf@ipfire.org \
    --to=peter.mueller@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