Hi,
I am installing PFIL 2.1.5 and IPFilter 4.1.6 on the following
configuration:
- Solaris 9, 64-bit kernel
- Sun Cluster 3.1
- sparc v9 hardware
I was able to successfully build both pfil & ipf, and create the
corresponding packages.
After the pfil package installation, I see that the /etc/opt/pfil/iu.ap file
contains the following entries:
clprivnet -1 0 pfil
hme -1 0 pfil
qfe -1 0 pfil
On a subsequent reboot, the autopush of pfil fails, with the following
errors:
autopush: ERROR: File /etc/opt/pfil/iu.ap: could not configure autopush for
line 2
autopush: ERROR: Major/minor already configured
autopush: ERROR: File /etc/opt/pfil/iu.ap: could not configure autopush for
line 3
autopush: ERROR: Major/minor already configured
I believe these errors are due to a prior autopush being executed from
inittab, using the file /etc/iu.ap. On my systems, this file contains the
following entries installed by Sun Cluster:
# Start of lines added by SUNWscr
hme -1 0 clhbsndr
qfe -1 0 clhbsndr
eri -1 0 clhbsndr
ge -1 0 clhbsndr
ce -1 0 clhbsndr
bge -1 0 clhbsndr
# End of lines added by SUNWscr
As you can see, Sun Cluster is pushing its clbhsndr module on the same
devices that pfil wants to use.
The easy work-around is for me to add pfil to the /etc/iu.ap file, after
clbhsndr. However, I would like to have a package that installs without
having to do any manual post-processing.
My questions are as follows:
- Has anyone else seen the same thing?
- Is there an automatic way to make the pfil autopush co-exist with other
modules in the 'master' /etc/iu.ap?
- Does it make sense to modify the post-install for pfil to consider these
cases, so that it adds pfil to /etc/iu.ap instead of creating a separate
iu.ap file in /etc/opt/pfil? Are there any hidden dependencies or reasons
why this should not be done?
Thanks in advance for your responses...
-Amruth Laxman