Suspecting the hard drive, I ran Disk Utility on it from another
startup disk. The Disk Repair option found, among other things, a
large number of orphaned nodes (inodes?) whose names started with
"temp" and repaired them. Whatever it did, it seems to have fixed my
problem. Thanks.
On D
On Dec 13, 2005, at 1:01 PM, Bill Spotz wrote:
> OK, I seem to be converging on something here, but I don't know what
> to do with it. Shark gives me the following tree:
>
> 97.6% 97.6% mach_kernel memcmp
> 0.0%94.3% mach_kernel vfs_addname
> 0.0%94
OK, I seem to be converging on something here, but I don't know what
to do with it. Shark gives me the following tree:
97.6% 97.6% mach_kernel memcmp
0.0%94.3% mach_kernel vfs_addname
0.0%94.3% mach_kernel hfs_create_attr_btree
OK, I seem to be converging on something here, but I don't know what
to do with it. Shark gives me the following tree:
97.6% 97.6% mach_kernel memcmp
0.0%94.3% mach_kernel vfs_addname
0.0%94.3% mach_kernel hfs_create_attr_btree
On Dec 13, 2005, at 9:38 AM, Bill Spotz wrote:
> I recently upgraded my dual-processor G5 from Mac OS X 10.3 to 10.4.
> Ever since, the python initialization has been extremely slow, maybe
> 10 seconds or so between issuing the "python" command and getting a
> prompt. I run some automated tests o
I recently upgraded my dual-processor G5 from Mac OS X 10.3 to 10.4.
Ever since, the python initialization has been extremely slow, maybe
10 seconds or so between issuing the "python" command and getting a
prompt. I run some automated tests on this machine, and the delays
can add up, dwar
