On (01/27/09 12:05), Erik Nordmark wrote: > > A possibility would be an undo log which is cleanup up on boot. If the > software invokes libdladm to create a temporary object (e.g., the IP > interface ip.tun0) then library would create a persistent object but > also add an entry to the cleanup log which takes care of deleting it on > reboot (should the application forgot).
Keeping this journal/trail-file for undoing a set of actions also avoids the atomicity problem associated with taking/restoring snapshots. --Sowmini > If there are dependencies on the object when you reboot, for instance > the admin having set some property on the object using ipadm (which > wouldn't add to the cleanup log), then when the cleanup log is run we > can choose (poilcy) whether to blow away the property setting and the > object, or leave the object in place. > > I think that approach is simpler for the admin (the admin would not have > to worry about anything but persistent configuration), and handles > applications which desire an implicit cleanup on reboot.
