pt-stalk documentation for .conf file is wrong

[Frederic Descamps]

In the documentation it's mention that if the file pt-stalk.conf exists in the current working directory, then “ENVIRONMENT” variables are imported from it. But in fact if pt-stalk is in the path, it won't use the config file in the current working dir but in the directory where the command is.

[Frederic Descamps (lefred)]

patch to solve this

[Baron Schwartz (baron-xaprb)]

I believe this is a duplicate issue.

What we need to do is add configuration capabilities to all of the
tools inherited from Aspersa, to match those of the tools from Maatkit.
I don't know why the documentation mentioned the cwd, because when I
wrote the code originally it was designed to be $0.conf, which is
basically an idea I copied from the Cacti templates. However this is
not the best thing; it should be
~/.tool.conf, /etc/percona-toolkit/tool.conf, and so on.

[Baron Schwartz (baron-xaprb)]

It's not supposed to read the file in the cwd, it's supposed to read $0.conf. The documentation is wrong, not the tool. Let's not change the code until we get proper configuration files for the bash tools.

[Daniel Nichter (daniel-nichter)]

pt-stalk is rewritten in 2.0 which makes this bug invalid for that series.

[Brian Fraser (fraserbn)]

Since we're no longer making patches for the 1.0 series, I'm marking this bug as Won't Fix there.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-888