[rrd-developers] [PATCH] rrd_client: Do not rewrite path names when accessing remote daemons.

Florian Forster rrdtool at nospam.verplant.org
Wed Oct 7 11:36:42 CEST 2009


sorry if I'm bringing up a point that was already denied, but I have to
admit that reading through that entire discussion is totally tiresome …

On Sun, Oct 04, 2009 at 01:14:24PM +0200, Tobias Oetiker wrote:
> I think the current implementation where only relative paths are
> allowed for remote access is fine, since this provides a measure of
> protection when people are transitioning from local to remote rrdtool.
> They may be trying to use the absolute path names they have been used
> to access when working locally and will be alerted to the problem.

I have to admit this sounds like some magic for me. Imagine some
sysadmin who uses the UNIX socket and is fine with it. Then, for
whatever reason, he switches to the network socket (requirements do
change). Now suddenly some RRD files are not updated anymore for some
reason and he has to figure our how to make it all work again.

Wouldn't it be *much* simpler to simply let the user chose what to do?
I. e. forbid absolute paths by default and only if the
option is given accept absolute paths.

There, no magic, it's possible to use absolute paths if transparency is
a must and if the user has no clue what he's doing the daemon behaves in
a way that avoids harm to some extend. Plus, it should be next to
trivial to implement.

Florian octo Forster
Hacker in training
GnuPG: 0x91523C3D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.oetiker.ch/pipermail/rrd-developers/attachments/20091007/b9b065a9/attachment.pgp 

More information about the rrd-developers mailing list