When adding a new user account in linuxconf, if you type in a bad home directory where the directory other than the base directory doesn't exist, the error shows up during the password creation, without any clue to what happened. Example: I entered in for a user account: Login name: oracle Full name: Oracle Database Admin group: dba Home directory(opt): /oracle/oracle But the /oracle directory didn't exist. Since it was supposed to be /oraclesrv/oracle. Notice that the mistake was at a higher directory level and not at the leaf level. Instead of giving me an error message that tells me something is wrong with the home directory, it gave me the following message: smbpasswd: User "oracle" was not found in the system password file. And since I didn't realize that I was entering the wrong home directory, this threw me for a loop. This looks like it does something with samba by the "smbpasswd" message, and I don't know what would have happened if I didn't have samba running. It would be nice to have a proper error message, but I would not go so far to create the full directory path, since a typo can cause a pain in the butt if you don't realize that the path was wrong and everthing went smoothly.
Closing because we don't ship linuxconf anymore
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.