LP #880341: pt-stalk documentation for .conf file is wrong
Description
Environment
Smart Checklist
Activity
lpjirasync January 24, 2018 at 6:03 PM
**Comment from Launchpad by: Brian Fraser on: 10-11-2012 14:30:11
Since we're no longer making patches for the 1.0 series, I'm marking this bug as Won't Fix there.
lpjirasync January 24, 2018 at 6:03 PM
**Comment from Launchpad by: Daniel Nichter on: 16-12-2011 15:36:14
pt-stalk is rewritten in 2.0 which makes this bug invalid for that series.
lpjirasync January 24, 2018 at 6:03 PM
**Comment from Launchpad by: Baron Schwartz on: 01-11-2011 16:55:44
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.
lpjirasync January 24, 2018 at 6:03 PM
**Comment from Launchpad by: Baron Schwartz on: 24-10-2011 08:51:17
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.
lpjirasync January 24, 2018 at 6:03 PM
**Comment from Launchpad by: Frederic Descamps on: 23-10-2011 13:08:10
patch to solve this
Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Priority
Low
Details
Details
Assignee
Reporter
lpjirasyncPriority
LowSmart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Smart Checklist
**Reported in Launchpad by Frederic Descamps last update 10-11-2012 14:30:13
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.