Which command is used to set restrictions on the size of a core file that is created for a user when a program crashes?
Which character, added to the end of a command, runs that command in the background as a child process of the current shell?
The character that, added to the end of a command, runs that command in the background as a child process of the current shell is the ampersand symbol (&). This means that the command will not block the shell and the user can enter other commands while the background command is running. The background command will also not receive any input from the keyboard or the terminal. The shell will print the job number and the process ID of the background command, and the user can use the jobs command to list the status of all background jobs in the current shell session. To bring a background job to the foreground, the user can use the fg command with the job number or the process ID. To terminate a background job, the user can use the kill command with the process ID.
The other characters are not valid or relevant for running a command in the background. The exclamation mark (!) is used to access the command history or to negate a condition. The plus sign (+) is used for arithmetic operations or to append text. The percent sign (%) is used for arithmetic operations or to refer to a job number. The hash sign (#) is used for comments or to specify a hexadecimal number.
[LPI Exam 101 Detailed Objectives], Topic 103: GNU and Unix Commands, Objective 103.5: Create, monitor and kill processes, Weight: 4, Key Knowledge Areas: Run jobs in the foreground and background.
How to Run Linux Commands in Background, Topic: Using Ampersand.
Which SysV init configuration file is commonly used to set the default run level? (Specify the full name of the file, including path.)
F . 4. SysV Init Runlevels - Red Hat Customer Portal
init - How can I see or change default run level? - Ask Ubuntu
The /etc/inittab file is a plain text file that contains information about the initialization process of the system. It defines the default run level, the available run levels, and the actions to be taken when entering or leaving a run level. The default run level is the mode of operation that the system starts up into, and it determines which services and processes are running. The default run level is specified by a line similar to the following in the /etc/inittab file:
id:5:initdefault:
The number after the first colon indicates the default run level, which can range from 0 to 6. The meaning of each run level is:
0 --- Halt
1 --- Single-user text mode
2 --- Not used (user-definable)
3 --- Full multi-user text mode
4 --- Not used (user-definable)
5 --- Full multi-user graphical mode (with an X-based login screen)
6 --- Reboot
To change the default run level, edit the /etc/inittab file as root and change the number to the desired run level. For example, to change the default run level to 3, use the following command:
sudo nano /etc/inittab
And change the line to:
id:3:initdefault:
Then save and exit the file. The changes will take effect on the next reboot.
SysV Init Runlevels - Red Hat Customer Portal
Which of the following commands reboots the system when using SysV init? (Choose TWO correct answers.)
The shutdown command is used to bring the system down in a safe and controlled way. It can take various options and arguments, such as the time of shutdown, the message to broadcast to users, the halt or reboot mode, etc. The option -r instructs the shutdown command to reboot the system after shutting down. The argument now means to shut down immediately. Therefore, shutdown -r now will reboot the system without delay. The telinit command is used to change the run level of the system. It takes a single argument that specifies the new run level. The run level 6 is reserved for rebooting the system. Therefore, telinit 6 will also reboot the system. The other options are either incorrect or irrelevant. shutdown -r ''rebooting'' will also reboot the system, but with a delay of one minute and a message to the users. telinit 0 will halt the system, not reboot it. shutdown -k now ''rebooting'' will only send a warning message to the users, but not actually shut down or reboot the system.Reference:LPI Linux Essentials - 1.101.2, LPI Linux Administrator - 101.3
Justin Bailey
1 month agoBrenda Williams
2 months agoRichard White
2 months agoRebecca Anderson
3 months agoMelissa Lopez
3 months agoMichael Sanchez
4 months agoBrian Howard
4 months agoEmily Collins
5 months agoTiffany Parker
5 months agoJennifer Lee
6 months agoRyan Robinson
6 months agoDorothy Anderson
6 months agoJohn Hall
6 months agoElizabeth Parker
6 months agoLaura Parker
6 months agoMarleen
7 months agoFrancis
7 months agoBea
7 months agoGeoffrey
8 months agoColene
8 months agoJustine
8 months agoAnnelle
8 months agoChana
9 months agoAnnette
9 months agoBlossom
9 months agoRenea
9 months agoCecily
10 months agoCarylon
10 months agoMadalyn
10 months agoMicah
10 months agoMitsue
11 months agoBea
11 months agoLinette
11 months agoDorthy
11 months agoGabriele
12 months agoWhitley
12 months agoLigia
1 year agoFloyd
1 year agoShoshana
1 year agoLouvenia
1 year agoYoko
1 year agoColette
1 year agoKimbery
1 year agoEun
1 year agoLeonida
1 year agoCarole
1 year agoLanie
1 year agoAnnamae
2 years agoAlida
2 years agoMarge
2 years agoOcie
2 years agoArthur
2 years agoDick
2 years agoColene
2 years agoCarolann
2 years agoAndrew
2 years agoYoulanda
2 years agoKyoko
2 years agoErnest
2 years agoTarra
2 years agoKeneth
2 years agoBulah
2 years agoTheron
2 years agoQuiana
2 years agoLorrine
2 years agoBenedict
2 years agoRyan
2 years agoOmega
2 years agoGarry
2 years agoGerman
2 years agoOzell
2 years agoDallas
2 years agoMariko
2 years agoWade
2 years agoTomoko
2 years agoRosamond
2 years agoDonte
2 years agoNichelle
2 years agoGarry
2 years agoArminda
2 years agoLeslie
2 years ago