lagg problems on diskless client

[Beeblebrox]

>
>
> Almost as bad as back when I sent a note to a customer about a
> requirement to adjust our 'peeing' policy. (And the spell checker
> won't catch that one.)
>
> On Tue, Apr 3, 2012 at 10:29 AM, Beeblebrox <zaphod at berentweb.com> wrote:
> > On Tue, Apr 3, 2012 at 7:46 PM, Kevin Oberman <kob6558 at gmail.com> wrote:
> >
> >> On Tue, Apr 3, 2012 at 4:51 AM, Beeblebrox <zaphod at berentweb.com>
> wrote:
> >> > Slightly different point of view: Under this scenario of dikless
> clients
> >> > having dual NICs would CRAP be a choice to consider? From what I have
> >> read
> >> Typo or editorial comment^^^^^^  -)
> >> > it can offer loadbalancing but as I understand it's not really
> applicable
> >> > to diskless node situations?
>

@ Kevin:
> Does a 'dikless' server run eunichs? Sorry. I really should resist this
kind of carp.
One could assert that all forms of harem *gateway* control
were eunichs-based.

However, after a compound slip-up like that, there's no graceful recovery:
pwned, I am.

@Peter: Thanks for the explanation on carp, confirmed my understanding of
its function.

> Actually, it doesn't matter that the root is RO, just that /mnt exists so
it can be used as a mountpoint.
Why the error and why does it freeze the system then? More than happy just
to go with default /mnt but the DC does not like it for some odd reason.

> whilst $lagg_tmp is parameterised, /mnt is hard-coded in several places
No big deal, easily corrected on my end.

> AFAIR, I use a separate ramdisk because /etc/rc.d/lagg runs very early and
other mountpoints cannot be relied on.
Do you mean like a usb flash?