Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prelim process cleanup exp #117

Draft
wants to merge 1 commit into
base: proposed_changes
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/source/user_guide/citizenship.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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 <help>`; include the loaded modules (module list) and stdout/stderr messages in your email.

Expand All @@ -19,4 +19,9 @@ As a Delta user, you agree to follow these acceptable/appropriate use policies:
- `ACCESS Acceptable Use Policy <https://access-ci.org/acceptable-use/>`_
- `University of Illinois Appropriate Use of Computers and Network Systems Policy <https://cam.illinois.edu/policies/fo-07/>`_

|
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.