[plug] Re: useradd error

[Matt Kemner]

On Thu, 5 Oct 2000, Support wrote:

> thanks  got it fixed  it was the lock file 
>  still doesnt explian why it did it 

If a lockfile exists it means either a previous useradd is still running
- which is why I said to check the process listing first, because someone
else may have been halfway through adding a user from another telnet
session, in which case removing the lock file is a bad idea, because if
they do continue to add that user, your user will be overwritten - or a
previous useradd died due to an error and didn't clean up after itself.

 - Matt