I realised I never got back to this. Thanks Marcelo for that - I'll look
into it.
Best,
Nicky
On Sat, 31 Oct 2020 at 16:36, Marcelo Diop-Gonzalez
wrote:
> Hey, I think this is because the process's umask is changing the mode. In
> fs/namei.c in the function lookup_open() there's this bit:
>
>
Hey, I think this is because the process's umask is changing the mode. In
fs/namei.c in the function lookup_open() there's this bit:
if (!IS_POSIXACL(dir->d_inode))
mode &= ~current_umask();
the open(2) and umask(2) manpages will explain how to deal with it
-Marcelo
On Sat, Oct
Hi folks,
I hope it's OK to ask this question here. I'm reading The Linux
Programming Interface and am beginning to get to grips with the file
oriented system calls.
I have a program that calls open to create a file, specifying the mode
flags for owner, group, other read and write. The file is
