Linux Programming Interface: Chapter 4

Jon Schipp
Quiz by Jon Schipp, updated more than 1 year ago
Jon Schipp
Created by Jon Schipp over 5 years ago
17
0

Description

Chapter 4 of the Linux Programming Interface book by Michael Kerrisk

Resource summary

Question 1

Question
The three standard file descriptor's are opened on the program's behalf by the [blank_start]______[blank_end]
Answer
  • shell

Question 2

Question
The O_CREAT flag to open(2) can be used in conjunction with [blank_start]______[blank_end] flag to create a file exclusively (atomically).
Answer
  • O_EXCL

Question 3

Question
The [blank_start]_____[blank_end] flag to open(2) prevents dereferencing symbolic links and its absence is the cause of some vulnerabilities in privileged programs.
Answer
  • O_NOFOLLOW

Question 4

Question
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 [blank_start]_____[blank_end] flag to open(2) closes them for you.
Answer
  • O_CLOEXEC

Question 5

Question
The [blank_start]____[blank_end] is a directory in the proc filesystem which contains information about each file descriptor opened by a program.
Answer
  • fdinfo

Question 6

Question
The two size types in the function prototype translate to what standard C types (in order of appearance)?
Answer
  • signed integer type, unsigned integer type
  • unsigned integer type, signed integer type
  • integer type, signed integer type
  • signed integer type, integer type

Question 7

Question
Which of the following flags to open(2) are not a part of the Single UNIX Specification?
Answer
  • O_DIRECT
  • O_LARGEFILE
  • O_NOATIME
  • O_ASYNC
  • O_DSYNC
  • O_SYNC

Question 8

Question
The creat(2) system call is equivalent to this open(2) system call
Answer
  • 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);

Question 9

Question
During which system calls does the kernel set the file offset or file pointer?
Answer
  • read()
  • write()
  • lseek()
  • open()
  • close()
  • creat()

Question 10

Question
During which system calls does the kernel update a pointer called the file offset or file pointer.
Answer
  • read()
  • write()
  • close()
  • creat()
  • lseek()
  • open()

Question 11

Question
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
Answer
  • True
  • False

Question 12

Question
The return value from a successful lseek() is a?
Answer
  • file offset
  • number of seeked bytes
  • number of read bytes

Question 13

Question
Writing to a file hole performs what action?
Answer
  • 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
Show full summary Hide full summary

Similar

Computing Hardware - CPU and Memory
ollietablet123
SFDC App Builder 2
Parker Webb-Mitchell
Intake7 BIM L1
Stanley Chia
Data Types
Jacob Sedore
CCNA Answers – CCNA Exam
Abdul Demir
Software Processes
Nurul Aiman Abdu
Design Patterns
Erica Solum
Abstraction
Shannon Anderson-Rush
Spyware
Sam2
Database Replication
Michael Mahfouz
Data Analytics
anelvr