[ofa-general] opensm as service - cfg files

[Sasha Khapyorsky]

On 10:10 Mon 27 Oct     , Al Chu wrote:
> > init scripts generally execute/source some configuration file located
> > in /etc/sysconfig/ to set some variables used in the script. These
> > variables can be used to distinguish pid filename and log filename for
> > different opensm instances. If these variables are not defined in the
> > conf file, they should be build from the parameter value e.g :
> > opensm.log.ddn12 or opensm.pid.ddn12 
> 
> My point was should the script automatically handle this, or is it the
> user's responsibility to set everything up?  As Ira mentioned in a later
> post, the console port is supposed to be at a known port value so users
> know what port to connect to.  So is it wise for the script to auto-
> magically select different different port values for different opensm
> instances?  Personally I don't think so.
> 
> I was initially thinking the init script could take command line
> arguments that could be passed directly to the init.d scripts.  So for
> example, you can say:
> 
> service opensmd start "--config ddn.conf"
> service opensmd start "--config lsi.conf"
> 
> This puts alternate log file names and console port numbers into the
> responsibility of the user.

Why to not just copy /etc/init.d/opensmd to let's say
/etc/init.d/opensmd2? Sligthly edit this (add different config file,
etc.).

Sasha