Infiniband Subnet Manager

Edit Package opensm

OpenSM provides an implementation for an InfiniBand Subnet Manager and
Administration. Such a software entity is required to run for in order
to initialize the InfiniBand hardware (at least one per each InfiniBand
subnet).

Refresh
Refresh
Source Files
Filename Size Changed
_service 0000000716 716 Bytes
baselibs.conf 0000000229 229 Bytes
conf.sysconfig 0000003848 3.76 KB
opensm-3.3.24.0.844ab3b7edaa.tar.gz 0001392133 1.33 MB
opensm-remove-date-time.patch 0000000453 453 Bytes
opensm.changes 0000011856 11.6 KB
opensm.launch 0000000937 937 Bytes
opensm.service 0000000613 613 Bytes
opensm.spec 0000005968 5.83 KB
Revision 29 (latest revision is 32)
Nicolas Morey-Chaisemartin's avatar Nicolas Morey-Chaisemartin (NMoreyChaisemartin) accepted request 925136 from Johannes Segitz's avatar Johannes Segitz (jsegitz) (revision 29)
Automatic systemd hardening effort by the security team. This has not been tested. For details please see https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort
Comments 3

Andrey Novikov's avatar

It seems any params from sysconfig/opensm are ignored, as opensm-launch uses none of them.

It looks like the provided sysconfig/opensm is supposed to work with old redhat-opensm.init, but it does not suit the newer opensm-launch.


Nicolas Morey-Chaisemartin's avatar

@NovA80 I'd need to run some test but a quick look at the codeshows that it should not be ignored https://build.opensuse.org/package/view_file/science:HPC/opensm/opensm.launch?expand=1 line 12: [ -f /etc/sysconfig/opensm ] && . /etc/sysconfig/opensm


Andrey Novikov's avatar

Yes, the config file is imported into opensm-launch, but the script just doesn't use any of the variables defined there. See for example PORT_NUM=1, it just does not transformed into opensmd startup options.

openSUSE Build Service is sponsored by