We used to check for the lock file before opening sockets. This produced a better error message when inadvertently starting two copies of mongod pointing to the same dbpath and using the same ports.
The bind error message isn't as obvious because we don't know what process is sharing the port; with the lock file, at least we know that mongod is conflicting with another mongod.