
\chapter{Administration}
\label{chap-adm}

\section{The \texttt{ippdor} user}
\label{sec-adm-ippdor}

\texttt{ippdor} is the dedicated user for any processing happening in
Condor. This user uses the \texttt{bash} shell. The ippdor has no
particular privilege on the system.

The \texttt{bashrc} file contains some definitions and expansions:
\begin{itemize}
\item \texttt{PATH} adds \texttt{\$HOME/local/bin};
\item \texttt{LD\_LIBRARY\_PATH} adds \texttt{\$HOME/local/lib};
\item \texttt{PYTHONPATH} adds \texttt{\$HOME/local/share/python} and
  \texttt{\$HOME/local/lib/python2.6/site-packages};
\item The \texttt{PSCONFIG} value is fixed to \texttt{current}. See
  section~\ref{sec-link-ippTODO} for details. The
  \texttt{psconfig.bash} utility is called using that value.
\end{itemize}

\texttt{cmake} was locally installed to allow Condor build and
install. It is now the only external software. It was built using the
\texttt{--prefix=\$HOME/local} option and can be found in the
\texttt{\$HOME/softwares} directory.

\section{Deploying Condor on a new host}
\label{sec-adm-newnode}

Log in as the \texttt{ippdor} user on any host of the cluster.

To install the condor on any \texttt{host}, run:
\begin{verbatim}
ippdor@ippc18 ~ $ ssh <host> ./deploy_condor.sh
\end{verbatim}

\section{Starting Condor where it does not run}
\label{sec-adm-start_condor}

It's been a long time that Condor has not been used. We don't know
where it runs and don't want to try to restart it where it does not
run...

Simply run (use auto-completion):
\begin{verbatim}
ippdor@ippc30 ~ $ start_condor_where_it_does_not_run.sh 
\end{verbatim}

\section{Updating Condor}
\label{sec-adm-update}

To be written when it's happening...
