oddjobd-mkhomedir.conf(5)

💖 oddjobd-mkhomedir.conf(5) 💖

okay bestie, so this is a File Formats Manual page for oddjobd-mkhomedir.conf, and it's basically the bouncer that decides how much of the mkhomedir machinery anyone's allowed to touch. it's giving ✨limited access✨ and honestly? iconic.

🌸 NAME 🌸

oddjobd-mkhomedir.conf — allow limited use of the mkhomedir functions 🫶

✨ DESCRIPTION ✨

so the file we're talking about is /etc/oddjobd.conf.d/oddjobd-mkhomedir.conf, and the tea is that it's typically processed along with all the other files chillin' in the /etc/oddjobd.conf.d directory. like, it's not out here alone, it's part of a whole squad. 💅

and then — the mkhomedir helper itself? it accepts these options, no cap:

• -q — bestie, it just… doesn't talk. it refrains from outputting the usual Creating home directory... message when it creates a home directory. silent. mysterious. main character. 🤫
• -n — only creates the home directory and does NOT populate it using the contents of the skeleton directory. it's giving bare bones, literally. 💀
• -s — overrides the location of the skeleton directory (by default it's /etc/skel). so if your skeleton lives somewhere else, this is your moment. 🦋
• -u — specifies a umask whose bits get masked off of the contents of the skeleton directory while they're being copied into the user's brand-new home directory. and the default? it's read from /etc/login.defs by taking the HOME_MODE and UMASK values, in this order. first found value persists. so whichever one shows up first wins, periodt. 👑

ngl, that "first found value persists" thing is important — don't be out here assuming it checks both, because it does not. 🙈

👀 SEE ALSO 👀

• oddjob.conf(5)
• login.defs(5)

and that's the whole vibe, bestie — slay 💖✨ this was the oddjob Manual, dated 17 June 2014, and we're signing off from oddjobd-mkhomedir.conf(5). go forth and make them home directories responsibly. 🎀🦋🌸