UNIX admin writes: > a) for Solaris 9, should I link to the init.d/ script in rc2.d, or rc3.d? The > default route should be up fairly early in the boot process, what is the > earilest I could sucessfully pull it off?
network/physical on S10 is roughly like rcS.d/S30network.sh on S9 and older, so any time after that should do if the dependency is on physical interfaces. network/initial is like rc2.d/S69inet. I would figure right after that would be the right spot for things dependent on boot-time-configured tunnels. However, there's really no guarantee that anything outside of the box itself is running (at any point in time, let alone right at boot), so setting it whenever convenient should be fine. > b) for Solaris 10, there are several possible SMF dependencies. Should I > pick: > > svc:/network/physical:default network/physical sets up just physical interfaces, not tunnels. > svc:/milestone/network:default svcs -d shows that this is just loopback, physical, and IP Filter. It doesn't include tunnels. > svc:/network/initial:default? This includes tunnels configured by /etc/hostname.ip.tunX. Obviously, it doesn't include any tunnels that might be configured on the fly after boot. > Which of these would be most appropriate to list as a dependency, the way Sun > would do it? > It's extremely important to me that this be implemented as cleanly as > possible and as Sun-like as possible (it'll even come onto the system as a > package). I'd make it dependent on network/initial and a dependency for network/service. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
