Re: mysqlcc-0.8.9-linux-glibc22 - Jorge del Conde - com.mysql.lists.bugs

4 messages in com.mysql.lists.bugsRe: mysqlcc-0.8.9-linux-glibc22

From	Sent On	Attachments
Bob Lockie	22 Jan 2003 22:10
Jorge del Conde	23 Jan 2003 01:59
Bob Lockie	23 Jan 2003 12:01
Jorge del Conde	24 Jan 2003 02:06

Subject:	Re: mysqlcc-0.8.9-linux-glibc22
From:	Jorge del Conde (jor...@mysql.com)
Date:	01/23/2003 01:59:12 AM
List:	com.mysql.lists.bugs

Hi!

I found ~/.mysqlcc. When I moved it, cc ran fine but I suspect there is another config file somewhere else.

How-To-Repeat: I may have found what causes the segmentation fault, The line: Open Items = 'gw.lockie.ca'/'mysql'/'test'/'visitor'^M in ~/.mysqlcc/mysqlcc.cfg causes a segmentation fault.

It works fine if I remove that line and it is reproduceable but no other combination on that line seems to cause a crash.

The config files mysqlcc uses are stored in ~/.mysqlcc If the directory doesn't exist, it will create a new one with all the default configuration files.

I can't reproduce a crash in any of my systems. Does it only happen with that value or with that line in general ? What happens if you remove the ^M at the end of line ? .. does it still crash ?

If you find this problem anoying while a fix is found, make sure "Restore last Workspace on startup" under Options->General is unchecked .

Should passwords be encrypted in the files under ~/.mysqlcc/connections?

No, passwords shouldn't be encrypted. All the directories inside ~/.mysqlcc should have 700 perms and all the files (including connections) should have 600. 0.8.9 now creates directories and files with the correct permissions, but previous versions of mysqlcc didn't.

Regards, Jorge

MySQL Users Conference and Expo http://www.mysql.com/events/uc2003/