On Thu, Jan 31, 2008 at 07:03:47AM -0800, Glenn Faden wrote:
>
> Unless someone can explain how to do this better, I will amend my
> proposal as follows:
>
>
> 1. Each zoneadmd will keep track of routes that it was successful in
> establishing. It will remove such routes when it halts a zone.
>
> 2. If the attempt to create the route fails with EEXIST, a warning
> message is printed stating that the route is was previously established
> and may be removed by another zone.That means that duplicate (shared)
> routes are permitted, but discouraged, since they will fail if the first
> zone to set this route is halted.
>
> It should be noted that this information will be lost if zoneadmd dies
> and is restarted. That shouldn't be happening, but there is logic in
> zoneadm to restart a failed daemon.
>
> This approach has the opposite problem that it cleans up too
> aggressively instead of leaving obsolete routes.
I'm a little concerned that this would cause problems for users who are
treating zones as administrative containers and assume that rebooting
zoneX will have no effect on zoneY. It sounds as if that would no
longer be the case, and that worries me: more and more the more I think
about it actually.
Ceri
--
That must be wonderful! I don't understand it at all.
-- Moliere
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080131/9c2bd3da/attachment.bin>
