Commit efad9306 authored by Michael Krause's avatar Michael Krause 🎉
Browse files

Fix minor warnings/issue/typos

parent 7a56f049
......@@ -51,7 +51,7 @@ might want to use your machine as well. But most importantly it is **slow**.
With the Tardis you can login from your laptop or workstation with SSH (see:
:doc:`login`) to a single head node called ``tardis``. On that node users can
prepare and test their code and analysis and then submit it to a queue (see:
:doc:`../pbs/torque`). Jobs will then **eventually** be submitted to one of the
:ref:`torque`). Jobs will then **eventually** be submitted to one of the
computing nodes to get a guaranteed set of processing resources. Afterwards
users can collect the results and copy them back to the file servers.
......
......@@ -94,7 +94,7 @@ Macfusion Configuration
Using sshfs directly
Alternatively, you can simply run sshfs in the command line to mount the remote side:
.. code-block:: bash
.. code-block::
lip-osx-001106:~ krause$ mkdir -p /Users/krause/Volumes/tardis # run this only once
lip-osx-001106:~ krause$ sshfs krause@tardis.mpib-berlin.mpg.de: /Users/krause/Volumes/tardis/
......
......@@ -25,7 +25,7 @@ Queues/Partitions
The RM usually manages a number of queues (they are called partitions for
Slurm) and they can hold thousands of jobs that are subject to execution. Once
you prepared a Job (:ref:`torque_jobs`, :ref:`slurm/slurm_jobs`) you can place them
you prepared a Job (:ref:`torque_jobs`, :ref:`slurm_jobs`) you can place them
inside a queue. All jobs of all users are going to the same central
queue(s):
......
.. _torque:
Torque **(End-Of-Life)**
========================
......@@ -12,4 +14,4 @@ became incompatible to some of the more recent feature of Torque.
.. include:: torque/commands.rst
.. include:: torque/resources.rst
.. _Torque: http://www.adaptivecomputing.com/products/open-source/torque
.. _torque: http://www.adaptivecomputing.com/products/open-source/torque
......@@ -162,7 +162,7 @@ Examples:
krause@master:~> $ qdel all
qdel: cannot find any jobs to delete
``qdel`` cannot handle wildcards to remove jobs matching the name 'project-*',
``qdel`` cannot handle wildcards to remove jobs matching the name 'project-\*',
but you can use grep and xargs:
.. code-block:: bash
......
.. _jobs:
.. _torque_jobs:
Example Jobs
------------
......
......@@ -63,7 +63,7 @@ pbs_resources``.
+ **b** defines the beginning of a job run as event
+ **e** send an e-mail when the job has finished
``#PBS -W depend=afterok:\ Job-Id``
``#PBS -W depend=afterok:Job-Id``
This will add a dependency to the current job. It will only be started or
tagged as startable when another job with id *Job-Id* finished
successfully.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment