Skip to main content

Do you have mouse lag issues in Mac OSX?

There has been reports of strange mouse lag with Apple OSX;  it's far more noticeable if you're coming from Windows for the first time. The way the mouse responds and moves across the screen on OSX looks and feels different than on Windows or Linux.  It seems from system to system, and even from mouse to mouse.  I've had more success with wired Logitech mice than anything, and of course, the trackpad doesn't seem to suffer from much lag at all.

When I moved to OSX almost exclusively about 3 years ago, I was driven mad by the mouse lag.  I almost switched back!  Over time, I have gotten more or less used to it.

There were various work-arounds, like BetterTouchTool and MagicPrefs but I've never found them to be sufficient.  They were great for adding functionality and gestures to the Magic Mouse/Trackpad, though.  The responsiveness has gotten better over the last few OSX releases (particularly Mountain Lion and Mavericks) in my opinion.

 For you newcomers, there is fortunately a new solution that I've been testing for a few weeks now:  SmoothMouse

It installs as a System Preferences item.  You can set the acceleration to be more Mac-like or Windows-like, and even the ability to disable mouse acceleration altogether. One of the things I've noticed is a lower overall lag in mouse responsiveness, especially while moving windows around.  I highly recommend it for people coming from the Windows universe, as it will make your mouse more or less feel like it does in Windows.


Popular posts from this blog

Starting vmtoolsd as a service on Red Hat / CentOS

If you're like me;  you may manage virtual servers within vSphere.. Linux ones.  Red Hat ones, in particular, but this applies to CentOS as well.

A long, long time ago, in a galaxy far away, the vmware-tools setup procedure installed the necessary init script for you.  Lately though, for new images that I've been building - those init scripts aren't getting installed by the vmware tools installation package.  So they don't start up on reboot.  VMware based backups failed; clock were going askew, you name it.   I need that daemon started on reboot.

Without a SysV init script handy, I had to roll my own.. and this is the result;  despite having worked with Linux for well over 15 years, setting up SysV init scripts remain somewhat of a black art.  The ones on our older system were more complicated than we needed.  I was aiming for something simpler and portable.

With RHEL 7, the rumor mills are abuzz with systemd so that may change. But, I'm a practical system admini…

Attempting to use dd on Mac OSX? Resource Busy?

If you're trying to use the dd command to image a usb disk or another device and you're running into an error that looks like:

# dd: /dev/disk#: Resource busy

There is a simple solution.

Use OSX's Disk Utility and unmount any of the partitions you have mounted on that particular disk without unmounting or ejecting the disk itself.

Afterwards, attempt the dd command again.


Attempting to use the umount utility in Mac OSX will result in a "Resource busy -- try 'diskutil unmount'".  The command-line equivalent would be:

# sudo diskutil unmount /Volumes/<disk in question>


# sudo diskutil unmount /Volumes/FLASHUSB

NetApp: Disabling snapshot for a volume on Data OnTAP

This is one of those things that isn't always very obvious. Sometimes, you need to disable snapshots for a volume.

Why in the world would someone want to disable a perfectly good feature of NetApp NAS Storage? Server/data migration for one. Disabling it temporarily will prevent the volume from filling up the snapshot directory. Maybe your volume doesn't need snapshots (data always changing, and can not be recoverable even with snapshots- such as oracle data dirs, in which case snapshots are useless).
You have to perform simple but important tasks. If your volume has a schedule, turn it off.

somefiler> snap sched rootvol Volume rootvol: 2 4 8@2,4,6,12,164
somefiler> snap sched rootvol 0 0 0 
somefiler> snap sched rootvol Volume rootvol: 0 0 0

That takes care of that. Next step is to disable the automatic snapshot option.

somefiler> vol options rootvol nosnap on

Now if you issue vol options rootvol You should see an option that says nosnap=on.

Lastly, you'l…