Thank you for taking the time to reportbugs and try to make Ubuntu
better.
This bug report has been marked as wont-fix due to that Ubuntu Karmic
9.10 has reached is End Of Life and it is no longer supported. Please
consider upgrading the newer Ubuntu releases. For more information
please visit
Sorry Hadn't realised this was purely karmic. I identified the problem
on lucid and on maverik. I've never used karmic, but I have had this
problem. Is there an easy way to transfer it over to a different
version of ubuntu?
--
You received this bug notification because you are a member of
Hi Andres,
Sorry Hadn't realised the bug, was just about karmic. I've only used
lucid/maverik, and have encountered it a few times. Could the bug be
re-identified as lucid or my comments be transfered to a new bug?
Simon
On 24/06/11 16:11, Andres Rodriguez wrote:
Thank you for taking the
I think the actual bug is misidentified here, even if the effect is the
same:-
If you install gmetad on a virgin machine, it creates
/var/lib/ganglia/rrds owned by nobody.
If you install ganglia-monitor on a virgin machine it creates
/var/lib/ganglia/rrds owned by ganglia
If you install gmetad
The bug appears to be in the ganglia.diff.gz file in the package source.
It includes code which creates a debian folder, within which is create a
file ganglia-monitor.postinst
That file includes code which will create the directory
/var/lib/ganglia/rrds and then run chown -R ganglia:ganglia
This is fixed in maverick, by changing the above bit of package code to
remove the references to rrds and the -R to leave rrds alone. :-
3337 +if [ -d /var/lib/ganglia ]; then
3338 + chown ganglia:ganglia /var/lib/ganglia
3339 + chmod 0755 /var/lib/ganglia
3340 +fi
Can I suggest as an update,
