The  file  command determines the type of a file by using a definition database file which contains information about all common file types. The database file is usually located at  /usr/share/misc/magic  or  /usr/share/file/magic  and can be customized by the user. The  file  command analyzes the content and structure of the file and compares it with the patterns in the database file to identify the file type. The  file  command can also check the file name extension, but it does not rely on it. The other options are either invalid or do not perform the desired task. The  magic ,  pmagic  and  hash  commands are not valid Linux commands. The  type  command is used to display information about command type, not file type.  References:

LPIC-1 Exam 101 Objectives , Topic 103: GNU and Unix Commands, 103.3 Perform basic file management

LPIC-1 Linux Administrator 101-500 Exam FAQ , LPIC-1 Exam 101 Objectives, GNU and Unix Commands (Total Weight: 25)

The bg command is used to resume a suspended command in the background, allowing it to run without user interaction. The command takes a job ID as an argument, which can be obtained by using the jobs command. Alternatively, if no job ID is specified, bg will resume the most recently suspended job. The bg command is part of the job control features of the Linux shell, which allow users to manage multiple processes running in the same terminal.  References :

LPI Linux Essentials: 1.3.2 Job Control

LPI Linux Administrator: 103.1 Work on the command line

 The  find  command is used to search for files and directories that match certain criteria. The  -uid  option specifies the numeric user ID of the owner of the file or directory, while the  -user  option specifies the name of the owner. The  -print  option prints the full file name of the matching file or directory to the standard output. Therefore, both  find /tmp -uid root -print  and  find /tmp -user root -print  will print all files and directories within the /tmp directory or its subdirectories which are also owned by the user root. The other options are either invalid or do not perform the desired task. The  -path  option matches the whole path name, not just the starting directory. The  -print  option is implied if no other action is specified, but it is good practice to include it for clarity.  References:

LPIC-1 Exam 101 Objectives , Topic 103: GNU and Unix Commands, 103.4 Use streams, pipes and redirects

LPIC-1 Linux Administrator 101-500 Exam FAQ , LPIC-1 Exam 101 Objectives, GNU and Unix Commands (Total Weight: 25)

 Running a command in the background of your shell means that the command will execute asynchronously, without blocking the shell prompt or waiting for user input. This can be useful for commands that take a long time to complete, or that do not require user interaction. One of the valid reasons to run a command in the background is when the command has to run immediately but the user needs to log out. For example, if the user wants to start a backup process that will take several hours, but also wants to close the terminal session and log out from the system, they can run the backup command in the background by appending an ampersand ( & ) to the command line. This way, the backup command will continue to run even after the user logs out, and the user can check the status or output of the command later. The other options are either incorrect or not applicable. Running a command in the background does not affect the execution priority of the command, which is determined by the nice value and the scheduler. Running a command in the background does not delay the execution of the command, which will start as soon as possible. Running a command in the background does not guarantee that the command will survive a system shutdown or reboot, unless the command is configured to do so with a service manager or a startup script.  References:

LPIC-1 Exam 101 Objectives , Topic 103: GNU and Unix Commands, 103.1 Work on the command line

LPIC-1 Linux Administrator 101-500 Exam FAQ , LPIC-1 Exam 101 Objectives, GNU and Unix Commands (Total Weight: 25)

 The command that displays the contents of a gzip compressed tar archive is tar ztf archive.tgz. This command uses the following options:

-z: Tells tar to read or write archives through gzip, allowing it to work on compressed files directly. -t: Lists the contents of an archive without extracting it. -f archive.tgz: Specifies the name of the archive file.

The output of this command will show the names of the files and directories stored in the archive, one per line. For example, if the archive contains three files named file1, file2, and file3, the output will be:

file1 file2 file3

The other commands are incorrect for the following reasons:

gzip archive.tgz | tar xvf -: This command will decompress the archive using gzip and pipe it to tar, which will extract the files to the current directory. The - option tells tar to read the archive from the standard input. This command does not display the contents of the archive, but rather extracts them.

gzip -d archive.tgz | tar tvf -: This command is similar to the previous one, except that it uses the -d option for gzip to decompress the archive instead of compressing it, and the -t option for tar to list the contents instead of extracting them. However, this command is redundant and inefficient, as tar can handle compressed archives directly with the -z option. Also, the -d option for gzip will delete the original archive file after decompression, which may not be desirable.

tar cf archive.tgz: This command will create a new archive named archive.tgz from the files and directories given as arguments. However, this command does not use the -z option, so the archive will not be compressed with gzip. Also, this command does not display the contents of the archive, but rather creates it.

The command that is used to change options and positional parameters for a running Bash is set. The set command allows the user to modify the behavior of the shell by enabling or disabling various options, such as -x (trace mode), -e (exit on error), -u (treat unset variables as errors), and others. The set command can also be used to assign values to the positional parameters, which are the arguments passed to the shell or a shell script. The positional parameters are denoted by $1, $2, $3, and so on, up to $9. The special parameter 0referstothenameoftheshellortheshellscript.Thespecialparameter# refers to the number of positional parameters. The special parameter $@ refers to all the positional parameters as a list.

To change the positional parameters, the set command can be used with the – option, followed by the new arguments. For example, the following command will set the positional parameters to “a”, “b”, and “c”:

set – a b c

After this command, $1 will be “a”, $2 will be “b”, 3willbe " c " ,# will be 3, and $@ will be “a b c”. The – option signals the end of options and prevents any argument that starts with a - from being interpreted as an option. Alternatively, the set command can be used with the - option, followed by the new arguments. However, this will also disable the -x and -v options, if they were previously enabled. For example, the following command will set the positional parameters to “-a”, “-b”, and “-c”, and turn off the trace and verbose modes:

set - -a -b -c

The set command can also be used without any option or argument, in which case it will display the names and values of all shell variables and functions.

The other commands are not valid or relevant for changing options and positional parameters for a running Bash. The history command displays the history list of commands entered by the user. The bashconf command does not exist. The setsh command does not exist. The envsetup command does not exist.

The default nice level when a process is started using the nice command is 10. This means that the process will have a lower priority than the normal processes, which have a nice level of 0. The nice command allows the user to adjust the priority of a process at the time of its execution. The syntax of the nice command is:

nice [-n {nice value increment}] [command]

The -n option specifies the nice value increment, which can be a positive or negative integer in the range of -20 to 19. The command is the name of the program or script to be executed. If the -n option is omitted, the default nice value increment is 10. For example, the following command will run the program ackermann with a nice value of 10:

nice ./ackermann

To verify the nice value of a running process, we can use the ps or top commands and look at the NI column. For example, the following command will show the nice value of the ackermann process:

ps -el | grep ackermann