[ofa-general] [PATCH 2/4 v2] opensm/osm_state_mgr.c rescan subnet configuration after SIGHUP

Sasha Khapyorsky sashak at voltaire.com
Wed Feb 11 03:52:55 PST 2009


On 11:22 Wed 11 Feb     , Eli Dorfman (Voltaire) wrote:
> 
> At the moment force_heavy_sweep is set in many places and also after SIGHUP.
> opensm rescans the configuration file when this flag is set, so if there is link change
> in the subnet while the user is modifying the file, the opensm may update the configuration
> even if the user didn't finish updating it.

So what is your concerts here? That OpenSM rescans unmodified file or
that file is potentially broken?

> Using another flag (e.g. rescan_config_file) that will be set only after SIGHUP will 
> assure that opensm updates subnet configuration when user finished updating the file.

Send SIGHUP. OpenSM will rescan config again and will do heavy sweep.
Where is a problem?

Sasha



More information about the general mailing list