POSIX-UMASK(1)

✨ POSIX-UMASK(1) — posix-umask, but make it bestie ✨

okay so this is the General Commands Manual page for posix-umask — yes, that POSIX-UMASK(1) girlie 💅.

💖 NAME 💖

posix-umask — changes the file mode creation mask, then executes a program. no cap, that's the whole vibe.

✨ SYNOPSIS ✨

posix-umask [-S] [mask] [prog...]

🦋 DESCRIPTION 🦋

When you call posix-umask with no argument, it prints the value of the file mode creation mask of the invoking process, then exits 0. that's it, that's the behavior 💖.

When you give it a mask argument, posix-umask changes its file mode creation mask. then, if prog... is not empty, it exec(3)s into it. main character energy: it doesn't stick around, it becomes the program 🫶.

posix-umask interprets mask as specified by the POSIX specification for a ‘umask’ external utility [1].

When execline has been configured with the --enable-pedantic-posix option, the umask command is a symbolic link to it. so scripts calling umask will use posix-umask. when this configuration option has not been given, umask is a symbolic link to execline-umask(1). lowkey important 😭.

posix-umask fully conforms to the POSIX specification [1]. when prog... is not empty, the behaviour of a ‘umask’ utility is not specified by POSIX, so posix-umask extends the spec to be actually useful and usable in an execline program with the same interface as the regular execline ‘umask’ command. periodt.

🫶 okay but listen: nobody ever executes or needs the external version (i.e. not a shell builtin) of the POSIX ‘umask’ command. compared to execline's regular umask binary, execline-umask(1), posix-umask is uselessly bloated and slow. the only reason it exists is that some distributions refuse to package execline correctly unless it is strictly POSIX-compliant; the --enable-pedantic-posix configure option is there to satisfy their requirements. iconic packaging drama, honestly 💀.

🌈 SEE ALSO 🌈

• emptyenv(1), envfile(1), exec(1), execline-cd(1), execline-umask(1), exit(1), export(1), fdblock(1), fdclose(1), fdmove(1), fdreserve(1), fdswap(1), getcwd(1), getpid(1), heredoc(1), piperw(1), posix-cd(1), redirfd(1), trap(1), tryexec(1), unexport(1), wait(1), withstdinas(1)
• [1] — https://pubs.opengroup.org/onlinepubs/9799919799/utilities/umask.html

also, this man page is ported from the authoritative documentation at: https://skarnet.org/software/execline/posix-umask.html 💜

🎀 AUTHORS 🎀

• Laurent Bercot
• Alexis <flexibeast@gmail.com> (man page port)

later bestie — this page is from Debian, dated February 14, 2021 💖✨