The three standard file descriptor's are opened on the program's behalf by the
The O_CREAT flag to open(2) can be used in conjunction with flag to create a file exclusively (atomically).
The flag to open(2) prevents dereferencing symbolic links and its absence is the cause of some vulnerabilities in privileged programs.
When file descriptors are open in a program and a fork(2) and exec(2) happen before closing them - the descriptors can end up being passed to a new program. The flag to open(2) closes them for you.
The is a directory in the proc filesystem which contains information about each file descriptor opened by a program.
The two size types in the function prototype translate to what standard C types (in order of appearance)?
signed integer type, unsigned integer type
unsigned integer type, signed integer type
integer type, signed integer type
signed integer type, integer type
Which of the following flags to open(2) are not a part of the Single UNIX Specification?
O_DIRECT
O_LARGEFILE
O_NOATIME
O_ASYNC
O_DSYNC
O_SYNC
The creat(2) system call is equivalent to this open(2) system call
fd = open(pathname, O_WRONLY | O_CREAT | O_TRUNC, mode);
fd = open(pathname, O_WRONLY | O_TRUNC, mode);
fd = open(pathname, O_WRONLY | O_CREAT |O_APPEND, mode);
fd = open(pathname, O_WRONLY | O_APPENDT | O_TRUNC, mode);
During which system calls does the kernel set the file offset or file pointer?
read()
write()
lseek()
open()
close()
creat()
During which system calls does the kernel update a pointer called the file offset or file pointer.
With file holes the file system doesn’t allocate any disk blocks for a hole until, at some later point, data is written into it
The return value from a successful lseek() is a?
file offset
number of seeked bytes
number of read bytes
Writing to a file hole performs what action?
Allocating disk blocks but not writing null bytes in them
Writing null bytes but not allocating disk blocks
Allocating disk blocks and writing null byes within the blocks
Neither, system assumes null byte are there
Por favor, aguarde! Carregando...