public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2] remove forgotten Nagios files, if any
Date: Thu, 26 Apr 2018 19:25:26 +0200	[thread overview]
Message-ID: <6df706d4-931b-3235-d56b-5bc5c9a457e7@link38.eu> (raw)
In-Reply-To: <1524762102.2479471.90.camel@ipfire.org>

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

Hello Michael,

thanks for the quick feedback.
> Hey,
> 
> On Thu, 2018-04-26 at 17:17 +0200, Peter Müller wrote:
>> When we decided to drop Nagios, some files were not removed on the
>> installations. Since the package does not exist anymore, "pakfire remove
>> nagios" does not work so we need to clean them up manually in case they exist.
>>
>> The second version of this patch makes sure Apache is restarted afterwards,
>> and includes some forgotten files [sic] as well as it is now applying for
>> Core Update 121.
>>
>> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
>> ---
>>  config/rootfiles/core/121/update.sh | 18 ++++++++++++++++--
>>  1 file changed, 16 insertions(+), 2 deletions(-)
>>
>> diff --git a/config/rootfiles/core/121/update.sh
>> b/config/rootfiles/core/121/update.sh
>> index 9986316e9..422f8f20f 100644
>> --- a/config/rootfiles/core/121/update.sh
>> +++ b/config/rootfiles/core/121/update.sh
>> @@ -17,14 +17,14 @@
>>  # along with IPFire; if not, write to the Free Software                    #
>>  # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA #
>>  #                                                                          #
>> -# Copyright (C) 2017 IPFire-Team <info(a)ipfire.org>.                        #
>> +# Copyright (C) 2018 IPFire-Team <info(a)ipfire.org>.                        #
>>  #                                                                          #
>>  ############################################################################
>>  #
>>  . /opt/pakfire/lib/functions.sh
>>  /usr/local/bin/backupctrl exclude >/dev/null 2>&1
>>  
>> -core=120
>> +core=121
>>  
>>  # Remove old core updates from pakfire cache to save space...
>>  for (( i=1; i<=$core; i++ )); do
>> @@ -42,7 +42,21 @@ ldconfig
>>  # Update Language cache
>>  /usr/local/bin/update-lang-cache
>>  
>> +# Remove forgotten Nagios files, if any...
>> +test -f /etc/rc.d/init.d/nagios && rm -f /etc/rc.d/init.d/nagios
>> +test -f /usr/bin/nagios && rm -f /usr/bin/nagios
>> +test -f /etc/rc.d/rc6.d/K33nagios && rm -f /etc/rc.d/rc6.d/K33nagios
>> +test -f /etc/rc.d/rc3.d/off/S67nagios && rm -f /etc/rc.d/rc3.d/off/S67nagios
>> +test -f /etc/rc.d/rc0.d/K33nagios && rm -f /etc/rc.d/rc0.d/K33nagios
>> +test -f /etc/httpd/conf/conf.d/nagios.conf && rm -f
>> /etc/httpd/conf/conf.d/nagios.conf
>> +test -f /etc/nagios/nagios.cfg && rm -f /etc/nagios/nagios.cfg
>> +test -f /usr/bin/p1.pl && rm -f /usr/bin/p1.pl
>> +test -f /usr/bin/nagiostats && rm -f /usr/bin/nagiostats
>> +test -d /usr/share/nagios/ && rm -rf /usr/share/nagios/
>> +test -d /var/nagios/ && rm -rf /var/nagios/
> 
> There is no need to test if the files or directories exist before deleting with
> rm -f. rm won't do anything if the files don't exist.
Well, we can never be sure... :-) Will change that in the 3rd version.
> 
> You can also just call rm once and add all files in one go. That would be tidier
> and if you would then sort the arguments alphabetically work well when someone
> extends it. Patches won't conflict then unless the same lines are being changed.
I am afraid I did not get it. Do you mean something like

rm -f [file1] [file2] [file3] ...

or

for i in (file1, file2, file3, ...); do
	rm -f $i;
done;

?

Thanks,
Peter Müller
> 
>> +
>>  # Start services
>> +/etc/init.d/apache restart
>>  
>>  # This update needs a reboot...
>>  touch /var/run/need_reboot

  reply	other threads:[~2018-04-26 17:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 14:38 [PATCH] " Peter Müller
2018-04-24  9:35 ` Michael Tremer
2018-04-24 14:54   ` Peter Müller
2018-04-24 14:58     ` Michael Tremer
2018-04-26 15:17       ` [PATCH v2] " Peter Müller
2018-04-26 17:01         ` Michael Tremer
2018-04-26 17:25           ` Peter Müller [this message]
2018-04-26 17:26             ` Michael Tremer
2018-04-26 19:44               ` [PATCH v3] " 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=6df706d4-931b-3235-d56b-5bc5c9a457e7@link38.eu \
    --to=peter.mueller@link38.eu \
    --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