This is not a question just a short description, I have attached my assignment file with this message. Also i want you to know that the previous assignment that you gave me this one is the continuous...

1 answer below »
This is not a question just a short description, I have attached my assignment file with this message. Also i want you to know that the previous assignment that you gave me this one is the continuous of that so here you have to add two more flags "e" & " E" along with the combination of other flags. All the details are mentioned in the attached file please read it carefully for better understanding , also im a graduate student so in the document there is a phrase "graduate student only" i need to have those instructions to be completed too. can you please help me this task?


Microsoft Word - hw3_CS332.532.docx CS 332/532 – 1G- Systems Programming HW 3 Deadline: 03/03/2023 Objectives To add additional features to the search program implemented in Project #2. Description The goal of this project is to add additional functionality to the search program implemented in Project #2. In addition to the functionality described in Project #2, the program must support the following command-line options: 1. -e "" 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 <= 1024="" bytes="" in="" the="" current="" directory,="" and="" execute="" the="" command="" "ls="" -l"="" on="" each="" file="" (ignore="" directories)="" $./search="" -f="" jpg="" 3="" -e="" "tar="" cvf="" jpg.tar"="" list="" all="" files="" that="" have="" the="" substring="" “jpg”="" in="" their="" filename="" or="" directory="" name="" with="" depth=""><=3 relative="" to="" the="" current="" directory,="" and="" creates="" a="" tar="" file="" named="" jpg.tar="" that="" contains="" these="" files="" $./search="" -s="" 1024="" -f="" jpg="" 3="" -e="" "wc="" -l"="" list="" all="" files="" that="" have="" the="" substring="" “jpg”="" in="" their="" filename="" with="" depth=""><=3 relative="" to="" the="" current="" directory="" and="" size=""><= 1024,="" and="" execute="" the="" command="" "wc="" -l"="" on="" each="" file="" (ignore="" directories)="" sample="" input="" and="" output:="" if="" you="" have="" the="" following="" directory="" structure="" as="" shown="" by="" the="" output="" of="" "ls="" -lr"="" command:="" (="" $="" ls="" -r="" projects="" projects:="" fread.c="" fwrite.c="" project1="" project2="" project3="" project4="" read.c="" write.c="" projects/project1:="" project1.docx="" readme="" projects/project2:="" project2.docx="" readme="" projects/project3:="" project3.docx="" readme="" projects/project4:="" project4.docx="" readme="" )="" then="" the="" output="" of="" find="" without="" any="" argument="" should="" look="" like="" this:="" (="" projects="" fread.c="" fwrite.c="" project1="" readme="" project1.docx="" project2="" project2.docx="" readme="" project3="" project3.docx="" readme="" project4="" project4.docx="" readme="" read.c="" write.c="" )="" it="" is="" not="" necessary="" that="" the="" order="" of="" the="" files="" are="" exactly="" as="" shown="" above,="" but="" the="" overall="" structure="" should="" look="" similar="" to="" the="" output="" shown="" above.="" you="" can="" use="" the="" following="" tar="" file="" to="" create="" the="" directory="" structure:="" projects.tar.="" download="" this="" file="" and="" extract="" the="" file="" using="" the="" command:="" (="" $="" tar="" xvf="" projects.tar="" )="" submission="" guidelines="" upload="" the="" c="" source="" code,="" pdf="" version="" of="" c="" source="" code,="" and="" readme.txt="" file="" to="" canvas.="" do="" not="" include="" any="" executable="" or="" object="" files.="" use="" the="" following="" command="" to="" create="" pdfs="" of="" your="" source="" code.(replace="" the="" and="" with="" your="" c="" source="" code="" file="" name):="" (="" $enscript="" .c="" -o="" -="" |="" ps2pdf="" -="" .pdf="" )="" ·="" use="" best="" software="" engineering="" practices="" to="" design="" and="" implement="" this="" project.="" ·="" use="" functions="" and="" organize="" these="" functions="" in="" multiple="" files="" if="" necessary.="" ·="" use="" a="" makefile="" to="" compile="" and="" build="" the="" multiple="" files.="" ·="" document="" you="" code="" and="" include="" instructions="" for="" compiling="" and="" executing="" the="" program="" in="" the="" readme.txt="" file.="" grading="" rubrics="" description="" points="" implementation="" of="" parsing="" the="" arguments="" to="" the="" search="" program="" correctly="" and="" invoking="" the="" appropriate="" function="" 20="" points="" implementation="" of="" search="" that="" executes="" the="" unix="" command="" with="" optional="" arguments="" for="" each="" matching="" file="" using="" fork/exec/wait="" 50="" points="" implementation="" of="" search="" that="" lists="" the="" files="" and="" directories="" in="" the="" specified="" format="" when="" executed="" with="" multiple="" options="" (combination="" of="" -s,="" -f="" and="" -e)="" 20="" points="" use="" of="" makefile,="" source="" code="" documentation="" (including="" readme.txt="" file)="" 10="" points="" microsoft="" word="" -="" hw2_cs332.532.docx="" cs="" 332/532="" –="" 1g-="" systems="" programming="" hw="" 2="" 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 <= 1024="" bytes="" in="" the="" current="" directory="" ./search="" -s="" 1024="" ../programs="" list="" all="" files="" with="" size=""><= 1024="" bytes="" in="" the="" ../programs="" (relative="" to="" the="" current="" directory)="" ./search="" -f="" jpg="" 1="" list="" all="" files="" in="" the="" current="" directory="" that="" have="" the="" substring="" “jpg”="" in="" their="" name="" with="" depth=""><=1 relative="" to="" current="" directory="" ./search="" -f="" jpg="" 1="" -s="" 1024="" list="" all="" files="" in="" the="" current="" directory="" that="" have="" the="" substring="" “jpg”="" in="" their="" name="" with="" depth=""><=1 relative="" to="" the="" current="" directory="" and="" size=""><= 1024 ./search -s 1024 -f jpg 1 the same as “./search -f jpg 1 -s 1024” ./search -s -f jpg 1 -s 1024 similar with “./search -f jpg 1 -s 1024”. print the required attributes, not only the filenames. sample input and output: if you have the following directory structure as shown by the output of "ls -lr" command: ( $ ls -r projects projects : fread.c fwrite.c project1 project2 project3 project4 read.c write.c projects/project1: project1.docx readme projects/project2: project2.docx readme projects/project3: project3.docx readme projects/project4: project4.docx readme ) then the output of find without any argument should look like this: ( projects fread.c fwrite.c project1 readme project1.docx project2 project2.docx readme project3 project3.docx readme project4 project4.docx readme read.c write.c ) it is not necessary that the order of the files are exactly as shown above, but the overall structure should look similar to the output shown above. you can use the following tar file to create the directory structure: projects.tar. download this file and extract the file using the command: ( $ tar xvf projects.tar ) submission guidelines · use best software engineering practices to design and implement this homework. the next homework will extend the functionality provided by this program. · use functions and organize these functions in multiple files if necessary. · use a makefile to compile and build the multiple files. · document you code and include instructions for compiling and executing the program in the readme.txt file. · test your program and describe how you tested this program in the readme.txt file. · to submit this homework : oupload all the source files and documentation to canvas. grading rubrics description points implementation of search that lists the files and directories in the specified format when executed with no arguments or when the directory name is specified as an argument 30 points correct use of function pointers to implement the required functionality 20 points implementation of search that lists the files and directories in the specified format when executed with -s option 10 points implementation of search that lists the files and directories in the specified format when executed with -s option 10 points implementation of search that lists the files and directories in the specified format when executed with -f option 10 points implementation of search that lists the files and directories in the specified format when executed with multiple options (combination of -s, -s, and -f) 10 points use of makefile, source code documentation (including readme..txt) 10 points 1024="" ./search="" -s="" 1024="" -f="" jpg="" 1="" the="" same="" as="" “./search="" -f="" jpg="" 1="" -s="" 1024”="" ./search="" -s="" -f="" jpg="" 1="" -s="" 1024="" similar="" with="" “./search="" -f="" jpg="" 1="" -s="" 1024”.="" print="" the="" required="" attributes,="" not="" only="" the="" filenames.="" sample="" input="" and="" output:="" if="" you="" have="" the="" following="" directory="" structure="" as="" shown="" by="" the="" output="" of="" "ls="" -lr"="" command:="" (="" $="" ls="" -r="" projects="" projects="" :="" fread.c="" fwrite.c="" project1="" project2="" project3="" project4="" read.c="" write.c="" projects/project1:="" project1.docx="" readme="" projects/project2:="" project2.docx="" readme="" projects/project3:="" project3.docx="" readme="" projects/project4:="" project4.docx="" readme="" )="" then="" the="" output="" of="" find="" without="" any="" argument="" should="" look="" like="" this:="" (="" projects="" fread.c="" fwrite.c="" project1="" readme="" project1.docx="" project2="" project2.docx="" readme="" project3="" project3.docx="" readme="" project4="" project4.docx="" readme="" read.c="" write.c="" )="" it="" is="" not="" necessary="" that="" the="" order="" of="" the="" files="" are="" exactly="" as="" shown="" above,="" but="" the="" overall="" structure="" should="" look="" similar="" to="" the="" output="" shown="" above.="" you="" can="" use="" the="" following="" tar="" file="" to="" create="" the="" directory="" structure:="" projects.tar.="" download="" this="" file="" and="" extract="" the="" file="" using="" the="" command:="" (="" $="" tar="" xvf="" projects.tar="" )="" submission="" guidelines="" ·="" use="" best="" software="" engineering="" practices="" to="" design="" and="" implement="" this="" homework.="" the="" next="" homework="" will="" extend="" the="" functionality="" provided="" by="" this="" program.="" ·="" use="" functions="" and="" organize="" these="" functions="" in="" multiple="" files="" if="" necessary.="" ·="" use="" a="" makefile="" to="" compile="" and="" build="" the="" multiple="" files.="" ·="" document="" you="" code="" and="" include="" instructions="" for="" compiling="" and="" executing="" the="" program="" in="" the="" readme.txt="" file.="" ·="" test="" your="" program="" and="" describe="" how="" you="" tested="" this="" program="" in="" the="" readme.txt="" file.="" ·="" to="" submit="" this="" homework="" :="" o="" upload="" all="" the="" source="" files="" and="" documentation="" to="" canvas.="" grading="" rubrics="" description="" points="" implementation="" of="" search="" that="" lists="" the="" files="" and="" directories="" in="" the="" specified="" format="" when="" executed="" with="" no="" arguments="" or="" when="" the="" directory="" name="" is="" specified="" as="" an="" argument="" 30="" points="" correct="" use="" of="" function="" pointers="" to="" implement="" the="" required="" functionality="" 20="" points="" implementation="" of="" search="" that="" lists="" the="" files="" and="" directories="" in="" the="" specified="" format="" when="" executed="" with="" -s="" option="" 10="" points="" implementation="" of="" search="" that="" lists="" the="" files="" and="" directories="" in="" the="" specified="" format="" when="" executed="" with="" -s="" option="" 10="" points="" implementation="" of="" search="" that="" lists="" the="" files="" and="" directories="" in="" the="" specified="" format="" when="" executed="" with="" -f="" option="" 10="" points="" implementation="" of="" search="" that="" lists="" the="" files="" and="" directories="" in="" the="" specified="" format="" when="" executed="" with="" multiple="" options="" (combination="" of="" -s,="" -s,="" and="" -f)="" 10="" points="" use="" of="" makefile,="" source="" code="" documentation="" (including="" readme..txt)="" 10="">
Answered 16 days AfterFeb 23, 2023

Answer To: This is not a question just a short description, I have attached my assignment file with this...

Sairama answered on Mar 03 2023
35 Votes
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here