On Fri, Jan 22, 2010 at 10:13:38AM +0100, Tomasz Torcz wrote:

On Fri, Jan 22, 2010 at 11:01:37AM +0200, Pasi Kärkkäinen wrote:

...

Hello,

Has there been any plans to support running custom post-up scripts for each interface, after "ifup <interface>" ?

Debian allows you to specify:

iface eth0 inet static .. post-up /etc/network/if-up.d/fw.start

I'm looking for something similar for rhel/fedora. Any ideas?

Maybe something like POST_UP="/path/script" in /etc/sysconfig/network-scripts/ifcfg-int

You can drop a script into /etc/NetworkManager/dispatcher.d/ and check parameters. IIRC $1 is interface name and $2 is state (up, down).

Thanks for the tip. I'll look into that..

Would be nicer if it was directly in ifcfg-<interface> file though..

-- Pasi

On Fri, Jan 22, 2010 at 10:35:13AM +0100, Miloslav Trma?? wrote:

Pasi Kärkkäinen píše v Pá 22. 01. 2010 v 11:01 +0200:

...

Has there been any plans to support running custom post-up scripts for each interface, after "ifup <interface>" ?

Debian allows you to specify:

iface eth0 inet static .. post-up /etc/network/if-up.d/fw.start

I'm looking for something similar for rhel/fedora. Any ideas?

grep ifup-local /etc/sysconfig/network-scripts/ifup-post

Thanks for pointing that out. I was looking at ifup-post, and I thought ifup-local was a script provided by the system, but it seems there's no such script as a default (on RHEL5).

So I can create it and use that.

Thanks!

-- Pasi

On Fri, Jan 22, 2010 at 01:08:46PM +0200, Pasi Kärkkäinen wrote:

...

...

grep ifup-local /etc/sysconfig/network-scripts/ifup-post

Thanks for pointing that out. I was looking at ifup-post, and I thought ifup-local was a script provided by the system, but it seems there's no such script as a default (on RHEL5).

So I can create it and use that.

.. just wondering why it's under /sbin and not under /etc/sysconfig/network-scripts/

It doesn't feel very good to add custom configuration under /sbin.

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.

Richard

On 10-01-22 11:37:51, Bill Nottingham wrote:

Richard Zidlicky (rz@linux-m68k.org) said:

...

...

.. just wondering why it's under /sbin and not under /etc/sysconfig/network-scripts/

It doesn't feel very good to add custom configuration under /sbin.

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.

It's not hopeless, after all (unless NM is running).

Tony Nelson (tonynelson@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.

Bill

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@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.

Richard

Once upon a time, Richard Zidlicky rz@linux-m68k.org said:

On Fri, Jan 22, 2010 at 01:08:46PM +0200, Pasi Kärkkäinen wrote:

...

It doesn't feel very good to add custom configuration under /sbin.

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.

When I have used this, I usually put ifup-local in /usr/local/sbin and symlink it to /sbin/ifup-local. This way, I can spot it easily as a local script when doing system upgrades, etc.