On Fri, Jan 29, 2016 at 11:15 AM, shawn l.green
wrote:
>
>
> On 1/28/2016 6:30 PM, Larry Martell wrote:
>>
>> On Thu, Jan 28, 2016 at 5:45 PM, shawn l.green
>> wrote:
>>>
>>>
>>>
>>> On 1/28/2016 3:32 PM, Larry Martell wrote:
On Thu, Jan 28, 2016 at 2:13 PM, shawn l.green
>>>
On 1/28/2016 6:30 PM, Larry Martell wrote:
On Thu, Jan 28, 2016 at 5:45 PM, shawn l.green wrote:
On 1/28/2016 3:32 PM, Larry Martell wrote:
On Thu, Jan 28, 2016 at 2:13 PM, shawn l.green
wrote:
On 1/28/2016 1:14 PM, Larry Martell wrote:
On Tue, Jan 26, 2016 at 8:40 AM, Hal.sz S.nd
Thanks for the reply - that was indeed a typo. I resolved this buy making these
changes:
mysqldump --defaults-extra-file="c:\sql\dump.cnf" dname > c:\loc
with my cnf containing:
[client]
user = user
password = pass
Looks like I misplaced "" and or [client] / [mysqldump] in the cnf
Thanks
-
- Original Message -
> From: "Harrie Robins"
> Subject: my.cnf authencication
>
> mysqldump --defaults-file dbase > c:\sql\dbase.sql 2>> c:\log.tct
Might just be a typo in your mail, but you'll need to actually pass the
defaults-file, too: --defaults-file=c:\sql\dump.cnf .
I think the
I'm running a mysqldump in windows and I'm mailing 2>> output, right now I get
this annoying 'insecure' error that pollutes my log. So I figured I use
--defaults-file and set:
In c:\sql\dump.cnf
[mysqldump]
user = myuser
password = pass
my line looks like this
mysqldump --defaults-file dbase