Easyfind mac and metadata7/26/2023 ![]() How much do they care about Windows file sharing? The Unix geek in me is glad that the free software underpinnings of OS X are configurable enough that I can fix them by editing a couple of text files!Īnd if you experience a delay of several seconds when connecting to a Windows file share from a Mac, e.g. The Mac lover in me is annoyed that Apple ships poor defaults for this important function. Lion (10.7) and later use smbd instead of Samba and don’t have this configuration file. Restarting the Mac is the easiest way to make these changes take effect. vfs objects = notify_kqueue,darwinacl,darwin_streams In Snow Leopard (10.6.6), the changes needed are as follows: - /etc/smb.confĒ 00:04:17đ.4 The darwin_streams module gives us named streams support. Don't become a master browser unless absolutely necessary. I don’t need those anyway, so the fix is to turn off the buggy feature unless it gets fixed in a future release. It doesn’t properly support extended attributes (an alternate data stream). Some Googling revealed that there’s a bug in the version of Samba that ships with Leopard. Going over to the Mac and copying the same files onto a shared folder on the PC works. Windows says it can’t read the source file. ![]() I also got errors when on a Windows XP client trying to copy files from an OS X share. Here is my nf for Leopard and Snow Leopard omit the maxsockbuf line in Lion and later, and you need only the first two lines in Mavericks (I think) and later because Apple changed the defaults to these settings: _ack=0 The sysctl settings to fix it are slightly different for Leopard and Gigabit networks. The fix is to, in Terminal with sudo, create the file /etc/nf and put some tweaked settings in it. Some research turned up the fact that the MacOS X default network parameters are suboptimal, at least when talking to Windows XP. Copying a file took several times as long as between two PCs on the same 100 megabit LAN. Several years ago, I noticed that SMB file sharing between Macs (running 10.3 Panther at that time, I think) and Windows XP was a lot slower than it should have been. Now my laptops have enough spare CPU time for me to use them again. It produces more usable results than Spotlight does, anyway. I use EasyFind if I really need to find a file. Launchctl unload -w /System/Library/LaunchDaemons/.plist Launchctl unload /System/Library/LaunchDaemons/.plist ![]() On the slower ones, I also turn Spotlight off completely (I think), by running (with sudo) the commands I found in this tip: On Mac laptops (excuse me, notebooks), I now edit /etc/defaults/nf and set ![]() You’d think Apple would rewrite it as a Spotlight front-end. Yes, I was involved in writing that stuff for GNU/Linux, but on Macs I almost never want to run “locate”. So, in addition to Spotlight hogging up the computer, Leopard builds a redundant, Unix-style file database, too. If it misses that time because the computer wasn’t on, it runs the job as soon as it wakes up. For a computer that’s on most of the time, that generally happens when it’s idle and I’m not around to care if the computer is slow. What’s happening? I discovered that Leopard updates the “locate” database in its weekly cron script. Just when I want to use the computer, it’s too busy to be usable. When I do open them up to do something, I often find that they are slowed to a crawl by a “find” process madly searching the disk and using most of the CPU power for the next hour or so. I keep them closed, in sleep mode, most of the time, often for days at a time, as I’m doing most of my work on faster Macs now. I have a couple of PowerBook G4 laptops that are now running Leopard.
0 Comments
Leave a Reply. |