Lars Ellenberg a écrit :
On Fri, Apr 23, 2010 at 11:03:11AM +0200, Hervé Gautier wrote:
Lars Ellenberg a écrit :
That's not how it works. Its not a global limit, but a common default
inherited by those resourced that don't override it locally.
I see that it could be useful to have t
On Fri, Apr 23, 2010 at 11:03:11AM +0200, Hervé Gautier wrote:
> Lars Ellenberg a écrit :
> >That's not how it works. Its not a global limit, but a common default
> >inherited by those resourced that don't override it locally.
> >
> >I see that it could be useful to have the global limit you descr
Lars Ellenberg a écrit :
That's not how it works. Its not a global limit, but a common default
inherited by those resourced that don't override it locally.
I see that it could be useful to have the global limit you describe.
But we don't have it.
Thank Lars !
So if I understand well, It is
On Fri, Apr 23, 2010 at 10:23:33AM +0200, Hervé Gautier wrote:
>
> Joseph L. Casale a écrit :
> >
> >>What about using both ?
> >
> >Why, what would that accomplish?
> It could be a way to allocated bandwidth per resource, but in case
> of several resources need to synchronize, the global may be u
Joseph L. Casale a écrit :
What about using both ?
Why, what would that accomplish?
It could be a way to allocated bandwidth per resource, but in case of
several resources need to synchronize, the global may be used for a
global limitation.
For example:
common {
syncer {
rat
>If rate is used like this:
>common {
> syncer {
> rate 20M;
> [...]
> }
> [...]
>}
>It it a global bandwidth limitation for all resources ?
http://www.drbd.org/users-guide/re-drbdconf.html
That's what common means...
>resource r2
> syncer {
> rate 15M;
> [...]
> }
Hello world !
If rate is used like this:
common {
syncer {
rate 20M;
[...]
}
[...]
}
It it a global bandwidth limitation for all resources ?
If rate is used like this:
resource r1
syncer {
rate 10M;
[...]
}
[...]
}
resource r2
syncer {
rate 15M;
[...
