Hi!
On Fri, 2016-11-18 at 17:21:58 +0100, Dario Minnucci wrote:
> On 11/04/16 14:38, Guillem Jover wrote:
> > ...
> > This is the relevant strace part for percona-toolkit 2.2.18-1:
> >
> > ,---
> > connect(3, {sa_family=AF_INET, sin_port=htons(443),
> > sin_addr=inet_addr("74.121.199.234")}, 16) = 0
> > `---
> >
> > Where 74.121.199.234 is www.percona.com.
> I've just discussed this issue with upstream just a minute ago and it seems
> there is a simple
> solution for it...
>
> There is a global configuration file to affect every percona-toolkit package
> tools.
> (See:
> https://www.percona.com/doc/percona-toolkit/2.2/configuration_files.html)
>
> The workaround consists in create (or modify) the file
> '/etc/percona-toolkit/percona-toolkit.conf'
> an add 'noversion-check' to it.
> ---%<-----------------------------------------------------------------
> cat << EOF >> /etc/percona-toolkit/percona-toolkit.conf
> noversion-check
> EOF
> ---%<-----------------------------------------------------------------
> This global configuration file (/etc/percona-toolkit/percona-toolkit.conf)
> should be read by every
> tool in percona-toolkit package disabling the 'call home' functionality.
>
> Can you try this solution and report results?
Yes, this seems to work! After making sure there's no version
timestamp file, stracing one of the programs does not show any
connection attempts anymore. And of course there's neither a message
prompting to upgrade the software (when run on a jessie system with an
older than published version).
So shipping such file by default would seem to fix this problem. Could
you prepare this for unstable and also stable?
Thanks,
Guillem
