[lustre-devel] LUSTRE_LNET_CONFIG_UTILITY in lnet SysV script

[Christopher J. Morrone <morrone2@llnl.gov>]

lnetctl is currently an optional build, and its build is not even
enabled by default in the lustre spec file.  To use lnetctl exclusively,
we would need lnetctl's build would need to be unconditional.

I don't have a problem with making the lnetctl build unconditional.  I'm
not sure why it was done that way.  Perhaps someone else can comment on
that.

When/if lnetctl is built unconditionally, it would be nice to purge the
"DLC" terminology from the code.

Chris

On 01/04/2017 04:16 PM, Di Natale, Giuseppe wrote:
> Greetings,
> 
> I am attempting to port the SysV lnet script as part of a transition to
> systemd. I ran into the following in lustre/scripts/lnet:
> 
>         if [ -x $LUSTRE_LNET_CONFIG_UTILITY -a -f
> "$LUSTRE_LNET_CONFIG_FILE" ]; then
>                 $LUSTRE_LNET_CONFIG_UTILITY lnet configure || exit 1
>         else
>                 lctl network up || exit 1
>         fi
> 
> Can the check for LUSTRE_LNET_CONFIG_UTILITY  (/usr/sbin/lnetctl by
> default) be removed so that way lnetctl is used exclusively?
> 
> Thanks,
> Giuseppe Di Natale
> 
> 
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>