Hi Al, On 00:05 Sat 13 Sep , Al Chu wrote: > > I *think* I remember how this is handled in Suse now. It's a different > set of comments at the top of the init.d script. In > opensm/scripts/opensm.init.in I see this: > > ### BEGIN INIT INFO > # Provides: opensm > # Required-Start: $syslog > # Default-Start: 2 3 5 > # Default-Stop: 0 1 6 > # Description: Manage OpenSM > ### END INIT INFO
It was my original thought too. But actually those fields are used as recommendation to chkconfig --add, chkconfig --del, etc.. > I think this indicates that by default opensm should start on boot on > run levels 2 3 5. Which I guess is what we don't want. I'm going to > take a guess that the following patch will fix the problem. Patch is > completely untested (I don't have a suse system). So hopefully someone > else can try it out. The patch is good since it drops unneeded assumption about configured runlevels. Without this system defaults will be used by chkconfig, and I guess it is more portable. Unfortunately it doesn't solve the original issue. Sasha _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
