So what is the fix? Sorry if this is a silly question and I'm aware I
may be going away from RKH support but do I need to somehow re-sync
the RPM package manager? Or can I whitelist this in RKH?
This is not something that RKH can sort out. By using the package
manager you are telling RKH
On Mon, 2007-11-05 at 16:12 +, Dogsbody wrote:
Hi,
Just upgrading to 1.3.0 and it's looking great so far. A few warnings
to start with but after checking things out and adding things to the
config file I am just left with one...
[15:53:58] /sbin/ifup
... as you can see, I have added /sbin/ifup to SCRIPTWHITELIST however
it still seems to show as a warning!?
Is it because I am using PKGMGR=RPM?
Yes. If you run 'rpm -Vf /sbin/ifup' it will show that the RPM package
manager thinks the file has changed (probably showing 5, S and T as
On Mon, 2007-11-05 at 17:12 +, Dogsbody wrote:
... as you can see, I have added /sbin/ifup to SCRIPTWHITELIST however
it still seems to show as a warning!?
Is it because I am using PKGMGR=RPM?
Yes. If you run 'rpm -Vf /sbin/ifup' it will show that the RPM package
manager thinks
