Skip to main content

Re-indenting a script in VIM

I use vim daily on all of the systems I manage.  It's a critical tool for me; I can't stand emacs nor can I stand nano.  Whatever.

All of my scripts are perfectly formatted; I swear by this.  Four spaces for tabs.  Opening and closing braces are where they need to be.   I take pride in this.  But, every once in a while, you're going to run into a script or two that wasn't written by you- and you need this formatted proper. 

One note, this only works for scripts that VIM recognizes- so these obscure scripts won't get reformatted properly. 

When you open up the file (`vim`), while in command mode (not edit mode)- type gg=G.  That's without hitting the ":" first.   Literally,  hit 'g', then 'g' again, followed by '=' and *SHIFT*+'g'.  

It has saved me quite a bit of headaches, especially from people who insist tab should be two literal spaces.  /smh

Granted, you can map this to a fn key.  E.g. in .vimrc, have an entry somehwhere on a line showing (this is untested):

map <F5> mzgg=G`z<CR>

But, as I said, on over 50 machines so I'm not about to maintain 50 .vimrc files.  :)  Sometimes it's simpler to just remember the shortcut.


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…