I sent the following post on Friday 5/11. I received no replies so I guess
nobody else finds this a problem.
Oh well - its down to the rc3.d script.
Tony
===================original posting=============================
I have a strange problem.
GS140 with DUNIX V4.0E + PK2. We have a 5 tape devices. A DAT and 4 x
TZ89's in a TL894 silo.
The tape device special file names (rmt0, rmt1 etc). Do not match the bus
ordering (bus, target and LUN). This is annoying but not a real problem.
We cannot change the rmt* file names as various applications, scripts etc
expect to see them in their existing order.
Now all this is fine. Pre V4.0E, if you rebooted the box, if the tape
device special files existed, they WERE NOT recreated. They were only
created if a physical device existed that DID NOT have a device special
file. ie., if you added a new device, the next rmt number would be used by
default.
The 4.0e upgrade release notes (we upgraded from v4.0d some months ago) did
say that tape device special files would be deleted and recreated in bus,
target and LUN order, and that if you wanted them in a different order, you
should delete and recreate following the upgrade. This we did and all was
fine with the world.
However, when we reboot the box now (V4.0e + PK2) it seems to ALWAYS delete
the tape device special file names and recreate them in the default order.
The /dev/MAKEDEV.log file matches the date and time of the last reboot and
shows these things being recreated.
Is this an intentional change of behaviour and is it documented anywhere? If
it is, does anybody have a way around the problem (apart from the obvious of
putting a script in /sbin/init.d and a link to /sbin/rc3.d/S??tapefilenames
to delete them and recreate them in the desired order).
Tony
Received on Tue Nov 09 1999 - 10:11:14 NZDT