title: Grunt Serve watch throws EBUSY warning over mongod.lock
body: <p>I have an app I am building using the full stack angular yeoman generator. I start mongod passing the path to my data folder:</p>
  
  <p>[my local path]/[my new app name]/server/data</p>
  
  <p>In my app i then run the grunt serve task. The app boots up correctly however the watch task throws a warning and then fails to do any live reloads it also causes the app in the browser to continuously load.</p>
  
  <p>The warning I get it:</p>
  
  <p>EBUSY, resource busy or locked "[my local path]/[my new app name]/server/data/mongod.lock"</p>
  
  <p>Not sure what is going on everything I have read about this suggests that I have multiple instances open trying to access the DB but I am pretty sure I do not.</p>
  
  <p>L</p>