From f2847d6979f68cd503b01ee8d1911810c49fad8c Mon Sep 17 00:00:00 2001 From: Craig P Steffen Date: Wed, 17 Jul 2024 11:50:21 -0500 Subject: [PATCH] prelim process cleanup exp Prelim version of the process cleanup explanation. Basically this is a description of "don't do this" and "if you do that, we'll kill your processes". --- docs/source/user_guide/citizenship.rst | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/source/user_guide/citizenship.rst b/docs/source/user_guide/citizenship.rst index 85463367..3aab037c 100644 --- a/docs/source/user_guide/citizenship.rst +++ b/docs/source/user_guide/citizenship.rst @@ -6,7 +6,7 @@ What you do on the system affects others. Exercise good citizenship to ensure your activity does not adversely impact the system and the research community with whom you share it. Here are some rules of thumb: -- Do not run production jobs on the login nodes (very short time debug tests are fine). +- Do not run production applications on the login nodes (very short time debug tests are fine). - Do not stress file systems with known-harmful access patterns (many thousands of small files in a single directory). - If you encounter an issue, :ref:`submit an informative support request `; include the loaded modules (module list) and stdout/stderr messages in your email. @@ -19,4 +19,9 @@ As a Delta user, you agree to follow these acceptable/appropriate use policies: - `ACCESS Acceptable Use Policy `_ - `University of Illinois Appropriate Use of Computers and Network Systems Policy `_ -| +Login Node Process Restriction +--------------------------------- + +We prefer that users self-restrict what they run on the login nodes, as explained above on this page. Some production processes still get run on the login nodes for whatever reason. This causes problems by using up I/O slots, RAM, and processor cores on the login nodes. As a result, we have implemented automatic safeguard scripts that stop codes that appear to be applications running on the login nodes. + +If have a code running on the logins and it suddenly stops, look for an email of this format. If you don't understand why your process was killed, please send in a ticket and we'll be happy to sit down and talk to you.