0
If you are the super-user you could kill the init process, however, it isn't recommended since no new tasks would be spawned and the system is likely to crash shortly thereafter.
Wiki User
∙ 11y ago
Add your answer:
Earn +20 pts
How can you kill a orphaned process with ppid 1 I am not able to kill that with Kill -9 pid options.?
PID 1 on a Unix or Unix-like system is init. You cannot kill init.
How do you terminate a process in unix?
Generally any process may be terminated by sending the appropriate signal to it. The command to send signals to a process is called 'kill', and the various signals you can use are identified by 'kill -l' or by 'man kill'
What would you name the link to an init script that would start the fictitious bigd demon early in the boot process?
Kill -9
What would you name the link to an init script that would kill the fictitious bigd daemon early in the boot process?
/etc/rc5.bigd.d
What command can be used to stop a proccess that is more powerful than Task manager?
kill kill-all Wait that might be in Unix... Windows has "k" and then the "Process ID" or "Process Name" taskkill is another command you could try.
How do you kill pest in crop fields?
ya burn tha field down init blap blap.
My computer used to freeze all the time and to solve the issue i had to reset the computer because i use ubuntu which doesnt have a task manager and now it wont even start up what is wrong with it?
Ubuntu is very stable.If one piece of software was freezing its clearly software problems. The rest of the screen outside that app's window would still work.If everything was locking up I'd suspect a hardware error.If you are hardware skilled try removing and re-inserting the memory cards.There is also excellent task management in Ubuntu. Bring up a terminal window and shell, then$ ps -afe | lessFind the process id of your mis-behaving program under the column labelled PID.Then simply type$ kill "insert process id number here"or alternatively you can$ pkill -9 "insert process name here"$ exitand your mis-behaving process will be dead, dead, dead...Hmm. I should perhaps caution you here not to try to kill process '1', also called 'init'. If you wish 'init' to change it's runlevel, simply consult the 'init' man page and issue the appropriate argument to 'init'. Well, just be sure you kill the correct process or your mileage may vary (GREATLY!).
How can you stop computer programmes running in the background?
In UNIX: with command kill, in Windows: from Task Manager.
What does the command kill -9 do in Unix?
Kill is a program that can terminate or send a signal to process.kill -9 pidWould send signal 9 to process having specific pid. 9 Means KILL signal that is not catchable or ignorable. In other words it would signal process (some running application) to quit immediately.pid - process identifier.
What are the different types of systems?
In computing, the process identifier (normally referred to as the process ID or just PID) is a number used by some operating system kernels (such as that of UNIX, Mac OS X or Microsoft Windows) to uniquely identify a process. This number may be used as a parameter in various function calls allowing processes to be manipulated, such as adjusting the process's priority or killing it altogether.A parent process is a computer process that has created one or more child processes.In UNIX, every process except process 0 (the swapper) is created when another process executes the fork system call. The process that invoked fork is the parent process and the newly-created process is the child process. Every process (except process 0) has one parent process, but can have many child processes.The kernel identifies each process by its process identifier (PID). Process 0 is a special process that is created when the system boots; after forking a child process (process 1), process 0 becomes the swapper process. Process 1, known as init, is the ancestor of every other process in the system.When a child process terminates execution, either by calling the exit system call, causing a fatal execution error, or receiving a terminating signal, an exit status is returned to the operating system. The parent process is informed of its child's termination through a SIGCHLD signal. A parent will typically retrieve its child's exit status by calling the wait system call. However, if a parent does not do so, the child process becomes a zombie process.A child process is a computer process created by another process (the parent process).A child process inherits most of its attributes, such as open files, from its parent. In UNIX, a child process is in fact created (using fork) as a copy of the parent. The child process can then overlay itself with a different program (using exec) as required.Each process may create many child processes but will have at most one parent process; if a process does not have a parent this usually indicates that it was created directly by the kernel. In some systems, including UNIX based systems such as Linux, the very first process (called init) is started by the kernel at booting time and never terminates (see Linux startup process); other parentless processes may be launched to carry out various daemon tasks in userspace. Another way for a process to end up without a parent is if its parent dies, leaving an orphan process; but in this case it will shortly be adopted by init.The exec functions of Unix-like operating systems are a collection of functions that causes the running process to be completely replaced by the program passed as argument to the function. As a new process is not created, the process ID (PID) does not change across an execute, but the data, heap and stack of the calling process are replaced by those of the new process.In the execl, execlp, execv, and execvp calls, the child process inherits the parent's environment.Files open when an exec call is made remain open in the new process. All open files must be flushed before an exec call. The exec calls do not preserve the translation modes of open files. If the child process uses files inherited from the parent, setmode function can be called to set the translation mode to the desired mode.In MS-DOS environments, a program executed with one of the exec functions is always loaded into memory as if the "maximum allocation" in the program's executable file header is set to default value 0xFFFF. The EXEHDR utility can be used to change the maximum allocation field of a program. However, if this is done and the program is invoked with one of the exec functions, the program might behave differently from a program invoked directly from the operating-system command line or with one of the spawn functions.Many Unix shells also offer an "exec" built-in command that replaces the shell process with the specified program.[1] "Wrapper" scripts often use this command to run a program (either directly or through an interpreter or virtual machine) after setting environment variables or other configuration. By using exec, the resources used by the shell program do not need to stay in use after the program is started. [2]A computer process terminates its execution by making an exit system call. More generally, an exit in a multithreading environment means that a thread of execution has stopped running. The operating system reclaims resources (memory, files, etc.) that were used by the process. The process is said to be a dead process after it terminates.In modern computer operating systems, a process (or task) may wait on another process to complete its execution. In most systems, a parent process can create an independently executing child process. The parent process may then issue a wait system call, which suspends the execution of the parent process while the child executes. When the child process terminates, it returns an exit status to the operating system, which is then returned to the waiting parent process. The parent process then resumes execution.Fork is the name of the system call that the parent process uses to "divide" itself ("fork") into two identical processes. After calling fork(), the created child process is actually an exact copy of the parent - which would probably be of limited use - so it replaces itself with another process using the system call exec().In computing, kill is a command that is used in several popular operating systems to request the termination of a process that is currently running on the system.
What are the different types of system call?
In computing, the process identifier (normally referred to as the process ID or just PID) is a number used by some operating system kernels (such as that of UNIX, Mac OS X or Microsoft Windows) to uniquely identify a process. This number may be used as a parameter in various function calls allowing processes to be manipulated, such as adjusting the process's priority or killing it altogether.A parent process is a computer process that has created one or more child processes.In UNIX, every process except process 0 (the swapper) is created when another process executes the fork system call. The process that invoked fork is the parent process and the newly-created process is the child process. Every process (except process 0) has one parent process, but can have many child processes.The kernel identifies each process by its process identifier (PID). Process 0 is a special process that is created when the system boots; after forking a child process (process 1), process 0 becomes the swapper process. Process 1, known as init, is the ancestor of every other process in the system.When a child process terminates execution, either by calling the exit system call, causing a fatal execution error, or receiving a terminating signal, an exit status is returned to the operating system. The parent process is informed of its child's termination through a SIGCHLD signal. A parent will typically retrieve its child's exit status by calling the wait system call. However, if a parent does not do so, the child process becomes a zombie process.A child process is a computer process created by another process (the parent process).A child process inherits most of its attributes, such as open files, from its parent. In UNIX, a child process is in fact created (using fork) as a copy of the parent. The child process can then overlay itself with a different program (using exec) as required.Each process may create many child processes but will have at most one parent process; if a process does not have a parent this usually indicates that it was created directly by the kernel. In some systems, including UNIX based systems such as Linux, the very first process (called init) is started by the kernel at booting time and never terminates (see Linux startup process); other parentless processes may be launched to carry out various daemon tasks in userspace. Another way for a process to end up without a parent is if its parent dies, leaving an orphan process; but in this case it will shortly be adopted by init.The exec functions of Unix-like operating systems are a collection of functions that causes the running process to be completely replaced by the program passed as argument to the function. As a new process is not created, the process ID (PID) does not change across an execute, but the data, heap and stack of the calling process are replaced by those of the new process.In the execl, execlp, execv, and execvp calls, the child process inherits the parent's environment.Files open when an exec call is made remain open in the new process. All open files must be flushed before an exec call. The exec calls do not preserve the translation modes of open files. If the child process uses files inherited from the parent, setmode function can be called to set the translation mode to the desired mode.In MS-DOS environments, a program executed with one of the exec functions is always loaded into memory as if the "maximum allocation" in the program's executable file header is set to default value 0xFFFF. The EXEHDR utility can be used to change the maximum allocation field of a program. However, if this is done and the program is invoked with one of the exec functions, the program might behave differently from a program invoked directly from the operating-system command line or with one of the spawn functions.Many Unix shells also offer an "exec" built-in command that replaces the shell process with the specified program.[1] "Wrapper" scripts often use this command to run a program (either directly or through an interpreter or virtual machine) after setting environment variables or other configuration. By using exec, the resources used by the shell program do not need to stay in use after the program is started. [2]A computer process terminates its execution by making an exit system call. More generally, an exit in a multithreading environment means that a thread of execution has stopped running. The operating system reclaims resources (memory, files, etc.) that were used by the process. The process is said to be a dead process after it terminates.In modern computer operating systems, a process (or task) may wait on another process to complete its execution. In most systems, a parent process can create an independently executing child process. The parent process may then issue a wait system call, which suspends the execution of the parent process while the child executes. When the child process terminates, it returns an exit status to the operating system, which is then returned to the waiting parent process. The parent process then resumes execution.Fork is the name of the system call that the parent process uses to "divide" itself ("fork") into two identical processes. After calling fork(), the created child process is actually an exact copy of the parent - which would probably be of limited use - so it replaces itself with another process using the system call exec().In computing, kill is a command that is used in several popular operating systems to request the termination of a process that is currently running on the system.
Why are PID numbers useful when you run processes in the background?
Process IDs are useful for backgrounded processes in cases where you need to either bring it into the foreground, send it a signal, or terminate/kill it. The reason for this is it's often not a good idea to identify a process by its program name lest there be multiple instances and you wish to address one of them. Process names are hardly unique, but running process IDs are. Thus when trying to background a process it's a good idea to make note of its PID. Daemons, on the other hand, don't necessarily require you to track its PID, as they are managed by the system's init system. If a daemon is misbehaving or needs management intervention by you, you can, as root, simply ask init, systemd, or whatever your distribution uses to pause or stop the daemon for a moment. Often when changing a daemon's configuration you use your init system to restart the daemon so it runs on the new config. Do not that daemons and even some other background processes are only under the control of root, or even more extremely, the kernel in kernel space, and you might not be able to do anything with them.
