You could set this up simply by adding the no_proxy option to the .curlrc file of the MEM  user to make the change permanent. Remember that to turn off the proxy for all connections, you would use:

$ setenv  no_proxy  '*'

You could set this up simply by adding the no_proxy option to the .curlrc file of the MEM  user to make the change permanent. Remember that to turn off the proxy for all connections, you would use:

$ setenv  no_proxy  '\*'

You could set this up simply by adding the no_proxy option to the .curlrc file of the MEM  user to make the change permanent. Remember that to turn off the proxy for all connections, you would use:

$ setenv  no_proxy  '\*'

A little late to post (I’ve known a while), but I thought I’d plug my talk for any interested readers out there, that are going to the conference, and use MEM!

I’m talking about Extending MySQL Enterprise Monitor with Custom Advisors, Graphs and Data Collections.

I’ve had the pleasure of working with the team that writes the MEM software (the “Enterprise Tools” team, internally and lovingly known as the “Merlin Team“, the codename that has survived various renames of the product!) for a little over 3 years now. I can’t say I was there at it’s conception, but I started working with them before the initial release of the product, and have watched (and I like to think helped shape) the product very closely whilst being the “Support Coordinator” for the Support Team for MEM. It’s …