In some circumstances, setmode(3) may call umask(2) twice to retrieve
the current mode and then restore it. Between calls, the process will
have a umask of 0.
Details
Details
- Reviewers
markj wblock emaste - Group Reviewers
manpages - Commits
- rS350330: MFC r350116:
rS350329: MFC r350116:
rS350116: Document that setmode(3) is not thread safe.
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Not Applicable - Unit
Tests Not Applicable