That's where they belong then. Thanks Michael.
Michael Perzl wrote:
> Hi Eric,
>
> in my opinion they should go into ganglia-gmond as they are the
> dynamically loaded modules by gmond and nobody else except gmond uses them.
>
> Regards,
> Michael
>
> On 02/10/2010 10:54 PM, Eric Shubert wrote
Hi Eric,
in my opinion they should go into ganglia-gmond as they are the
dynamically loaded modules by gmond and nobody else except gmond uses them.
Regards,
Michael
On 02/10/2010 10:54 PM, Eric Shubert wrote:
> I'm attempting to update the ganglia packages I found at the epel repo
> for myself
I'm attempting to update the ganglia packages I found at the epel repo
for myself and possible inclusion at rpmforge. There are some apparently
new files with this release, and I'd like to be sure I put them with the
appropriate packages.
I'm guessing that these files should go in the ganglia-d
On Sun, Feb 07, 2010 at 01:30:43PM +, Daniel Pocock wrote:
>
> We've just been discussing the sysconfdir issue while here at FOSDEM
>
> For Ganglia <= 3.1.2,
> - the configure --help output tells people they can use --sysconfdir to
> set the location of gmond.conf
> - the configure --help out
Brooks Davis wrote:
> On Sun, Feb 07, 2010 at 01:30:43PM +, Daniel Pocock wrote:
>
>> We've just been discussing the sysconfdir issue while here at FOSDEM
>>
>> For Ganglia <= 3.1.2,
>> - the configure --help output tells people they can use --sysconfdir to
>> set the location of gmond.conf
On Wed, Feb 10, 2010 at 12:02, Daniel Pocock wrote:
> Jesse Becker wrote:
>> On Wed, Feb 10, 2010 at 11:32, Daniel Pocock wrote:
>>
>>> A while back, I introduced a patch to configure.in that determines
>>> whether or not lib directories should be called lib or lib64
>>>
>>> This is needed when t
Jesse Becker wrote:
> On Wed, Feb 10, 2010 at 11:32, Daniel Pocock wrote:
>
>> A while back, I introduced a patch to configure.in that determines
>> whether or not lib directories should be called lib or lib64
>>
>> This is needed when trying to find things like libconfuse
>>
>> lib64 is not a
On Wed, Feb 10, 2010 at 11:32, Daniel Pocock wrote:
>
>
> A while back, I introduced a patch to configure.in that determines
> whether or not lib directories should be called lib or lib64
>
> This is needed when trying to find things like libconfuse
>
> lib64 is not a universal phenomenon though -
A while back, I introduced a patch to configure.in that determines
whether or not lib directories should be called lib or lib64
This is needed when trying to find things like libconfuse
lib64 is not a universal phenomenon though - it is not the norm on Debian.
However, I note that the Linux FH
