sysconfig ifcfg-* support for running custom post-up scripts per interface?
Pasi Kärkkäinen
pasik at iki.fi
Mon May 17 11:56:43 UTC 2010
On Fri, Jan 22, 2010 at 11:04:18PM +0100, Richard Zidlicky wrote:
> On Fri, Jan 22, 2010 at 10:05:04PM +0100, Richard Zidlicky wrote:
> > On Fri, Jan 22, 2010 at 03:42:47PM -0500, Bill Nottingham wrote:
> > > Tony Nelson (tonynelson at georgeanelson.com) said:
> > > > > > same opinion here. I have actually used this for a while, adds
> > > > > > one more thing that needs be verified after system upgrades, not
> > > > > > very nice.
> > > > >
> > > > > Realistically, the conglomeration of configuration and scripts in
> > > > > /etc/sysconfing/network-scripts was never thought out well. But it's
> > > > > not worth dealing with the historical baggage to change it now.
> > > >
> > > > Perhaps there should be a default /sbin/ifup-local script that
> > > > dispatches to /etc/sysconfig/network-scripts/ifup-local/<interface>?
> > > > It could contain useful comments, including that it is by default
> > > > replaceable as its target directory is empty by default.
> > >
> > > ... which would then try and overwrite any prior user-created files
> > > in that place on upgrade.
> >
> > it could be in an optional package or declared config, noreplace. I do not
> > feel good about user-created files in /sbin.
>
> thought about it a bit more, I think it would be better to add a separate hook
> to /sbin/ifup calling config post-up scripts in /etc and leave /sbin/ifup-local
> alone.
>
I just filed RHEL5 RFE bug about this:
https://bugzilla.redhat.com/show_bug.cgi?id=592928
-- Pasi
More information about the devel
mailing list