Ticket Options
Question Details
TICKET ARCHIVE -> Console Information
jsnyder12 - Oct 4, 2005 - 4:24 pm
Imac G5, OS X 10.4.2
I've been getting the following messages from Console when using Carbon Copy Cloner. Is there a problem here that I should correct?
Oct 4 10:34:31 Macintosh mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-000000000000” instead
Oct 4 10:34:36 Macintosh mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-000000000000” instead
Oct 4 11:08:13 Macintosh mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-0011243F677E” instead
Also, when using Quicken, I get the following. Is it anything to worry about?
Quicken 2005(448,0xa000ef98) malloc: *** Deallocation of a pointer not malloced: 0xffffffff; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
I've been getting the following messages from Console when using Carbon Copy Cloner. Is there a problem here that I should correct?
Oct 4 10:34:31 Macintosh mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-000000000000” instead
Oct 4 10:34:36 Macintosh mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-000000000000” instead
Oct 4 11:08:13 Macintosh mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-0011243F677E” instead
Also, when using Quicken, I get the following. Is it anything to worry about?
Quicken 2005(448,0xa000ef98) malloc: *** Deallocation of a pointer not malloced: 0xffffffff; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
kainjow - Oct 5, 2005 - 4:45 pm
Hi Joel,
Make sure you're running the latest version of Carbon Copy Cloner: http://www.bombich.com/software/ccc.html - if you still get that error, contact the developer of the program directly and explain to him the same thing you explained here.
For that Quicken error, it shouldn't affect the program, but you may want to send them an email about it. If you can find out where it's happening and when, then this would be very useful for them to. If not, it won't do them much good, but still it's worth a shot :-)
Kevin
Make sure you're running the latest version of Carbon Copy Cloner: http://www.bombich.com/software/ccc.html - if you still get that error, contact the developer of the program directly and explain to him the same thing you explained here.
For that Quicken error, it shouldn't affect the program, but you may want to send them an email about it. If you can find out where it's happening and when, then this would be very useful for them to. If not, it won't do them much good, but still it's worth a shot :-)
Kevin
jsnyder12 - Oct 6, 2005 - 10:44 am
Hi Kainjow,
Thanks for your suggestions. I'll follow-up with Bombich. Since Intuit forced me to purchase Quicken 2005 even though 2002 worked well and 2005 is a miserable piece of software, I don't want to have anything to do with them. Besides, getting an answer out of them is next to impossible.
I appreciate your assistance.
Joel
Thanks for your suggestions. I'll follow-up with Bombich. Since Intuit forced me to purchase Quicken 2005 even though 2002 worked well and 2005 is a miserable piece of software, I don't want to have anything to do with them. Besides, getting an answer out of them is next to impossible.
I appreciate your assistance.
Joel
jsnyder12 - Oct 6, 2005 - 11:58 am
Hi Kainjow,
It turns out that many people are having trouble with the scheduler in CCC and are getting console messages of the kind I reported to you. Bombich has a fix and it works. So, just in case you are interested, here it is:
In the terminal type:
Code:
tcsh
setenv EDITOR pico
crontab -e
Then once in Crontab press Return once and then ctrl and x to get it to exit... it will ask you to save. type y and press return to accept the name it gives you.
This creates an empty crontab. Once you restart the system will activate Cron for you. Then you can use Cronix to add the CCC script and run it whenever you want it to.
It turns out that many people are having trouble with the scheduler in CCC and are getting console messages of the kind I reported to you. Bombich has a fix and it works. So, just in case you are interested, here it is:
In the terminal type:
Code:
tcsh
setenv EDITOR pico
crontab -e
Then once in Crontab press Return once and then ctrl and x to get it to exit... it will ask you to save. type y and press return to accept the name it gives you.
This creates an empty crontab. Once you restart the system will activate Cron for you. Then you can use Cronix to add the CCC script and run it whenever you want it to.
TechSupport - Oct 9, 2005 - 5:30 pm
This ticket has been moved to the open forums for more exposure.
Please follow this link:
http://www.macosx.com/forums/showthread.php?t=252063
Please follow this link:
http://www.macosx.com/forums/showthread.php?t=252063
IF THIS IS YOUR QUESTION AND YOU WISH TO RESPOND, LOGIN HERE FIRST.
