Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Preventing updates to iptables

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Preventing updates to iptables


Chronological Thread 
  • From: Mark Feit <>
  • To: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>, "Garnizov, Ivan (RRZE)" <>, "" <>
  • Subject: Re: [perfsonar-user] Preventing updates to iptables
  • Date: Tue, 12 Jul 2016 15:25:43 +0000
  • Accept-language: en-US
  • Authentication-results: nasa.gov; dkim=none (message not signed) header.d=none;nasa.gov; dmarc=none action=none header.from=internet2.edu;
  • Spamdiagnosticoutput: 1:0
Uhl, George D. (GSFC-423.0)[SGT INC] writes:
>
> I was interested in knowing if I could customize the update process. IMO,
> having that capability is a plus simply because then I could prevent
> unwanted modifications to my pS config prior to the upgrade rather than
> finding out after the fact. For iptables I can implement a post-update
> restore.

If you’re on an RPM-based system, the easiest thing to do might be to write a
package that uses triggers (see http://rpm.org/api/4.4.2.2/triggers.html) to
detect an upgrade on whatever of our packages is clobbering your iptables
confg, replace it with your own and restart iptables.

--Mark



Archive powered by MHonArc 2.6.19.

Top of Page