SlideShare una empresa de Scribd logo
1 de 27
Descargar para leer sin conexión
Fundamentals

  CIS 552
Fundamentals

Low-level I/O (read/write using system calls)
 Opening/Creating files
 Reading & Writing files
 Moving around in files
 file descriptors

Program Creation and Execution
 exec family of system calls
 using fork() to create processes
 exiting processes
 process termination
Low-level I/O

Unix System Calls can be used to:
 Open/Create Files
 Read & Write files
 Move around in files

System calls work with file descriptors
 A file descriptor is an int that represents a file/device
 File descriptors are allocated by the system
      Limited number of file descriptors available
      0 is stdin, 1 is stdout, 2 is stderr; these are automatically allocated
       and opened when a program begins
Opening/Creating Files

open(<file/device name>,<how to open>[,<mode>])
 <file/device name> is a C-string, exactly as in the C++ fstream member
  function open()
 <how to open> is an int, usually specified with a constant defined in
  fcntl.h. The values may be combined using a logical OR ( | ), allowing
  every possible way of opening a file (examples on next slide)
       Detail on this appears on the next slide
 <mode> is an optional third argument that is specified only if the file is
  created. It is a three digit octal number representing the permissions to be
  set on the file.
 a file descriptor (of type int) is returned on success; otherwise –1 is
  returned.
Specifying How a File is to be Opened
                    File Access
 You must specify how the file is to be accessed. Exactly one of these
  values must appear in the 2nd argument of open():
 O_RDONLY
       The file is opened for reading only. If the file doesn’t exist, and the create
        option (next slide) isn’t specified, open() will fail (note that it is not
        ordinary to open a file to be read with the create option specified)
 O_WRONLY
       The file is to be opened for writing only. If the file doesn’t exist, and the
        create option is not specified, or if the file does exist, and the create option
        is specified along with the fail if file exists option, open() will fail.
 O_RDWR
       The file is opened for full access. Errors specified above can occur,
        however.
 If none of these are specified, open() can succeed, but nothing can be
  done to the file. (See open2.c in the demo directory)
Specifying How a File is to be Opened
              File Opening Options
The following are used to further specify how a file is opened. They are
combined with the access and possibly each other:
O_APPEND
       all access is at end of file
O_CREAT
       create file if it doesn’t exist (does not cause failure if file exists).
        Use a third argument to specify mode.
O_TRUNC
       Destroy the existing contents of the file, if it exists.
O_EXCL
       When combined with O_CREAT, causes open() to fail if the file
        already exists.
Specifying How a File is to be Opened
               Exercises/Examples
 Open a file named abc.txt for writing, only if it exists. If it does, the
  present contents should be preserved, and writing should occur after the
  present contents.
 Give an open() command equivalent to the C++ command
  Dest.open(“abc.txt”), where Dest is an ofstream
 Give an open command that opens a file abc.txt for writing only if it
  doesn’t already exist.
 Give command(s), to open a file abc.txt for writing. If abc.txt exists, the
  user should be prompted, and then the file opened for writing only if the
  user answers affirmatively to a prompt to overwrite the file. Otherwise,
  the file is created.
 Repeat the previous exercise, using C++
Low-level Reading and Writing

Using low-level (system) calls, I/O can only be accomplished via a buffer,
  whose size is determined by the user.
 small buffer requires more device accesses, slowing program; some
  systems override with their own buffer

Commands:
 read(<file descriptor>,<address of buffer>,<# bytes to read>)
 write(<file descriptor>,<address of buffer>,<# bytes to read>)
       value returned is # bytes read; 0 => eof (read only), -1 => error
Moving Around in A File
         Low-level access via File Descriptor

lseek(<file descriptor>,<amount>,<relativity>)
where
 <file descriptor> is a file descriptor of an open file
 <amount> is the number of bytes to move the file descriptor...
 <relativity> is the point from which the operation takes place
       SEEK_SET (0) is start of file
       SEEK_CUR (1) is current position
       SEEK_END (2) is end of file
            if <amount> is positive with this option, there will be a hole in the file.
 the return value is the new offset in the file
Exercises

 Give an lseek() command to find the present offset in a file
 How is the present offset in a file found when the file is
  accessed via a file pointer?
 Give a loop to write the values 1-100 in the same spot of a
  text file.
 Why is the seek command basically worthless in a text file,
  except to go to the beginning or end of the file?
Program Creation and Execution

   exec family of system calls
   using fork() to create processes
   process termination
   waiting for processes
exec Family of System Calls

Execute a program using one of the exec calls
 Six exec functions
 Can provide a list and have function build argv[] vector or provide the
  vector itself
 Can specify path to program or use path variable to find it
 Can use present environment, or specify new environment
       environment defined by setenv items. Type set at Unix prompt to see
        environment
 called program occupies environment of caller (takes its pid, as new
  process isn’t created). Only replaces text, data, heap, and stack segments
  of caller of exec
 execs are the only function calls that don’t return
execl & execv

execl
 give pathname to file (incl. name) as 1st argument
 Follow with list of command line arguments; executable 1st
      this list is used to build the argv vector passed to the called program
      executable name is in argv[0]
 last argument must be null char *
execv
 give pathname to file (incl. name) as 1st argument
 Follow with null-terminated argv vector
execlp & execvp

execlp
 give filename as 1st argument; path environment variable is
  used to find executable
 Follow with list of command line arguments; executable 1st
      this list is used to build the argv vector passed to the called program
 last argument must be null char *
execvp
 give filename as 1st argument; path used
 Follow with null-terminated argv vector
Exercise

   Suppose a program X is executed whose
   purpose is to call another program Y whose
   name and command-line arguments are
   passed in to X as command-line arguments.
1. Write an execlp and an execvp command,
   as they would appear in X, to execute Y.
2. What problem could arise if we choose to
   use execl or execv?
Process Creation
                      fork & vfork
  Processes can only be created using a fork
  command
 fork is called once, but returns twice
      parent calls fork, value is returned to each of parent and
       child
 created process is called the child
 existing process is the parent
 Process identifier (pid) is used to distinguish
  between parent and child
      Every process has a unique pid in the system
fork

 Called once, returns twice; return type is pid_t, unsigned int type for
  pids
       Parent receives child’s pid as return value of fork
    
        child receives 0 as return value from fork
       Order of execution depends on scheduling algorithm of system.
            Order can be controlled; important if there is dependence between parent and
             child
 Child and parent execute in their own environments
       Child gets copy of parent’s environment (including data space) as it is at
        time of fork
            If parent has file open, child gets copy of file pointers or descriptors
            If parent’s stdout (cout) is redirected before fork, child output to stdout is also
             redirected
Child Process’ Inheritance

   user id, group id
   controlling terminal
   current working directory
   root directory
   file mode creation mask
   signal mask (later) and dispositions
   close-on-exec flag for open file descriptors
   environment
   attached shared memory segments
   resource limits
Items That Distinguish
                  Parent From Child
 Return value from fork
 unique pid
 different parent pid (ppid)
       child’s ppid is the parent’s pid
       parent’s pid stays same
   certain time values reset in child
   parent’s file locks aren’t inherited
   pending alarms are not inherited
   pending signals in parent aren’t inherited
vfork


 Maintained for compatability, vfork is not often used
      Some systems implement it as a fork
 Child executes first. Parent doesn’t resume until child either
  exits (via call of exit() or _exit()) or uses exec to start
  another program.
 The child is a separate process, but it shares the parent’s
  data space. vforkdemo.c shows that this is the case
vforkdemo.c
#include <stdio.h>
#include <sys/types.h>
#include <unistd.h>
                                  •Parent output is same as child’s
int glob ;
int                               •If separate data spaces, parent wouldn’t experience ++
main(void){
                                  operations
 int var;
 pid_t pid;
 glob = 10; var = 20;
 printf("before vforkn");

 if (vfork()== 0 ) {
   sleep(1);
   glob++;
   var++;
   printf("child glob= %d var= %dn", glob, var);
   _exit(0); // what if this is just exit()?
 }
 else {
  printf("parent glob= %d var= %dn", glob, var);
 }
}
When a process terminates...

 Its parent is informed via a SIGCHLD signal
 If its parent doesn’t “collect” it, it becomes a zombie
  process (next slide)
 If its parent has already terminated, it is inherited by the init
  process (pid 1), which “collects” it using a wait operation (2
  slides hence).
      All processes must have an identifiable (by pid) parent
 It is able to provide minimal information to its parent when
  it comes to “collect” it
Zombie Process

A zombie is a process that has terminated, but hasn’t
  been “collected” by its parent
 The system frees most of the resources associated
  with this terminated process, e.g. closing open files
  and freeing memory,and minimally maintains:
      process id
      CPU time used
      termination status
wait operations

A terminated process’ information is “collected” via a
  call of a wait operation by its parent
 Operations:
      wait
          blocks the calling process until a child process terminates,
           returning the child’s pid.
             If caller has no children, wait immediately returns –1 (error)
          the termination status (return value) of the child may be obtained
           via the argument
      waitpid
        permits a caller to wait for a particular child, identified by its pid
        can be configured to not block if the child is active
Process Termination

Normal:
1. main contains return statement
2. call exit
3. call _exit
Abnormal:
1. Process aborts itself
2. Process receives a signal (e.g. division by 0)
exit() vs._exit()

 exit() causes a process to terminate.
      stdio funtion fclose is applied to all open streams
      the argument is the exit status
          exit status becomes termination status when exit() calls _exit()
 _exit is a Unix specific command
      the process terminates immediately without any cleanup
          see vfork examples
 If a process doesn’t explicitly specify exit status via
  a call to exit() or _exit(), the process’ termination
  status will be undefined
Exercises

1. What can happen if a process calls exit
   while writing to a buffered output stream?
2. Write code guaranteed to create a zombie
   process.
3. Write code that will cause a process to be
   inherited by the init process.

Más contenido relacionado

La actualidad más candente (18)

File Handling and Command Line Arguments in C
File Handling and Command Line Arguments in CFile Handling and Command Line Arguments in C
File Handling and Command Line Arguments in C
 
srgoc
srgocsrgoc
srgoc
 
Unit 5 dwqb ans
Unit 5 dwqb ansUnit 5 dwqb ans
Unit 5 dwqb ans
 
Python File Handling | File Operations in Python | Learn python programming |...
Python File Handling | File Operations in Python | Learn python programming |...Python File Handling | File Operations in Python | Learn python programming |...
Python File Handling | File Operations in Python | Learn python programming |...
 
Java Programming - 06 java file io
Java Programming - 06 java file ioJava Programming - 06 java file io
Java Programming - 06 java file io
 
Python Session - 2
Python Session - 2Python Session - 2
Python Session - 2
 
python.ppt
python.pptpython.ppt
python.ppt
 
Python-files
Python-filesPython-files
Python-files
 
web programming UNIT VIII python by Bhavsingh Maloth
web programming UNIT VIII python by Bhavsingh Malothweb programming UNIT VIII python by Bhavsingh Maloth
web programming UNIT VIII python by Bhavsingh Maloth
 
web programming Unit VI PPT by Bhavsingh Maloth
web programming Unit VI PPT  by Bhavsingh Malothweb programming Unit VI PPT  by Bhavsingh Maloth
web programming Unit VI PPT by Bhavsingh Maloth
 
CORE JAVA-1
CORE JAVA-1CORE JAVA-1
CORE JAVA-1
 
Let’s Learn Python An introduction to Python
Let’s Learn Python An introduction to Python Let’s Learn Python An introduction to Python
Let’s Learn Python An introduction to Python
 
intro unix/linux 10
intro unix/linux 10intro unix/linux 10
intro unix/linux 10
 
Spsl unit1
Spsl   unit1Spsl   unit1
Spsl unit1
 
CORE JAVA-2
CORE JAVA-2CORE JAVA-2
CORE JAVA-2
 
Introduction to Python Pandas for Data Analytics
Introduction to Python Pandas for Data AnalyticsIntroduction to Python Pandas for Data Analytics
Introduction to Python Pandas for Data Analytics
 
Python for Beginners(v1)
Python for Beginners(v1)Python for Beginners(v1)
Python for Beginners(v1)
 
CORE JAVA
CORE JAVACORE JAVA
CORE JAVA
 

Similar a 02 fundamentals

Similar a 02 fundamentals (20)

File management
File managementFile management
File management
 
Systemcall1
Systemcall1Systemcall1
Systemcall1
 
18CS56-UP-Module 3.pptx
18CS56-UP-Module 3.pptx18CS56-UP-Module 3.pptx
18CS56-UP-Module 3.pptx
 
Linux 系統程式--第一章 i/o 函式
Linux 系統程式--第一章 i/o 函式Linux 系統程式--第一章 i/o 函式
Linux 系統程式--第一章 i/o 函式
 
File handling C program
File handling C programFile handling C program
File handling C program
 
File Handling in Java.pdf
File Handling in Java.pdfFile Handling in Java.pdf
File Handling in Java.pdf
 
working with files
working with filesworking with files
working with files
 
FILES IN C
FILES IN CFILES IN C
FILES IN C
 
File Handling
File HandlingFile Handling
File Handling
 
File Handling
File HandlingFile Handling
File Handling
 
GE3151 PSPP UNIT V QUESTION BANK.docx.pdf
GE3151 PSPP UNIT V QUESTION BANK.docx.pdfGE3151 PSPP UNIT V QUESTION BANK.docx.pdf
GE3151 PSPP UNIT V QUESTION BANK.docx.pdf
 
Write a shell in CC++Prefer this to be written in C++Your s.pdf
Write a shell in CC++Prefer this to be written in C++Your s.pdfWrite a shell in CC++Prefer this to be written in C++Your s.pdf
Write a shell in CC++Prefer this to be written in C++Your s.pdf
 
Unit5
Unit5Unit5
Unit5
 
11_UNIX_Processes_Including_Select.ppt
11_UNIX_Processes_Including_Select.ppt11_UNIX_Processes_Including_Select.ppt
11_UNIX_Processes_Including_Select.ppt
 
Unix-module3.pptx
Unix-module3.pptxUnix-module3.pptx
Unix-module3.pptx
 
These questions will be a bit advanced level 2
These questions will be a bit advanced level 2These questions will be a bit advanced level 2
These questions will be a bit advanced level 2
 
Chapter10
Chapter10Chapter10
Chapter10
 
Basics of file handling
Basics of file handlingBasics of file handling
Basics of file handling
 
basics of file handling
basics of file handlingbasics of file handling
basics of file handling
 
Linux Programming
Linux ProgrammingLinux Programming
Linux Programming
 

Último

3.21.24 The Origins of Black Power.pptx
3.21.24  The Origins of Black Power.pptx3.21.24  The Origins of Black Power.pptx
3.21.24 The Origins of Black Power.pptxmary850239
 
Human-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesHuman-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesMohammad Hassany
 
How to Solve Singleton Error in the Odoo 17
How to Solve Singleton Error in the  Odoo 17How to Solve Singleton Error in the  Odoo 17
How to Solve Singleton Error in the Odoo 17Celine George
 
Prescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxPrescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxraviapr7
 
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...Nguyen Thanh Tu Collection
 
Practical Research 1 Lesson 9 Scope and delimitation.pptx
Practical Research 1 Lesson 9 Scope and delimitation.pptxPractical Research 1 Lesson 9 Scope and delimitation.pptx
Practical Research 1 Lesson 9 Scope and delimitation.pptxKatherine Villaluna
 
How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17Celine George
 
Patterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxPatterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxMYDA ANGELICA SUAN
 
HED Office Sohayok Exam Question Solution 2023.pdf
HED Office Sohayok Exam Question Solution 2023.pdfHED Office Sohayok Exam Question Solution 2023.pdf
HED Office Sohayok Exam Question Solution 2023.pdfMohonDas
 
CapTechU Doctoral Presentation -March 2024 slides.pptx
CapTechU Doctoral Presentation -March 2024 slides.pptxCapTechU Doctoral Presentation -March 2024 slides.pptx
CapTechU Doctoral Presentation -March 2024 slides.pptxCapitolTechU
 
Clinical Pharmacy Introduction to Clinical Pharmacy, Concept of clinical pptx
Clinical Pharmacy  Introduction to Clinical Pharmacy, Concept of clinical pptxClinical Pharmacy  Introduction to Clinical Pharmacy, Concept of clinical pptx
Clinical Pharmacy Introduction to Clinical Pharmacy, Concept of clinical pptxraviapr7
 
AUDIENCE THEORY -- FANDOM -- JENKINS.pptx
AUDIENCE THEORY -- FANDOM -- JENKINS.pptxAUDIENCE THEORY -- FANDOM -- JENKINS.pptx
AUDIENCE THEORY -- FANDOM -- JENKINS.pptxiammrhaywood
 
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptxSandy Millin
 
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxPractical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxKatherine Villaluna
 
The basics of sentences session 10pptx.pptx
The basics of sentences session 10pptx.pptxThe basics of sentences session 10pptx.pptx
The basics of sentences session 10pptx.pptxheathfieldcps1
 
M-2- General Reactions of amino acids.pptx
M-2- General Reactions of amino acids.pptxM-2- General Reactions of amino acids.pptx
M-2- General Reactions of amino acids.pptxDr. Santhosh Kumar. N
 
General views of Histopathology and step
General views of Histopathology and stepGeneral views of Histopathology and step
General views of Histopathology and stepobaje godwin sunday
 
What is the Future of QuickBooks DeskTop?
What is the Future of QuickBooks DeskTop?What is the Future of QuickBooks DeskTop?
What is the Future of QuickBooks DeskTop?TechSoup
 

Último (20)

3.21.24 The Origins of Black Power.pptx
3.21.24  The Origins of Black Power.pptx3.21.24  The Origins of Black Power.pptx
3.21.24 The Origins of Black Power.pptx
 
Personal Resilience in Project Management 2 - TV Edit 1a.pdf
Personal Resilience in Project Management 2 - TV Edit 1a.pdfPersonal Resilience in Project Management 2 - TV Edit 1a.pdf
Personal Resilience in Project Management 2 - TV Edit 1a.pdf
 
Human-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming ClassesHuman-AI Co-Creation of Worked Examples for Programming Classes
Human-AI Co-Creation of Worked Examples for Programming Classes
 
How to Solve Singleton Error in the Odoo 17
How to Solve Singleton Error in the  Odoo 17How to Solve Singleton Error in the  Odoo 17
How to Solve Singleton Error in the Odoo 17
 
Prescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptxPrescribed medication order and communication skills.pptx
Prescribed medication order and communication skills.pptx
 
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
CHUYÊN ĐỀ DẠY THÊM TIẾNG ANH LỚP 11 - GLOBAL SUCCESS - NĂM HỌC 2023-2024 - HK...
 
Practical Research 1 Lesson 9 Scope and delimitation.pptx
Practical Research 1 Lesson 9 Scope and delimitation.pptxPractical Research 1 Lesson 9 Scope and delimitation.pptx
Practical Research 1 Lesson 9 Scope and delimitation.pptx
 
How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17How to Use api.constrains ( ) in Odoo 17
How to Use api.constrains ( ) in Odoo 17
 
Patterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptxPatterns of Written Texts Across Disciplines.pptx
Patterns of Written Texts Across Disciplines.pptx
 
HED Office Sohayok Exam Question Solution 2023.pdf
HED Office Sohayok Exam Question Solution 2023.pdfHED Office Sohayok Exam Question Solution 2023.pdf
HED Office Sohayok Exam Question Solution 2023.pdf
 
CapTechU Doctoral Presentation -March 2024 slides.pptx
CapTechU Doctoral Presentation -March 2024 slides.pptxCapTechU Doctoral Presentation -March 2024 slides.pptx
CapTechU Doctoral Presentation -March 2024 slides.pptx
 
Clinical Pharmacy Introduction to Clinical Pharmacy, Concept of clinical pptx
Clinical Pharmacy  Introduction to Clinical Pharmacy, Concept of clinical pptxClinical Pharmacy  Introduction to Clinical Pharmacy, Concept of clinical pptx
Clinical Pharmacy Introduction to Clinical Pharmacy, Concept of clinical pptx
 
AUDIENCE THEORY -- FANDOM -- JENKINS.pptx
AUDIENCE THEORY -- FANDOM -- JENKINS.pptxAUDIENCE THEORY -- FANDOM -- JENKINS.pptx
AUDIENCE THEORY -- FANDOM -- JENKINS.pptx
 
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
2024.03.23 What do successful readers do - Sandy Millin for PARK.pptx
 
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptxPractical Research 1: Lesson 8 Writing the Thesis Statement.pptx
Practical Research 1: Lesson 8 Writing the Thesis Statement.pptx
 
The basics of sentences session 10pptx.pptx
The basics of sentences session 10pptx.pptxThe basics of sentences session 10pptx.pptx
The basics of sentences session 10pptx.pptx
 
M-2- General Reactions of amino acids.pptx
M-2- General Reactions of amino acids.pptxM-2- General Reactions of amino acids.pptx
M-2- General Reactions of amino acids.pptx
 
General views of Histopathology and step
General views of Histopathology and stepGeneral views of Histopathology and step
General views of Histopathology and step
 
Finals of Kant get Marx 2.0 : a general politics quiz
Finals of Kant get Marx 2.0 : a general politics quizFinals of Kant get Marx 2.0 : a general politics quiz
Finals of Kant get Marx 2.0 : a general politics quiz
 
What is the Future of QuickBooks DeskTop?
What is the Future of QuickBooks DeskTop?What is the Future of QuickBooks DeskTop?
What is the Future of QuickBooks DeskTop?
 

02 fundamentals

  • 2. Fundamentals Low-level I/O (read/write using system calls)  Opening/Creating files  Reading & Writing files  Moving around in files  file descriptors Program Creation and Execution  exec family of system calls  using fork() to create processes  exiting processes  process termination
  • 3. Low-level I/O Unix System Calls can be used to:  Open/Create Files  Read & Write files  Move around in files System calls work with file descriptors  A file descriptor is an int that represents a file/device  File descriptors are allocated by the system  Limited number of file descriptors available  0 is stdin, 1 is stdout, 2 is stderr; these are automatically allocated and opened when a program begins
  • 4. Opening/Creating Files open(<file/device name>,<how to open>[,<mode>])  <file/device name> is a C-string, exactly as in the C++ fstream member function open()  <how to open> is an int, usually specified with a constant defined in fcntl.h. The values may be combined using a logical OR ( | ), allowing every possible way of opening a file (examples on next slide)  Detail on this appears on the next slide  <mode> is an optional third argument that is specified only if the file is created. It is a three digit octal number representing the permissions to be set on the file.  a file descriptor (of type int) is returned on success; otherwise –1 is returned.
  • 5. Specifying How a File is to be Opened File Access  You must specify how the file is to be accessed. Exactly one of these values must appear in the 2nd argument of open():  O_RDONLY  The file is opened for reading only. If the file doesn’t exist, and the create option (next slide) isn’t specified, open() will fail (note that it is not ordinary to open a file to be read with the create option specified)  O_WRONLY  The file is to be opened for writing only. If the file doesn’t exist, and the create option is not specified, or if the file does exist, and the create option is specified along with the fail if file exists option, open() will fail.  O_RDWR  The file is opened for full access. Errors specified above can occur, however.  If none of these are specified, open() can succeed, but nothing can be done to the file. (See open2.c in the demo directory)
  • 6. Specifying How a File is to be Opened File Opening Options The following are used to further specify how a file is opened. They are combined with the access and possibly each other: O_APPEND  all access is at end of file O_CREAT  create file if it doesn’t exist (does not cause failure if file exists). Use a third argument to specify mode. O_TRUNC  Destroy the existing contents of the file, if it exists. O_EXCL  When combined with O_CREAT, causes open() to fail if the file already exists.
  • 7. Specifying How a File is to be Opened Exercises/Examples  Open a file named abc.txt for writing, only if it exists. If it does, the present contents should be preserved, and writing should occur after the present contents.  Give an open() command equivalent to the C++ command Dest.open(“abc.txt”), where Dest is an ofstream  Give an open command that opens a file abc.txt for writing only if it doesn’t already exist.  Give command(s), to open a file abc.txt for writing. If abc.txt exists, the user should be prompted, and then the file opened for writing only if the user answers affirmatively to a prompt to overwrite the file. Otherwise, the file is created.  Repeat the previous exercise, using C++
  • 8. Low-level Reading and Writing Using low-level (system) calls, I/O can only be accomplished via a buffer, whose size is determined by the user.  small buffer requires more device accesses, slowing program; some systems override with their own buffer Commands:  read(<file descriptor>,<address of buffer>,<# bytes to read>)  write(<file descriptor>,<address of buffer>,<# bytes to read>)  value returned is # bytes read; 0 => eof (read only), -1 => error
  • 9. Moving Around in A File Low-level access via File Descriptor lseek(<file descriptor>,<amount>,<relativity>) where  <file descriptor> is a file descriptor of an open file  <amount> is the number of bytes to move the file descriptor...  <relativity> is the point from which the operation takes place  SEEK_SET (0) is start of file  SEEK_CUR (1) is current position  SEEK_END (2) is end of file  if <amount> is positive with this option, there will be a hole in the file.  the return value is the new offset in the file
  • 10. Exercises  Give an lseek() command to find the present offset in a file  How is the present offset in a file found when the file is accessed via a file pointer?  Give a loop to write the values 1-100 in the same spot of a text file.  Why is the seek command basically worthless in a text file, except to go to the beginning or end of the file?
  • 11. Program Creation and Execution  exec family of system calls  using fork() to create processes  process termination  waiting for processes
  • 12. exec Family of System Calls Execute a program using one of the exec calls  Six exec functions  Can provide a list and have function build argv[] vector or provide the vector itself  Can specify path to program or use path variable to find it  Can use present environment, or specify new environment  environment defined by setenv items. Type set at Unix prompt to see environment  called program occupies environment of caller (takes its pid, as new process isn’t created). Only replaces text, data, heap, and stack segments of caller of exec  execs are the only function calls that don’t return
  • 13. execl & execv execl  give pathname to file (incl. name) as 1st argument  Follow with list of command line arguments; executable 1st  this list is used to build the argv vector passed to the called program  executable name is in argv[0]  last argument must be null char * execv  give pathname to file (incl. name) as 1st argument  Follow with null-terminated argv vector
  • 14. execlp & execvp execlp  give filename as 1st argument; path environment variable is used to find executable  Follow with list of command line arguments; executable 1st  this list is used to build the argv vector passed to the called program  last argument must be null char * execvp  give filename as 1st argument; path used  Follow with null-terminated argv vector
  • 15. Exercise Suppose a program X is executed whose purpose is to call another program Y whose name and command-line arguments are passed in to X as command-line arguments. 1. Write an execlp and an execvp command, as they would appear in X, to execute Y. 2. What problem could arise if we choose to use execl or execv?
  • 16. Process Creation fork & vfork Processes can only be created using a fork command  fork is called once, but returns twice  parent calls fork, value is returned to each of parent and child  created process is called the child  existing process is the parent  Process identifier (pid) is used to distinguish between parent and child  Every process has a unique pid in the system
  • 17. fork  Called once, returns twice; return type is pid_t, unsigned int type for pids  Parent receives child’s pid as return value of fork  child receives 0 as return value from fork  Order of execution depends on scheduling algorithm of system.  Order can be controlled; important if there is dependence between parent and child  Child and parent execute in their own environments  Child gets copy of parent’s environment (including data space) as it is at time of fork  If parent has file open, child gets copy of file pointers or descriptors  If parent’s stdout (cout) is redirected before fork, child output to stdout is also redirected
  • 18. Child Process’ Inheritance  user id, group id  controlling terminal  current working directory  root directory  file mode creation mask  signal mask (later) and dispositions  close-on-exec flag for open file descriptors  environment  attached shared memory segments  resource limits
  • 19. Items That Distinguish Parent From Child  Return value from fork  unique pid  different parent pid (ppid)  child’s ppid is the parent’s pid  parent’s pid stays same  certain time values reset in child  parent’s file locks aren’t inherited  pending alarms are not inherited  pending signals in parent aren’t inherited
  • 20. vfork  Maintained for compatability, vfork is not often used  Some systems implement it as a fork  Child executes first. Parent doesn’t resume until child either exits (via call of exit() or _exit()) or uses exec to start another program.  The child is a separate process, but it shares the parent’s data space. vforkdemo.c shows that this is the case
  • 21. vforkdemo.c #include <stdio.h> #include <sys/types.h> #include <unistd.h> •Parent output is same as child’s int glob ; int •If separate data spaces, parent wouldn’t experience ++ main(void){ operations int var; pid_t pid; glob = 10; var = 20; printf("before vforkn"); if (vfork()== 0 ) { sleep(1); glob++; var++; printf("child glob= %d var= %dn", glob, var); _exit(0); // what if this is just exit()? } else { printf("parent glob= %d var= %dn", glob, var); } }
  • 22. When a process terminates...  Its parent is informed via a SIGCHLD signal  If its parent doesn’t “collect” it, it becomes a zombie process (next slide)  If its parent has already terminated, it is inherited by the init process (pid 1), which “collects” it using a wait operation (2 slides hence).  All processes must have an identifiable (by pid) parent  It is able to provide minimal information to its parent when it comes to “collect” it
  • 23. Zombie Process A zombie is a process that has terminated, but hasn’t been “collected” by its parent  The system frees most of the resources associated with this terminated process, e.g. closing open files and freeing memory,and minimally maintains:  process id  CPU time used  termination status
  • 24. wait operations A terminated process’ information is “collected” via a call of a wait operation by its parent  Operations:  wait  blocks the calling process until a child process terminates, returning the child’s pid.  If caller has no children, wait immediately returns –1 (error)  the termination status (return value) of the child may be obtained via the argument  waitpid  permits a caller to wait for a particular child, identified by its pid  can be configured to not block if the child is active
  • 25. Process Termination Normal: 1. main contains return statement 2. call exit 3. call _exit Abnormal: 1. Process aborts itself 2. Process receives a signal (e.g. division by 0)
  • 26. exit() vs._exit()  exit() causes a process to terminate.  stdio funtion fclose is applied to all open streams  the argument is the exit status  exit status becomes termination status when exit() calls _exit()  _exit is a Unix specific command  the process terminates immediately without any cleanup  see vfork examples  If a process doesn’t explicitly specify exit status via a call to exit() or _exit(), the process’ termination status will be undefined
  • 27. Exercises 1. What can happen if a process calls exit while writing to a buffered output stream? 2. Write code guaranteed to create a zombie process. 3. Write code that will cause a process to be inherited by the init process.

Notas del editor

  1. e.g. cexec