Please Include these points as well. Microsoft Word - hw2_CS332.532.docx CS 332/532 – 1G-...

Question

Please Include these points as well.					Microsoft Word - hw2_CS332.532.docx CS 332/532 – 1G- Systems Programming  HW 2  Deadline: 02/19/2023 11:59pm  Objectives  To implement a search program in C program using system calls for files and  directories. Description  Find is a popular UNIX command that traverses a file hierarchy and performs various  functions on each file in the hierarchy. The goal of this project is to implement a  program similar called search that supports the following functionality:  1. The program should take the directory name from where to start the file traversal as a  command-line argument and print the file hierarchy starting with the directory that is  provided by the command-line argument.  2. If the program is executed without any arguments, the program should print the file  hierarchy starting with the current directory where the program is executed. If there are no  directories in the current directory only files are listed one per line.  3. If there are other directories in the current directory then the directory name is first  displayed on a separate line and then the files in that directory are listed one-per-line with  one-tab indentation.  4. If a file is a symbolic link then the program should display the symbolic link name and in  parentheses the file name the link points to.  5. The program should also support three command-line options:  1. -S  This should list all files in the hierarchy and print the size, permissions, and last access  time next to the filename in parenthesis. Print 0 for the size of a directory.  2. -s   This should list all files in the hierarchy with file size less than or equal to the value  specified.  3. -f    This should list all files in the hierarchy that satisfy the following conditions: 1) the file  name contains the substring in the string pattern option, AND 2) the depth of the file  relative to the starting directory of the traversal is less than or equal to the depth option.  The starting directory itself has a depth of 0.  6. The program should support not only each of these options separately but also any  combination of these options. For example: -S, -s 1024, -f jpg 1, -S -s 1024, -S -f jpg 2, -s  1024 -f jpg 2, -S -s 1024 -f jpg 1, -S -f jpg 2 -s 1024.  7. If both -s and -f options are specified then the program should list only those files that  match both criteria. The order of the options should not matter.  8. [Graduate Students Only] The program should support a fourth command-line option:  1. -t f - list regular files only  2. -t d - list directories only   Guidelines and Hints  1. The program must use function pointers similar to Figure 4.22 in the text book to  implement the functionality described above. You can use the logic and structure from  Figure 4.22 as the starting point to implement this program (make sure to go over the  program in Figure 4.22 and understand all the steps performed). However, please note that  your final program must compile and execute without any dependencies on the source  code provided by the text book. You can find a simple example on how to use function  pointers in the funcptr.c file  2. You can use the getopt function to process the command-line options. See man 3  getopt for more details and an example on how to use getopt function.   3. You should use a Makefile to compile and build this project and make sure to submit the  Makefile along with the rest of the source code.  4. You should upload all the source code, Makefile, and a README.txt file to Canvas. Please  do not upload any object files or executable files.  Program Documentation and Testing  1. Use appropriate names for variables and functions.  2. Use a Makefile to compile your program.  3. Include meaningful comments to indicate various operations performed by the program.  4. Programs must include the following header information within comments:  /*  Name:  BlazerId:  Project #:  To compile:   To run:   */  5. Test your program with the sample test cases provided as well as your own test cases.  6. You can include any comments you may have about testing in the README.txt file. Examples               Command Description  ./search List all files in the current directory where the program is executed.  ./search ../programs List all files in the directory ../programs (relative to the current directory)  ./search  /home/UAB/puri/CS332/programs  List all files in the directory /home/UAB/puri/CS332/programs (absolute  path)  ./search -S ../programs List all files in the directory ../programs along with the required attributes  ./search -s 1024 List all files with size "  For each file that matches the search criteria the UNIX command specified with  arguments must be executed.   2. -E "" [Graduate Students Only]  The list of files that matches the search criteria must be provided as an argument to  the UNIX command specified.  Note that with the -e option the UNIX command is executed for each file whereas with  the -E option the UNIX command is executed only once but uses all the file names as  the argument. You must use fork/exec/wait to create a new process to execute the  UNIX command.  The UNIX command and any optional arguments are enclosed within double quotes.  The program should support -e or -E options in combination with -s and -f options. You  can assume that the -e or -E options appear after the -s and -f options.   Guidelines and Hints  1. You should use a Makefile to compile and build this project and make sure to  submit the Makefile along with the rest of the source code.  2. You should upload all the source code, Makefile, and a README.txt file to Canvas.  Please do not upload any object files or executable files.  Program Documentation and Testing  1. Use appropriate names for variables and functions.  2. Use a Makefile to compile your program.  3. Include meaningful comments to indicate various operations performed by the  program.  4. Programs must include the following header information within comments:  /*  Name:  BlazerId:  Project #:  To compile:   To run:   */  4. Test your program with the sample test cases provided as well as your own test  cases.  5. You can include any comments you may have about testing in the README.txt  file.    Examples  Command Description  $./search -s 1024 -e "ls -l"  List all files with size

Aditi · Accepted Answer

SOL
Approach 1:
switch (dir->d_type) {
    // is a Regular File.
    case DT_REG:
        if (tFflag) {
            if (showFile) {
                if (Eflag) {
                    if (eval != NULL && strstr(dir->d_name, eval) != NULL) {
                        break;
                    }
                    else {
                        launch(set_pathFileName(working_directory, dir->d_name, path_and_filename));
                        break;
                    }
                }
                printf("%s%s
", tabs, dir->d_name);
            }
            break;
        }
        break;
    // is a Directory.
    case DT_DIR:
        if (tDflag) {
            printf("%s%s/
", tabs, dir->d_name);
            char path[FILENAME_MAX];
            sprintf(path,

Microsoft Word - hw2_CS XXXXXXXXXXdocxCS 332/532 – 1G- Systems Programming HW 2 Deadline: 02/19/2023 11:59pm Objectives To implement a search program in C program using system calls for...

Answer To: Microsoft Word - hw2_CS XXXXXXXXXXdocxCS 332/532 – 1G- Systems Programming HW 2 Deadline:...

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment