umask sets the attributes for the entire process by default, also when creating a file we can give it the parameters we need. If you can always specify them, then why bother with this team? For example, set umask(022) and then skip this parameter in open(...) ? Perhaps the example is poorly formulated, but I do not fully understand the purpose of this command.

  • Already there was such a question earlier, was it really difficult to search first, before asking again? stackoverflow.com/questions/6198623/when-is-umask-useful - And
  • @And seen. But I cannot improve the level of English at least until I understand it through the translate for the day. Everything is bad with him. So please explain in Russian. - Bambaleila
  • If you are given an exhaustive answer, mark it as correct (a daw opposite the selected answer). - Nicolas Chabanovsky ♦

1 answer 1

umask sets attributes for the entire process by default.

That's right - DEFAULT!

they can always be specified

But only in the open() system call!

why bother with this team?

And how to be in this situation:

 system("cp file1 file2");

This is where the default permissions are useful.