lusermod(1)

πŸ’– lusermod(1) β€” the glow-up page for your users πŸ’–

okay bestie, so this is lusermod, straight out of the General Commands Manual, and it's literally the makeover artist for user accounts. think of it as ✨editing✨ a person's whole vibe in the user database. no cap.


🌸 NAME 🌸

lusermod β€” modify an user πŸ’…


✨ SYNOPSIS ✨

lusermod [OPTION]... user

πŸ¦‹ DESCRIPTION πŸ¦‹

so basically? it modifies the user with name user. that's the whole thing. the rest is just how you do it. πŸŽ€


πŸ’œ OPTIONS πŸ’œ

  • -c, --gecos=gecos β€” sets the user's GECOS field to gecos. ngl the GECOS field is the classic little spot where the system traditionally keeps the user's real name and other info about them. 🫢
  • -d, --directory=directory β€” sets the user's home directory to directory. new address, who dis. 🏠
  • -g, --gid=gid β€” changes the user's primary group ID to gid. heads up tho: if a group with ID gid does not exist, it prints a warning but does the operation anyway. so like… it tells you, and then does it regardless. iconic chaos. 😭
  • -i, --interactive β€” asks you all the questions when connecting to the user database, even if default answers are already set up in libuser configuration. very "let's talk about it" energy. πŸ™ˆ
  • -L, --lock β€” locks the user's account. this prevents logging in using the user's password. πŸ”’
  • -l, --login=name β€” renames the user to name. rebranding, but for a person. πŸ‘‘
  • -m, --movedirectory β€” after changing the user's home directory (with the -d option), it moves the old home directory to the new location. packing day fr fr. πŸ“¦
  • -P, --plainpassword=password β€” sets the user's password to password. lowkey important: the password can be viewed while lusermod is running, using tools like ps(1). so… everyone at the party can see it. πŸ’€
  • -p, --password=encrypted β€” sets the user's password to the password represented by the hash encrypted. also important: that hash can be viewed while lusermod is running, using tools such as ps(1). same vibe, still exposed. 😭
  • -s, --shell=shell β€” sets the user's login shell to shell. pick your fighter. 🐚
  • -U, --unlock β€” unlocks the user's account. welcome back bestie. πŸ”“
  • -u, --uid=uid β€” changes the user's user ID to uid. new number, same queen. πŸ”’
  • --commonname=name β€” sets the user's common name to name. this attribute is only supported in some backends (e.g. LDAP), and its support may have further limitations (e.g. LDAP schema rules). so like, backend-dependent, iykyk. 🌈
  • --givenname=name β€” sets the user's given name to name. this attribute is only supported in some backends (e.g. LDAP), and its support may have further limitations (e.g. LDAP schema rules). 🌸
  • --homephone=phone β€” sets the user's home telephone number to phone. this attribute is only supported in some backends (e.g. LDAP), and its support may have further limitations (e.g. LDAP schema rules). ☎️
  • --roomnumber=room β€” sets the user's room number to room. this attribute is only supported in some backends (e.g. LDAP), and its support may have further limitations (e.g. LDAP schema rules). πŸšͺ
  • --surname=name β€” sets the user's surname to name. this attribute is only supported in some backends (e.g. LDAP), and its support may have further limitations (e.g. LDAP schema rules). πŸ’«
  • --telephonenumber=phone β€” sets the user's telephone number to phone. this attribute is only supported in some backends (e.g. LDAP), and its support may have further limitations (e.g. LDAP schema rules). πŸ“ž
quick note bestie: every one of those --commonname, --givenname, --homephone, --roomnumber, --surname and --telephonenumber ones is only supported in some backends (e.g. LDAP), and even then the support may have further limitations (e.g. LDAP schema rules). so don't come for me if your backend says no. 🧚

⭐ EXIT STATUS ⭐

the exit status is 0 on success, and nonzero on error. simple as that. ✨


this page came from libuser, dated 2009-12-11, and it's the lusermod(1) page from the General Commands Manual. ty for reading bestie, go modify some users, and remember: vibe check your backends first πŸ’–πŸ¦‹πŸŽ€