> Yes, once the VNIC is plumbed, it will not be renamed/deleted. But vrrpd > cannot be assured that the VNIC is always plumbed when the VRRP router > is created. Administrators can always unplumb the VNIC whenever they > want, even the VRRP router that relies on the VNIC is already enabled.
Sure -- so this is just a safeguard against an edge case, which I see as mostly an implementation matter and not really core to the architecture. I'm fine with it. > > What's the reason we settled on /usr/lib/vrrpd instead of > > /usr/lib/inet/vrrpd? > > > If /usr/lib/inet/vrrpd is a better place. I can certainly change that. I know there have been some religious wars about the fact that the directory is named /usr/lib/inet and not /usr/lib/net, but for all intents and purposes we generally use that directory for networking daemons, regardless of whether they are TCP/IP-specific. That said, if others feel strongly about using /usr/lib instead of /usr/lib/inet, I won't argue further about it. -- meem
