>>> On 7/3/2008 at 10:20 AM, in message
<[EMAIL PROTECTED]
, <[EMAIL PROTECTED]> wrote:
>
>> > > Should a single module handle all architectures, or
>> should there be
>> > > a different module for each architecture? Also, does gmond have
>> > > some way
>> >
>> > Ideally a single module s
On Tue, Jul 01, 2008 at 08:36:20AM -0600, Brad Nicholes wrote:
> <[EMAIL PROTECTED]> wrote:
> >
> > Just a few questions about the multi-disk module implemented in Python:
> >
> > http://ganglia.svn.sourceforge.net/viewvc/ganglia/trunk/monitor-core/gmo
> > nd/python_modules/disk/multidisk.py?rev
>>> On 7/1/2008 at 8:48 AM, in message
<[EMAIL PROTECTED]
, <[EMAIL PROTECTED]> wrote:
>> > - How should such a module handle disks that are not always
>> present,
>> > e.g. iSCSI SAN volumes attached after the process has
>> started? Is it
>> > appropriate to re-initialise the list of metr
>>> On 7/1/2008 at 2:40 AM, in message
<[EMAIL PROTECTED]
, <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> Just a few questions about the multi-disk module implemented in Python:
>
> http://ganglia.svn.sourceforge.net/viewvc/ganglia/trunk/monitor-core/gmo
> nd/python_modules/disk/multidisk.py?revi
