Alan Maguire wrote: > hi folks > > i'm a bit confused about the need to store temporary configuration > data in the link id management API, and i was wondering if you could > help me understand the need to do this. > > are there other reasons that temporary data is stored in > /var/run/datalink.conf > other than that cited in section 2 of the Link Id Management Design - > i.e. that this data is needed in the case of a restart of dlmgmtd?
yes, that is the reason, and the temporary file is /etc/svc/volatile/network-datalink-management.cache. > (i'm assuming in this case the temporary data is needed in order to > apply all > the temporary changes again rather than reverting to persistently-configured > state - have i got this right?). > Note that the only temporary configuration saved in the /etc/svc/volatile/network-datalink-management.cache file is the <linkname, linkid> mapping, that those are only information need to be recovered. It includes <linkname, linkid, class, media> of the active links. All other configuration (e.g. ports of the aggregation etc.) will not be saved at all. Thanks - Cathy > the reason i'm asking is we're trying to figure out the what/how of > the SMF representation, and representing temporary data there > is quite complex (our hope had been that temporary configuration > was represented by kernel state, as would be the case with the > interfaces i'd plumbed and configured non-persistently). > > thanks! > > alan > > _________________________________ > clearview-discuss mailing list > clearview-discuss at opensolaris.org
