Allow writing data to graphite without the cluster prefix

[criemen]

Allow writing data to graphite without the cluster prefix

[criemen]

Thanks for the fast fix on #86 and the turnaround time, but I can't see how the commit fixes this issue.
What I asked for was a switch to turn of the cluster prefix, either globally or for sending the data to graphite.
Maybe this is already implemented and I overlooked it, and this is the
if (source) {
part of the code, I think it is still wrong, because without a graphite_prefix and without a source, you'll still access an unitialiued graphite_msg when adding the host ti graphite_msg.

[vvuksan]

This was errantly closed. Previous fix was just for #86.

[djosephsen]

Noticed this didn't get fixed at monitorama, so I put in a pull request that will allow you to do whatever you want with the graphite path, to include omitting whatever parts make sense. (#99).

From the new gmetad.conf:

A user-definable graphite path. Graphite uses dot-separated paths to organize and refer to metrics. For reverse compatibility graphite_prefix will be prepended to this path, but this behavior should be considered deprecated.
This path may include 3 variables that will be replaced accordingly:
%s -> source (cluster name)
%h -> host (host name)
%m -> metric (metric name)
default: graphite_prefix.%s.%h.%m
graphite_path "datacenter1.gmetad.%s.%h.%m

[djosephsen]

so we can close this yeah?

[criemen]

I believe so, yes.
Thanks for your effort!