1733 |
\label{proc} |
\label{proc} |
1734 |
|
|
1735 |
The \texttt{proc} server implements Unix process semantics in the Hurd |
The \texttt{proc} server implements Unix process semantics in the Hurd |
1736 |
system. |
system. It will also assign a PID to each task that was created with |
1737 |
|
the \texttt{task} server, so that the owner of these tasks, and the |
1738 |
|
system administrator, can at least send the \verb/SIGKILL/ signal to |
1739 |
|
them. |
1740 |
|
|
1741 |
|
The \texttt{proc} server uses the task manager capability from the |
1742 |
|
\texttt{task} server to get hold of the information about all tasks |
1743 |
|
and the task control caps. |
1744 |
|
|
1745 |
|
\begin{comment} |
1746 |
|
The \texttt{proc} server might also be the natural place to |
1747 |
|
implement a first policy server for the \texttt{task} server. |
1748 |
|
\end{comment} |
1749 |
|
|
1750 |
|
|
1751 |
\subsection{Signals} |
\subsection{Signals} |
1799 |
reusing task IDs as long as possible. |
reusing task IDs as long as possible. |
1800 |
\end{comment} |
\end{comment} |
1801 |
|
|
1802 |
|
Some signals are not implemented by sending a message to the task. |
1803 |
|
\verb/SIGKILL/ for example destroys the tasks without contacting it at |
1804 |
|
all. This feature is implemented in the \texttt{proc} server. |
1805 |
|
|
1806 |
|
The signal capability is also used for other things, like the message |
1807 |
|
interface (which allows you to manipulate the environment variables |
1808 |
|
and \texttt{auth} capability of a running task, etc). |
1809 |
|
|
1810 |
|
|
1811 |
\section{Exec} |
\section{Exec} |
1812 |
|
|