> And my questions are: > > 1. One restriction of the implicated behavior is that it will only the > autopush configuration stored in /etc/iu.ap. But I don't see any good way to > solve this.
Since I believe that's the only autopush file that is examined today during boot, I don't see a problem with that. > 2. Also, a link can be assigned to an exclusive local zone, and the > autopush(1M) setting is stored in its zone-local file system. Is it possible > that I can know the relative path of that local zone and do the autopush > migration using the information stored in /local-zone-path/root/etc/iu.ap? > Is this a good idea at all? Why wouldn't we do the migrate-autopush as part of booting the zone? > 3. Another problem is that when both forms of autopush configuration exist, > if we apply both autopush settings, it might leads to incorrect behavior. So > that I'd like only apply the per-link autopush setting in that case. Is this > acceptable? That makes sense to me. -- meem
