Posts Tagged ‘macosx’

Rsync, Mac OS X, and external USB drives

Monday, October 4th, 2010

For the last year or so, I’ve had two 1tb external USB drives, one attached to a winPC at work, the other to a MacPC at home.  I kept them synchronized with rsync over ssh, and had silently been bemoaning the lack of consistent support for extended characters.  Lots of “file vanished” type errors.

Recently, the USB drive at home started ejecting itself; seemed like a sign of impending overall failure, so I went and bought a replacement drive, 2tb ’cause it was on sale.  When I got it home, I had to reformat it before the Mac could write to it (in fairness, the box did mention this, I just didn’t read the box), so I went with journaled MacFS.  Today’s sync is taking extra time because it’s finally started successfully transfering the files with embedded extended chars, ala “Bj\#224rk”.  All this time, I assumed the problem was poor character set support in the mac version of rsync, turns out it was more of a FAT filesystem problem.  Learn something every day.

Or maybe rsync just discovered a new way of duplicating files.  d’ohwell.

iTunes process xx exceeded 500 log message per second limit

Thursday, September 16th, 2010

Dealing with some driver errors on my iMac, I started looking at /var/log/system.log on my Snow Leopard machine, and noticed that when I start iTunes, it’s generating a boatload of log messages of questionable value.

It’s row after row of incrementing numbers

Sep 16 10:22:03 WideMac [0x0-0x1e01e].com.apple.iTunes[202]: 14212
Sep 16 10:22:03 WideMac [0x0-0x1e01e].com.apple.iTunes[202]: 1
Sep 16 10:22:03 WideMac [0x0-0x1e01e].com.apple.iTunes[202]: 2
Sep 16 10:22:03 WideMac [0x0-0x1e01e].com.apple.iTunes[202]: 3

Sep 16 10:22:03 WideMac [0x0-0x1e01e].com.apple.iTunes[202]: *** process 202 exceeded 500 log message per second limit  -  remaining messages this second discarded ***

Once the next second comes up, the messages start again.  It goes all the way up to about 10,000 before it hits another discard message and doesn’t start again when the next second comes up.  Odd.

Mac ScreenSaverEngine out of control memory usage

Tuesday, May 11th, 2010

I suspect the size of my iPhoto library has something to do with the fact that the ScreenSaverEngine.app process has grown to a 12Gb VSize.    I will have to monitor that, see if it continues to grow.  I’m taking a lot of pictures with the new camera.  I ended up with over 1700 for the Maritime Festival, which totally broke the Flickr Uploadr =(

“..namedfork/rsrc” no such file or directory

Tuesday, April 20th, 2010

You are running a perl script, on a mac, and you get this error, on a script that’s run without giving you that error before, eh?

I’m 99.99% sure the causer of your problem is that  you are accessing a file on a non HFS+ filesystem, like say an external USB drive, or perhaps a network share from a windows box.  That seemed to be the issue when I got it.  The lack of resource fork can be safely ignored for files on such filesystems.

If you are seeing the error on a proper mac-disk, I dunno what to tell you.  Hope you have good backups?

Mac OSX file system quirk

Thursday, March 11th, 2010

I learned today that, “the default file system of Mac OS X, HFS+ (Mac OS Extended format), is case-insensitive but case preserving.”

In retrospect, it explains some odd behavior I have seen working in the shell, but I never put it together till today.  I have a parent dir with 26 children dirs “A,B,C,…”.  I type “cd a” by accident, and am surprised when I get no error message, and confused when pwd shows “a” as current dir, yet cd’ing back up a level and looking at the parent dir only shows capital letter sub-dir names.  It doesn’t just preserve the case something exists as, it also seems to preserve the case I referred to something with, which seems needlessly complex, but I have to admit is technically cool.  I’d hate to have to test it though.