code: def _pre_mongod_server_start(server, options_override=None):
      
  
      lock_file_path = server.get_lock_file_path()
  
      no_journal = (server.get_cmd_option("nojournal") or
                    (options_override and "nojournal" in options_override))
      if (os.path.exists(lock_file_path) and
              server.is_arbiter_server() and
              no_journal):
  
          log_warning("WARNING: Detected a lock file ('%s') for your server '%s'"
                      " ; since this server is an arbiter, there is no need for"
                      " repair or other action. Deleting mongod.lock and"
                      " proceeding..." % (lock_file_path, server.id))
          try:
              os.remove(lock_file_path)
          except Exception, e:
              log_exception(e)
              raise MongoctlException("Error while trying to delete '%s'. "
                                      "Cause: %s" % (lock_file_path, e))
docs: Does necessary work before starting a server
  
      1- An efficiency step for arbiters running with --no-journal
          * there is a lock file ==>
          * server must not have exited cleanly from last run, and does not know
            how to auto-recover (as a journalled server would)
          * however:  this is an arbiter, therefore
          * there is no need to repair data files in any way ==>
          * i can rm this lockfile and start my server