I've got an Automount set in Disk Utility for an NFS mount of my NAS at home on my MacBook Pro. The NAS stores my music and my iTunes library locally references that music.
As you might imagine, when I'm not at home, and the NFS mount is broken, iTunes doesn't always work so great. However, this never affected Quicksilver to the best of my knowledge, at least not r3815 b54. I recently upgraded to 10.6 Snow Leopard and realized that I should also upgrade Quicksilver to b56a7. Had really no problems to speak of on my Mac Pro at home, which doesn't move. And, while at home, all was well with my b56a7 install on my MacBook Pro with 10.6 as well. The problems started when I left town. I kept getting the spinning wheel of death (SPOD) immediately after activating QS, then after typing a bit (about 10 seconds) searches would show up, but then another 10 seconds of delays occurred before getting the action list for the selected item. This drove me nuts for the last few hours. A few things I did -- I found a symlink in my Home dir to the /Volumes/ NetFolder which is where my NFS mount lives, so I removed it, lest QS try to index that link on every launch. I also uninstalled the iTunes plugin and relaunched QS to make sure QS wasn't getting hung up on itunes getting hung up. Finally I removed the TextMate string ranker. This works on my Mac Pro, but when I use it on my MacBook I simply get no results. Not sure if that was related to my issues, but it definitely caused consternation, to the point where I removed it. I'm now pretty solid. I miss TextMate, and I'm sure I'll miss iTunes when I'm at home (I'll just re-enable it when at home, and disable it when not). However, I wanted to post about it should others have a similar problem. I googled for the issue and couldn't find any posts that mention it. I'm not sure what changed, either QS or OSX or iTunes, that manifested this issue where broken Automounted NFS mounts would cause QS to get stuck in a SPOD for 10-15 seconds per action, but it is definitely an issue I'd love to see resolved, if it is indeed a QS issue directly.
