Skip to contentSkip to conversation

config file lost

DISCUSSION Or Gerlitz 2 participants 5 messages Jun 16, 2013 – Jun 18, 2013 4 messages not in the archive InfiniBand

lore
Share & tools
lore

Or Gerlitz

author
#0 lore raw

opensm 3.3.15 comes with /etc/rdma/opensm.conf as part of the rpm, 3.3.16 doesn't, why?

# rpm -ql opensm-3.3.16-1.el6.x86_64
/etc/init.d/opensmd
/etc/logrotate.d/opensm
/etc/opensm
/usr/sbin/opensm
/usr/sbin/osmtest
/usr/sbin/sldd.sh
/usr/share/doc/opensm-3.3.16
/usr/share/doc/opensm-3.3.16/AUTHORS
/usr/share/doc/opensm-3.3.16/COPYING
/usr/share/doc/opensm-3.3.16/QoS_management_in_OpenSM.txt
/usr/share/doc/opensm-3.3.16/README
/usr/share/doc/opensm-3.3.16/opensm_release_notes-3.3.txt
/usr/share/doc/opensm-3.3.16/performance-manager-HOWTO.txt
/usr/share/man/man5/torus-2QoS.conf.5.gz
/usr/share/man/man8/opensm.8.gz
/usr/share/man/man8/osmtest.8.gz
/usr/share/man/man8/torus-2QoS.8.gz
/var/cache/opensm

# rpm -ql opensm-3.3.15-1.el6.x86_64 /etc/logrotate.d/opensm
/etc/rc.d/init.d/opensm
/etc/rdma/opensm.conf
/etc/sysconfig/opensm
/usr/sbin/opensm
/usr/sbin/osmtest
/usr/share/doc/opensm-3.3.15 /usr/share/doc/opensm-3.3.15/AUTHORS /usr/share/doc/opensm-3.3.15/COPYING /usr/share/doc/opensm-3.3.15/ChangeLog /usr/share/doc/opensm-3.3.15/INSTALL /usr/share/doc/opensm-3.3.15/NEWS /usr/share/doc/opensm-3.3.15/README /usr/share/doc/opensm-3.3.15/doc /usr/share/doc/opensm-3.3.15/doc/QoS_management_in_OpenSM.txt /usr/share/doc/opensm-3.3.15/doc/opensm-sriov.txt /usr/share/doc/opensm-3.3.15/doc/opensm_release_notes-3.3.txt /usr/share/doc/opensm-3.3.15/doc/partition-config.txt /usr/share/doc/opensm-3.3.15/doc/performance-manager-HOWTO.txt /usr/share/man/man5 /usr/share/man/man5/torus-2QoS.conf.5.gz /usr/share/man/man8
/usr/share/man/man8/opensm.8.gz /usr/share/man/man8/osmtest.8.gz /usr/share/man/man8/torus-2QoS.8.gz /var/cache/opensm

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 51BDB769.70107-VPRAkNaXOzVWk0Htik3J/[email protected]

#2 lore raw
Quoted 2 lines · Or Gerlitz

opensm 3.3.15 comes with /etc/rdma/opensm.conf as part of the rpm, 3.3.16 doesn't, why?

I'm not 100% sure about the origin of those RPMs but I think the 3.3.15 one is RedHat packaged and the 3.3.16 appears to be PLD packaged and the processes are a little different. I suspect the 3.3.16 one is packaged with the spec file in the tree whereas RedHat uses their own spec file.

FWIW it's simple to generate an up to date config file:

opensm -c opensm.conf

-- Hal

Quoted 40 lines
# rpm -ql opensm-3.3.16-1.el6.x86_64
/etc/init.d/opensmd
/etc/logrotate.d/opensm
/etc/opensm
/usr/sbin/opensm
/usr/sbin/osmtest
/usr/sbin/sldd.sh
/usr/share/doc/opensm-3.3.16
/usr/share/doc/opensm-3.3.16/AUTHORS
/usr/share/doc/opensm-3.3.16/COPYING
/usr/share/doc/opensm-3.3.16/QoS_management_in_OpenSM.txt
/usr/share/doc/opensm-3.3.16/README
/usr/share/doc/opensm-3.3.16/opensm_release_notes-3.3.txt
/usr/share/doc/opensm-3.3.16/performance-manager-HOWTO.txt
/usr/share/man/man5/torus-2QoS.conf.5.gz
/usr/share/man/man8/opensm.8.gz
/usr/share/man/man8/osmtest.8.gz
/usr/share/man/man8/torus-2QoS.8.gz
/var/cache/opensm

# rpm -ql opensm-3.3.15-1.el6.x86_64 /etc/logrotate.d/opensm
/etc/rc.d/init.d/opensm
/etc/rdma/opensm.conf
/etc/sysconfig/opensm
/usr/sbin/opensm
/usr/sbin/osmtest
/usr/share/doc/opensm-3.3.15 /usr/share/doc/opensm-3.3.15/AUTHORS /usr/share/doc/opensm-3.3.15/COPYING /usr/share/doc/opensm-3.3.15/ChangeLog /usr/share/doc/opensm-3.3.15/INSTALL /usr/share/doc/opensm-3.3.15/NEWS /usr/share/doc/opensm-3.3.15/README /usr/share/doc/opensm-3.3.15/doc /usr/share/doc/opensm-3.3.15/doc/QoS_management_in_OpenSM.txt /usr/share/doc/opensm-3.3.15/doc/opensm-sriov.txt /usr/share/doc/opensm-3.3.15/doc/opensm_release_notes-3.3.txt /usr/share/doc/opensm-3.3.15/doc/partition-config.txt

Quoted 14 lines

/usr/share/doc/opensm-3.3.15/doc/performance-manager-HOWTO.txt /usr/share/man/man5 /usr/share/man/man5/torus-2QoS.conf.5.gz /usr/share/man/man8
/usr/share/man/man8/opensm.8.gz /usr/share/man/man8/osmtest.8.gz /usr/share/man/man8/torus-2QoS.8.gz /var/cache/opensm

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 51BF591B.4090002-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org

author
#4 lore raw
Quoted 8 lines · Hal Rosenstock

I'm not 100% sure about the origin of those RPMs but I think the 3.3.15 one is RedHat packaged and the 3.3.16 appears to be PLD packaged and the processes are a little different. I suspect the 3.3.16 one is packaged with the spec file in the tree whereas RedHat uses their own spec file.

FWIW it's simple to generate an up to date config file:

opensm -c opensm.conf

Hal,

YES for your observations, that 3.3.15 was RHEL packages and the 3.3.16 was built from the upstream spec. I know that
I can generate the config file using the method you suggested, however, does the upstream service scripts uses the location to which this is generated, so things are plug-and-play, or I need to hack that somehow?

Or.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 51C02269.5050105-VPRAkNaXOzVWk0Htik3J/[email protected]

#6 lore raw
Quoted 10 lines · Or Gerlitz
Quoted 8 lines · Hal Rosenstock

I'm not 100% sure about the origin of those RPMs but I think the 3.3.15 one is RedHat packaged and the 3.3.16 appears to be PLD packaged and the processes are a little different. I suspect the 3.3.16 one is packaged with the spec file in the tree whereas RedHat uses their own spec file.

FWIW it's simple to generate an up to date config file:

opensm -c opensm.conf

Quoted 7 lines

Hal,

YES for your observations, that 3.3.15 was RHEL packages and the 3.3.16 was built from the upstream spec. I know that
I can generate the config file using the method you suggested, however, does the upstream service scripts uses the location to which this is generated,

Is /etc/rdma a standard location in Linux ? Is it used by other RDMA upstream components ?

Also, opensm doesn't by default use this location for the config file. I expect that's dealt with by other scripts RedHat supplies.

Quoted 1 line

so things are plug-and-play, or I need to hack that somehow?

You would currently need to hack that.

-- Hal

Quoted 3 lines

Or.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#8 lore raw
Quoted 1 line · Hal Rosenstock

Is /etc/rdma a standard location in Linux ? Is it used by other RDMA upstream components ?

its used by RHEL packages, not upstream

Quoted 2 lines

Also, opensm doesn't by default use this location for the config file. I expect that's dealt with by other scripts RedHat supplies.

yes, this is part of their specs I think

Quoted 3 lines
Quoted 2 lines
Quoted 2 lines

so things are plug-and-play, or I need to hack that somehow?

You would currently need to hack that.

How exactly? I'd like to build rpm from upstream opensm, generate config file and have the opensm service script to read this config and apply it for successive restarts or sig HUPs I send. Maybe you can come up with some patch, it will help

Or.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html