UMIACS - User contributions [en]

Network/VPN/macOS

2024-05-23T17:55:08Z

Hiteesh:

'''Please note that this tutorial assumes you already have a network connection established.'''
'''If you have a UMIACS account, you already have access.'''

The UMIACS VPN is accessible through the Ivanti Connect Secure Client. Alternatively, you can establish a connection through a [https://vpn.umiacs.umd.edu/ web browser], but this may fail if you have an outdated version of Ivanti Connect Secure already installed.

'''As of May 10th 2019, MFA Authentication is mandatory.'''
==Prerequisites==
* Device enrolled with [[Duo | UMIACS Duo]]
* macOS 11.x or higher as of the current version of the Ivanti Connect Secure Client

== Connecting through the Ivanti Connect Secure client ==
#'''Download the client:'''
#:[https://obj.umiacs.umd.edu/ivanti-connectsecure/macOS/ps-pulse-mac-22.7r2-b29103-installer.dmg macOS Ivanti Connect Secure Client]
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up-to-date version of the client with the most recent configuration.''
#'''Open the client and click 'Add' (+) under the connection section.'''
#:[[Image:Ivanti client1.png|thumb|left|510px|[macOS] Click the 'Add' (+) button to create a new connection]] 
#'''In the 'Name' field, enter a descriptive name for this vpn Connection.'''
#'''In the 'Server URL' enter 'vpn.umiacs.umd.edu''''
#:[[Image:Ivanticonnection.png|thumb|left|510px|[macOS] Enter the name of the vpn server]] 
#'''Enter your UMIACS credentials and hit connect.'''
#:[[Image:Ivanticlientmac5.png|thumb|left|510px|[macOS] Enter UMIACS Credentials]] 
#'''Complete the [[Network/VPN/MFA | MFA]] Verification Step. For example, if you wish to push a notification to your device, type the word "push" into the secondary password box.
#:[[Image:SecondaryloginmacOS.png|thumb|left|510px|[macOS] Enter a secondary password.]] 
::The Ivanti VPN multi-factor authentication implementation relies on a secondary authentication source to fulfill the [[Network/VPN/MFA | MFA]] requirement. As a result, you will be prompted for credentials twice.

::{|class="wikitable"
!Second Credential Password Value:
! Result
|-
| push
| Send a push verification to your Duo connected device
|-
| phone
| Send a call verification to your Duo connected device.
|-
| <press YubiKey>
| If you have a physical token then you would press the YubiKey for the one time password.
|}

::Please note that registering a YubiKey for use with the VPN requires interaction with UMIACS Tech Staff. Please [[HelpDesk | contact us]] if you would like to register a YubiKey for this purpose.
{{Note|Pro-tip: Select ‘Save Settings’ on the secondary authentication prompt to have Duo automatically use your preferred method.}}

You should now be connected to the UMIACS VPN. You can close the window and the VPN will remain connected.

If you encounter an error, please refer to the "Setup Security Requirement" section bellow.

==Checking VPN Status==
# In the top right hand corner, on your status bar, you should see an S icon in a black circle. If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#: [[Image:CheckingVPNstatus1.png|thumb|left|610px|[macOS] The top image is connected, the bottom image is not.]] 
# You can click this icon, as well, and it will show you the status of your connection.
#:[[Image:CheckingVPN2.png|thumb|left|610px|[macOS] The Pulse drop down menu.]] 
# If the icon is not in the status bar, you can find Pulse Secure in your Applications folder. There you will see a list of connections.

==Setup Security Requirement (Follow these steps if you encounter an error while connecting through the Ivanti Secure client) ==

# Click the Apple logo at the top left of your desktop
# Click '''System Settings'''
# Click '''Privacy & Security'''
# Scroll to the '''Security''' section and select '''App Store and identified developers'''
#* You will have to enter your credentials
# Click '''Next''' to the message "System Software From Developers "Pulse Secure LLC" was blocked from loading" if prompted.
# Click '''Allow''' to enable the extension.
# Close the '''System Settings''' window.

SLURM/JobSubmission

2023-05-22T17:57:23Z

Hiteesh:

=Job Submission=
SLURM offers a variety of ways to run jobs. It is important to understand the different options available and how to request the resources required for a job in order for it to run successfully. All job submission should be done from submit nodes; any computational code should be run in a job allocation on compute nodes. The following commands outline how to allocate resources on the compute nodes and submit processes to be run on the allocated nodes.

Please note that the hard maximum number of jobs that the SLURM scheduler can handle is 10000. It is best to limit your number of submitted jobs at any given time to less than half this amount in the case that another user also wants to submit a large number of jobs.

'''Computational jobs run on submission nodes will be terminated. Please use compute nodes for running computational jobs.'''

For details on how SLURM decides how to schedule jobs when multiple jobs are waiting in a scheduler's queue, please see [[SLURM/Priority]].

==srun==
<code>srun</code> is the command used to run a process on the compute nodes in the cluster. It works by passing it a command (this could be a script) which will be run on a compute node and then <code>srun</code> will return. <code>srun</code> accepts many command line options to specify the resources required by the command passed to it. Some common command line arguments are listed below and full documentation of all available options is available in the man page for <code>srun</code>, which can be accessed by running <code>man srun</code>.

<pre>
username@nexuscml010:srun --qos=default --mem=100mb --time=1:00:00 bash -c 'echo "Hello World from" `hostname`'
Hello World from tron33.umiacs.umd.edu
</pre>

It is important to understand that <code>srun</code> is an interactive command. By default input to <code>srun</code> is broadcast to all compute nodes running your process and output from the compute nodes is redirected to <code>srun</code>. This behavior can be changed; however, '''srun will always wait for the command passed to finish before exiting, so if you start a long running process and end your terminal session, your process will stop running on the compute nodes and your job will end'''. To run a non-interactive submission that will remain running after you logout, you will need to wrap your <code>srun</code> commands in a batch script and submit it with [[#sbatch | sbatch]].

===Common srun arguments===
* <code>--mem=1gb</code> ''if no unit is given MB is assumed''
* <code>--nodes=2</code> ''if passed to srun, the given command will be run concurrently on each node''
* <code>--qos=default</code> ''to see the available QOS options on a cluster, run'' <code>show_qos</code>
* <code>--time=hh:mm:ss</code> ''time needed to run your job''
* <code>--job-name=helloWorld</code>
* <code>--output=filename</code> ''file to redirect stdout to''
* <code>--error=filename</code> ''file to redirect stderr''
* <code>--partition=$PNAME</code> ''request job run in the $PNAME partition''
* <code>--ntasks=2</code> ''request 2 "tasks" which map to cores on a CPU, if passed to srun the given command will be run concurrently on each core''
* <code>--account=accountname</code> ''use qos specific to an account''

===Interactive Shell Sessions===
An interactive shell session on a compute node can be useful for debugging or developing code that isn't ready to be run as a batch job. To get an interactive shell on a node, use <code>srun</code> to invoke a shell:
<pre>
username@nexuscml00:srun --pty --qos=default --mem 1gb --time=01:00:00 bash
username@tron33:
</pre>
'''Please do not leave interactive shells running for long periods of time when you are not working. This blocks resources from being used by everyone else.'''

==salloc==
The salloc command can also be used to request resources be allocated without needing a batch script. Running salloc with a list of resources will allocate the resources you requested, create a job, and drop you into a subshell with the environment variables necessary to run commands in the newly created job allocation. When your time is up or you exit the subshell, your job allocation will be relinquished.

<pre>
username@nexuscml00:salloc --qos=default -N 1 --mem=2gb --time=01:00:00
salloc: Granted job allocation 159
username@nexuscml00:srun /usr/bin/hostname
tron33.umiacs.umd.edu
username@nexuscml00:exit
exit
salloc: Relinquishing job allocation 159
</pre>

'''Please note that any commands not invoked with srun will be run locally on the submit node. Please be careful when using salloc.'''

==sbatch==
The sbatch command allows you to write a batch script to be submitted and run non-interactively on the compute nodes. To run a simple Hello World command on the compute nodes you could write a file, helloWorld.sh with the following contents:

<pre>
#!/bin/bash

srun bash -c 'echo Hello World from `hostname`'
</pre>

Then you need to submit the script with sbatch and request resources:

<pre>
username@nexuscml00:sbatch --qos=default --mem=1gb --time=1:00:00 helloWorld.sh
Submitted batch job 121
</pre>

SLURM will return a job number that you can use to check the status of your job with squeue:

<pre>
username@nexuscml00:squeue
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
121 tron helloWor username R 0:01 1 tron32
</pre>

====Advanced Batch Scripts====
You can also write a batch script with all of your resources/options defined in the script itself. This is useful for jobs that need to be run 10s/100s/1000s of times. You can then handle any necessary environment setup and run commands on the resources you requested by invoking commands with srun. The srun commands can also be more complex and be told to only use portions of your entire job allocation, each of these distinct srun commands makes up one "job step". The batch script will be run on the first node allocated as part of your job allocation and each job step will be run on whatever resources you tell them to. In the following example, we have a batch job that will request 2 nodes in the cluster. We then load a specific version of [[Python]] into our environment and submit two job steps, each one using one node. Since srun is blocks until the command finishes, we use the '&' operator to background the process so that both job steps can run at once; however, this means that we then need to use the wait command to block processing until all background processes have finished.

<pre>
#!/bin/bash

# Lines that begin with #SBATCH specify commands to be used by SLURM for scheduling

#SBATCH --job-name=helloWorld # sets the job name
#SBATCH --output=helloWorld.out.%j # indicates a file to redirect STDOUT to; %j is the jobid. Must be set to a file instead of a directory or else submission will fail.
#SBATCH --error=helloWorld.out.%j # indicates a file to redirect STDERR to; %j is the jobid. Must be set to a file instead of a directory or else submission will fail.
#SBATCH --time=00:05:00 # how long you think your job will take to complete; format=hh:mm:ss
#SBATCH --qos=default # set QOS, this will determine what resources can be requested
#SBATCH --nodes=2 # number of nodes to allocate for your job
#SBATCH --ntasks=4 # request 4 cpu cores be reserved for your node total
#SBATCH --ntasks-per-node=2 # request 2 cpu cores be reserved per node
#SBATCH --mem=1gb # memory required by job; if unit is not specified MB will be assumed

module load Python/2.7.9 # run any commands necessary to setup your environment

srun -N 1 --mem=512mb bash -c "hostname; python --version" & # use srun to invoke commands within your job; using an '&'
srun -N 1 --mem=512mb bash -c "hostname; python --version" & # will background the process allowing them to run concurrently
wait # wait for any background processes to complete

# once the end of the batch script is reached your job allocation will be revoked
</pre>

Another useful thing to know is that you can pass additional arguments into your sbatch scripts on the command line and reference them as <code>${1}</code> for the first argument and so on.

====More Examples====
* [[SLURM/ArrayJobs]]

===scancel===
The scancel command can be used to cancel job allocations or job steps that are no longer needed. It can be passed individual job IDs or an option to delete all of your jobs or jobs that meet certain criteria.
*<code>scancel 255</code> ''cancel job 255''
*<code>scancel 255.3</code> ''cancel job step 3 of job 255''
*<code>scancel --user username --partition=tron</code> ''cancel all jobs for username in the tron partition''

=Identifying Resources and Features=
The sinfo can show you additional features of nodes in the cluster but you need to ask it to show some non-default options using a command like <code>sinfo -o "%40N %8c %8m %20f %35G"</code>.

<pre>
username@nexuscml00:sinfo -o "%40N %8c %8m %20f %35G"
NODELIST CPUS MEMORY AVAIL_FEATURES GRES
tron[22-33,35-45] 16 128521+ rhel8,Zen,EPYC-7302 gpu:rtxa4000:4
tron[06-09,12-15,21] 16 128520+ rhel8,Zen,EPYC-7302P gpu:rtxa4000:4
tron[10-11,16-20,34] 16 128524 rhel8,Zen,EPYC-7313P gpu:rtxa4000:4
legacy00 48 128248 rhel8,Zen,EPYC-7402 (null)
legacy[01-09] 12 128436 rhel8,Xeon,E5-2620 (null)
clip07 8 257570 rhel8,Xeon,E5-2623 gpu:gtx1080ti:3
clip08 32 257565 rhel8,Xeon,E5-2683 gpu:gtx1080ti:8
clip09 32 385350 rhel8,Xeon,6130 gpu:rtx2080ti:5,gpu:gtx1080ti:3
clip00 32 257583 rhel8,Xeon,E5-2683 gpu:gtxtitanx:3
clip01 32 257583 rhel8,Xeon,E5-2683 gpu:gtxtitanx:1,gpu:gtxtitanxp:2
clip02 20 128562 rhel8,Xeon,E5-2630 gpu:gtx1080ti:3
clip03 20 128562 rhel8,Xeon,E5-2630 gpu:rtx2080ti:1,gpu:gtx1080ti:2
clip04 32 257540 rhel8,Zen,EPYC-7302 gpu:rtx3090:4
clip[05-06] 24 128523 rhel8,Zen,EPYC-7352 gpu:rtxa6000:2
gammagpu[01-03] 32 257541 rhel8,Zen,EPYC-7313 gpu:rtxa5000:8
legacy14 20 322068 rhel8,Xeon,E5-2650 gpu:gtxtitanx:4
legacy[15-16] 16 257587 rhel8,Xeon,E5-2630 gpu:teslak80:2
legacy17 44 515501 rhel8,Xeon,E5-2699 gpu:gtx1080ti:4
twist[00-01] 16 64031 rhel8,Xeon,E5-1660 (null)
twist[02-05] 48 257452 rhel8,Xeon,E5-2650 (null)
tron[00-05] 32 257540 rhel8,Zen,EPYC-7302 gpu:rtxa6000:8
tron[46-61] 48 257539 rhel8,Zen,EPYC-7352 gpu:rtxa5000:8
</pre>

Note that all of the nodes shown by this may not necessarily be in a partition you are able to submit to.

There is also a prewritten alias <code>show_nodes</code> on all of our SLURM computing clusters that shows each node's name, number of CPUs, memory, processor type (as AVAIL_FEATURES), GRES, State, and partitions that can submit to it.

You can identify further specific information about a node using [[SLURM/ClusterStatus#scontrol | scontrol]] with various flags.

=Requesting GPUs=
If you need to do processing on a GPU, you will need to request that your job have access to GPUs just as you need to request processors or CPU cores. You will also need to make sure that you submit your job to the correct partition since nodes with GPUs are often put into their own partition to prevent the nodes from being tied up by jobs that don't utilize GPUs. In SLURM, GPUs are considered "generic resources" also known as GRES. To request some number of GPUs be reserved/available for your job, you can use the flag <code>--gres=gpu:2</code>. If there are multiple types of GPUs available in the cluster and you need a specific type, you can provide the type option to the gres flag e.g. <code>--gres=gpu:rtxa5000:1</code>. If you do not request a specific type of GPU, you may be scheduled on the oldest/lowest specced GPU available.

<pre>
username@nexuscml00:srun --pty --gres=gpu:2 nvidia-smi
Thu Aug 25 15:22:15 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.129.06 Driver Version: 470.129.06 CUDA Version: 11.4 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA RTX A4000 Off | 00000000:01:00.0 Off | Off |
| 30% 23C P8 20W / 140W | 0MiB / 16376MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
| 1 NVIDIA RTX A4000 Off | 00000000:41:00.0 Off | Off |
| 30% 24C P8 15W / 140W | 0MiB / 16376MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
</pre>

Please note that your job will only be able to see/access the GPUs you requested. If you only need 1 GPU, please only request 1 GPU. The others on the node (if any) will be left available for other users.

<pre>
username@nexuscml00:srun --pty --gres=gpu:rtxa5000:1 nvidia-smi
Thu Aug 25 15:22:15 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.129.06 Driver Version: 470.129.06 CUDA Version: 11.4 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA RTX A5000 Off | 00000000:01:00.0 Off | Off |
| 30% 23C P8 20W / 230W | 0MiB / 24256MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
</pre>

As with all other flags, the <code>--gres</code> flag may also be passed to [[#sbatch | sbatch]] and [[#salloc | salloc]] rather than directly to [[#srun | srun]].

=MPI example=
To run [https://en.wikipedia.org/wiki/Message_Passing_Interface MPI] jobs, you will need to include the <code>--mpi=pmix</code> flag in your submission arguments.

<pre>
#!/usr/bin/bash
#SBATCH --job-name=mpi_test # Job name
#SBATCH --nodes=4 # Number of nodes
#SBATCH --ntasks=8 # Number of MPI ranks
#SBATCH --ntasks-per-node=2 # Number of MPI ranks per node
#SBATCH --ntasks-per-socket=1 # Number of tasks per processor socket on the node
#SBATCH --time=00:30:00 # Time limit hrs:min:sec

srun --mpi=pmix /nfshomes/username/testing/mpi/a.out
</pre>

Orders

2022-05-27T15:54:15Z

Hiteesh:

The following pages outline the procedures and best practices for creating and requesting orders.

=Personal Orders=
Please visit [https://umd.service-now.com/itsupport?id=service&service=250341bf3708c20041271f9543990e5a&t=so this page] to order personal equipment or get quotes for Apple or Dell equipment.

=UMIACS Orders=
==Requesting Orders Tickets==
===Important Considerations===
* Verbosity is always preferred to lack of critical details.
* Ticket descriptions should contain a list of specific items being ordered (provide direct links) unless you're attaching an official quote. No wishlists or links to carts.
* If it requires priority shipping, please include that in the subject of the email.

===Send email to staff===
'''Before proceeding''': If the account you plan on charging is owned by the Computer Science Department, please [https://helpdesk.cs.umd.edu/faq/iribe/equipment-peripherals consult their FAQ] for ordering the equipment you want.

Otherwise, if the account you plan on charging is owned by UMIACS: send mail to orders@umiacs.umd.edu.
* Please CC the PI for the KFS account you want to charge.
* In the body of your email:
** Specify the KFS account to charge.
** Specify the items using links or attached quotes and specify the amount of each item. '''Please do not use wishlists or carts.'''
*** Quotes must include any applicable shipping costs.
*** If ordering from numerous vendors:
**** Send one email per vendor. Otherwise, UMIACS staff will separate your request into different emails/[[Jira]] tickets anyway.
**** Specify if you want priority shipping per vendor. If no shipping speed is selected, the lowest cost shipping that still provides tracking will be used.
** Specify the purpose of the purchase (brief description). If on sponsored funds such as federal grants, the description should also provide how the purchase relates to the purpose of the project.

===When Staff Receives the Ticket===
* As long as the PI is CC'd and all needed information is present, we will go ahead and process the order.
* You will receive an email to pick up the order when it arrives.

==Submitting/Creating Order within [[Jira]]==
===Important Considerations===
* Verbosity is always preferred to lack of critical details.
* ORDERS ticket descriptions should contain a list of specific items being ordered unless you're attaching an official quote. No wishlists or links to carts.
* Always attach supporting documents (like a PDF print-out of a dell e-quote, a vendor-furnished quote, or a screen-shot of a requestor-furnished wishlist or cart.)

===Step-by-step===
*Create an Issue via the [[Jira]] web interface.
**Go to https://intranet.umiacs.umd.edu/jira/servicedesk/customer/portals.
**Select the Order option.

You will be presented with the default ordering screen. Here is a very fictitious example: 
Please note that Summary, Reporter, Account and PI are mandatory fields. 
[[File:ORDERS_main_new.png|465px|600px]]

*Requester
** If the order is being requested by CBCB, MC2, or QuICS, prepend the summary with [CBCB], [MC2], or [QuICS] respectively.
*Summary
** This should be of the format "<tt>Vendor | Brief Description</tt>".
** If the order must be placed today, this will instead be "<tt>PRIORITY TODAY | Vendor | Brief Description</tt>".
* Account
** This should be the account (KFS) to be charged. Please be as specific as possible with either account number or account description (e.g., don't say "DRIF" since there are multiple DRIF accounts, instead say "UMIACS DRIF", or "CHIB DRIF", etc.)
** In the event that a single order has multiple accounts, list them all and specify which items are being charged to what accounts (or what percent of an item is being charged to an account) in the description.
* PI
** A PI (Principal Adviser) who has approved the purchase on the KFS account.
** In some cases, multiple PIs can charge to a single KFS account.

* Description
** Provide a description of what you want to buy or provide it in a comment before you submit your order.
** When possible, provide a link to the item to be purchased.
** When purchasing through Amazon or a site that provides fulfillment for third party vendors, please state the specific vendor that is providing the item and at what price. This work to prevent errors caused by ordering from a different vendor when the site auto-updates
** It's good to be polite with your description. ex - <tt>"Hi, please purchase $requestedItems. Here are the links/relevant information: $relevantInformation. Thanks!"</tt>

File:ORDERS main new.png

2022-05-27T15:50:21Z

Hiteesh: Hiteesh uploaded a new version of File:ORDERS main new.png

CML

2020-05-05T19:41:57Z

Hiteesh:

The Center for Machine Learning ([https://ml.umd.edu CML]) at the University of Maryland is located within the Institute for Advanced Computer Studies. The CML has a cluster of computational (CPU/GPU) resources that are available to be scheduled.

= Compute Infrastructure =
Each of UMIACS' cluster computational infrastructures is accessed through the submission node. Users will need to submit jobs through the [[SLURM]] resource manager once they have logged into the submission node. Each cluster in UMIACS has different quality of service (QoS) that are '''required''' to be selected upon submission of a job. Many clusters, including this one, also have other resources such as GPUs that need to be requested for a job.

The current submission node(s) for '''CML''' are:
* <code>cmlsub00.umiacs.umd.edu</code>

The Center for Machine Learning GPU resources are a small investment from the base Center funds and a number of investments by individual faculty members. The scheduler's resources are modeled around this concept. This means there are additional Slurm accounts that users will need to be aware of if they are submitting in the non-scavenger partition.

== Partitions ==
There are two partitions to the CML [[SLURM]] computational infrastructure. If you do not specify a partition when submitting your job, you will receive the '''dpart''' partition.

* '''dpart''' - This is the default partition and job allocations are guaranteed.
* '''scavenger''' - This is the alternate partition that allows jobs longer run times and more resources but is preemptable when jobs in the '''dpart''' partition are ready to be scheduled.

== Accounts ==
The Center has a base account <code>cml</code> which has a modest number of nodes (currently 16 GPUs) total available in it. Other faculty that have invested in the cluster have an additional account provided to their sponsored accounts on the cluster, which provides a number of guaranteed GPU resources corresponding to the amount that they invested. If you do not specify a account when submitting your job, you will receive the <code>cml</code> account.

<pre>
# sacctmgr show accounts
Account Descr Org
---------- -------------------- --------------------
abhinav abhinav shrivastava cml
cml cml cml
furongh furong huang cml
john john dickerson cml
root default root account root
scavenger scavenger scavenger
sfeizi soheil feizi cml
tomg tom goldstein cml
</pre>

You can check your account associations by running the '''show_assoc''' to see the accounts you are associated with. Please contact staff@umiacs.umd.edu and CC your faculty member if you do not see the appropriate association.

<pre>
$ show_assoc
User Account Def Acct Def QOS QOS
---------- ---------- ---------- --------- ------------------------------------
tomg tomg default,high,medium
tomg cml default,medium
tomg scavenger scavenger
</pre>

You can also see the total number of Track-able Resources (TRES) allowed for each account by running the following command. Please make sure you give the appropriate account that you are looking for.

<pre>
$ sacctmgr show assoc account=tomg format=user,account,qos,grptres
User Account QOS GrpTRES
---------- ---------- -------------------- -------------
tomg gres/gpu=24
...

</pre>

== QoS ==
CML currently has 3 QoS for the '''dpart''' partition and 1 QoS for the '''scavenger''' partition. You are '''required''' to specify a QoS when submitting your job. The important part here is that in different QoS you can have a shorter/longer maximum wall time, a different total number of jobs running at once, and a different maximum number of track-able resources (TRES) for the job. In the scavenger QoS, one more constraint that you are restricted by is the total number of TRES per user (over multiple jobs).

<pre>
# show_qos
Name MaxWall MaxJobs MaxTRES MaxTRESPU
---------- ----------- ------- ------------------------------ -------------
medium 3-00:00:00 1 cpu=8,mem=64G,gres/gpu=2
default 7-00:00:00 2 cpu=4,mem=32G,gres/gpu=1
high 1-12:00:00 1 cpu=16,mem=128G,gres/gpu=4
scavenger 3-00:00:00 gres/gpu=36
</pre>

== GPUs ==
Jobs that require GPU resources need to explicitly request the resources within their job submission. This is done through Generic Resource Scheduling (GRES). Currently all nodes in the cluster are homogeneous, however in the future this may not be the case. Users may use the most generic identifier (in this case '''gpu'''), a colon, and a number to select without explicitly naming the type of GPU (ie. <code>--gres gpu:4</code> for 4 GPUs).

<pre>
$ sinfo -o "%15N %10c %10m %25f %25G"
NODELIST CPUS MEMORY AVAIL_FEATURES GRES
cml[00-09] 32 1+ (null) gpu:rtx2080ti:8
</pre>

== Job Submission and Management ==
Users should review our [[SLURM]] [[SLURM/JobSubmission | job submission]] and [[SLURM/JobStatus | job management]] documentation.

A very quick start to get an interactive shell is as follows when run on the submission node. This will allocate 1 GPU with 16GB of memory (system RAM) in the QoS default for 4 hours maximum time. If the job goes beyond these limits (either the memory allocation or the maximum time) it will be terminated immediately.

<pre>
srun --pty --gres=gpu:1 --mem=16G --qos=default --time=04:00:00 bash
</pre>

<pre>
[derek@cmlsub00:~ ] $ srun --pty --gres=gpu:1 --mem=16G --qos=default --time=04:00:00 bash
[derek@cml00:~ ] $ nvidia-smi -L
GPU 0: GeForce RTX 2080 Ti (UUID: GPU-20846848-e66d-866c-ecbe-89f2623f3b9a)
</pre>

If you are going to run in a faculty account instead of the default <code>cml</code> account you will need to specify the <code>--account=</code> flag.

=Data Storage=
Until the final storage investment arrives we have made available a temporary allocation of storage. This section is subject to change. There are 3 types of storage available to users in the CML:
* Home directories
* Project directories
* Scratch directories

== Home Directories ==
Home directories in the CML computational infrastructure are available from the Institute's [[NFShomes]] as <code>/nfshomes/USERNAME</code> where USERNAME is your username. These home directories have very limited storage and are intended for your personal files, configuration and source code. Your home directory is '''not''' intended for data sets or other large scale data holdings. Users are encouraged to utilize our [[GitLab]] infrastructure to host your code repositories.

'''NOTE''': To check your quota on this directory you will need to use the <code>quota -s</code> command.

Your home directory data is fully protected and has both snapshots and is backed up nightly.

== Project Directories ==
Users within the CML compute infrastructure can request project based allocations for up to 2TB for up to 120 days from [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu] with approval from a CML faculty member and the director of CML. These allocations will be available from '''/fs/cml-projects''' under a name that you provide when you request the allocation. Once the allocation period is over, the user will be contacted and give a window of opportunity to clean and secure their data before staff will remove the allocation.

This data is backed up nightly.

== Scratch Directories ==
Scratch data has no data protection including no snapshots and the data is not backed up. There are two types of scratch directories in the CML compute infrastructure:
* Network scratch directory
* Local scratch directories

=== Network Scratch Directory===
Users granted access to the CML compute infrastructure are each allocated '''400GB''' of network attached scratch. This is available as <code>/cmlscratch/USERNAME</code> where USERNAME is your username. This directory is '''automounted''' so you will need to <code>cd</code> into the directory or request/specify a fully qualified file path to access this.

Users may request an additional allocation of scratch space up to a total of '''800GB''' by contacting [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].

=== Local Scratch Directories===
Each computational node that a user can schedule compute jobs on has one or more local scratch directories. These are always named <code>/scratch0</code>, <code>/scratch1</code>, etc. These are almost always more performant than any other storage available to the job. However, users must stage their data within the confine of their job and stage the data out before the end of their job.

These local scratch directories will have a tmpwatch job which will '''delete unmodified data after 120 days'''. Please make sure you secure any data you write to these directories at the end of your job.

== Data sets ==
The following data sets are available read only for the Center. If there are other data sets that you would like to see curated and available, please contact [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].

{| class="wikitable"
! Data set
! Path
|-
| CelebA
| /fs/cml-datasets/CelebA
|-
| COCO
| /fs/cml-datasets/coco
|-
| ImageNet ILSVRC2012
| /fs/cml-datasets/ImageNet/ILSVRC2012
|-
| LSUN
| /fs/cml-datasets/LSUN
|-
| MegaFace
| /fs/cml-datasets/megaface
|-
| roberta
| /fs/cml-datasets/roberta
|-
| ShapeNetCore.v2
| /fs/cml-datasets/ShapeNetCore.v2
|-
| MS-Celeb-1M
| /fs/cml-datasets/MS_Celeb_aligned_112
|}

AddingUMIACSCertificateAuthority

2020-04-21T20:13:53Z

Hiteesh:

===Introduction===

When you visit webpages encrypted with SSL, you may be presented with a warning about the site's security certificate not being trusted. These are normally important screens to pay attention to on the internet as a whole and UMIACS goes to great lengths to maintain a secure environment for our users. However, it is not cost effective to provide commercial certs for all our public facing certificates. In order to keep costs down we provide a UMIACS CA (certificate authority) that enables your web browser to trust our secure webpages. The following steps explain how to import this certificate based on your preferred web browser.

===Windows===

For most Windows browsers (Chrome, Firefox, Edge and Internet Explorer), certificate authorities are handled by Windows itself. These are the steps required to accept the certificate:

*Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS Certificate Authority] to download the file.
*Open the file and click "Install Certificate"
[[File:UMIACSCA1.png]]
*In the dialog box opened, click "next"
*Choose "Place all certificates in the following store"
*Choose "Browse", in the dialog box opened, Choose "Trusted Root Certification Authorities" and click "Ok".
[[File:UMIACSCA2.png]]
*Click "Next" and then "Finish"
*If you get a Security Warning asking if you want to install this certificate, click "Yes".
[[File:UMIACSCA3.png]]
*You should Receive a success message similar to the following:
[[File:UMIACSCA4.png]]
*You may need to restart your browser for the change to take effect.

===Safari and Google Chrome (Mac macOS)===

For most macOS browsers (excluding Firefox), certificate authorities are handled by macOS itself. This process requires administrator access. If you do not have administrator access and you are using a UMIACS-supported Mac, please contact [[HelpDesk|Staff]]. Otherwise, here are the steps required to accept the certificate:

*Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS Certificate Authority]] to download the file.
*Open this file by double-clicking it
* The previous step will add the certificate for your own account, but it will not be trusted by macOS itself. If you have administrative access on your Mac, choose Always Trust: [[Image:UMIACSCA_2.png|500px]]
* Enter the administrator credentials to add this certificate for all users of the system: [[Image:UMIACSCA_3.png|500px]]
* Close the keychain access window.
* You may need to restart your browser for the change to take effect.

===Other Browsers (Unix)===

If you are using a browser other than Firefox in Unix, the process is more complicated than the above methods and may depend on your particular Unix distribution. If you need assistance with this please contact [[HelpDesk|UMIACS Staff]].

File:UMIACSCA4.png

2020-04-21T19:54:38Z

Hiteesh: Hiteesh uploaded a new version of File:UMIACSCA4.png

File:UMIACSCA3.png

2020-04-21T19:54:18Z

Hiteesh: Hiteesh uploaded a new version of File:UMIACSCA3.png

File:UMIACSCA2.png

2020-04-21T19:54:00Z

Hiteesh: Hiteesh uploaded a new version of File:UMIACSCA2.png

File:UMIACSCA1.png

2020-04-21T19:53:00Z

Hiteesh: Hiteesh uploaded a new version of File:UMIACSCA1.png

AddingUMIACSCertificateAuthority

2020-04-20T20:02:46Z

Hiteesh: /* Safari and Google Chrome (Mac macOS) */

===Introduction===

When you visit webpages encrypted with SSL, you may be presented with a warning about the site's security certificate not being trusted. These are normally important screens to pay attention to on the internet as a whole and UMIACS goes to great lengths to maintain a secure environment for our users. However, it is not cost effective to provide commercial certs for all our public facing certificates. In order to keep costs down we provide a UMIACS CA (certificate authority) that enables your web browser to trust our secure webpages. The following steps explain how to import this certificate based on your preferred web browser.

===Windows===

For most Windows browsers (Chrome, Firefox, Edge and Internet Explorer), certificate authorities are handled by Windows itself. These are the steps required to accept the certificate:

*Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS CA Root Certificate] to download the file.
*Open the file and click "Install Certificate"
[[File:UMIACSCA1.png]]
*In the dialog box opened, click "next"
*Choose "Place all certificates in the following store"
*Choose "Browse", in the dialog box opened, Choose "Trusted Root Certification Authorities" and click "Ok".
[[File:UMIACSCA2.png]]
*Click "Next" and then "Finish"
*If you get a Security Warning asking if you want to install this certificate, click "Yes".
[[File:UMIACSCA3.png]]
*You should Receive a success message similar to the following:
[[File:UMIACSCA4.png]]
*You may need to restart your browser for the change to take effect.

===Safari and Google Chrome (Mac macOS)===

For most macOS browsers (excluding Firefox), certificate authorities are handled by macOS itself. This process requires administrator access. If you do not have administrator access and you are using a UMIACS-supported Mac, please contact [[HelpDesk|Staff]]. Otherwise, here are the steps required to accept the certificate:

*Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS CA Root Certificate] to download the file.
*Open this file by double-clicking it
* The previous step will add the certificate for your own account, but it will not be trusted by macOS itself. If you have administrative access on your Mac, choose Always Trust: [[Image:UMIACSCA_2.png|500px]]
* Enter the administrator credentials to add this certificate for all users of the system: [[Image:UMIACSCA_3.png|500px]]
* Close the keychain access window.
* You may need to restart your browser for the change to take effect.

===Other Browsers (Unix)===

If you are using a browser other than Firefox in Unix, the process is more complicated than the above methods and may depend on your particular Unix distribution. If you need assistance with this please contact [[HelpDesk|UMIACS Staff]].

AddingUMIACSCertificateAuthority

2020-04-20T20:02:31Z

Hiteesh:

===Introduction===

When you visit webpages encrypted with SSL, you may be presented with a warning about the site's security certificate not being trusted. These are normally important screens to pay attention to on the internet as a whole and UMIACS goes to great lengths to maintain a secure environment for our users. However, it is not cost effective to provide commercial certs for all our public facing certificates. In order to keep costs down we provide a UMIACS CA (certificate authority) that enables your web browser to trust our secure webpages. The following steps explain how to import this certificate based on your preferred web browser.

===Windows===

For most Windows browsers (Chrome, Firefox, Edge and Internet Explorer), certificate authorities are handled by Windows itself. These are the steps required to accept the certificate:

*Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS CA Root Certificate] to download the file.
*Open the file and click "Install Certificate"
[[File:UMIACSCA1.png]]
*In the dialog box opened, click "next"
*Choose "Place all certificates in the following store"
*Choose "Browse", in the dialog box opened, Choose "Trusted Root Certification Authorities" and click "Ok".
[[File:UMIACSCA2.png]]
*Click "Next" and then "Finish"
*If you get a Security Warning asking if you want to install this certificate, click "Yes".
[[File:UMIACSCA3.png]]
*You should Receive a success message similar to the following:
[[File:UMIACSCA4.png]]
*You may need to restart your browser for the change to take effect.

===Safari and Google Chrome (Mac macOS)===

For most macOS browsers (excluding Firefox), certificate authorities are handled by macOS itself. This process requires administrator access. If you do not have administrator access and you are using a UMIACS-supported Mac, please contact [[HelpDesk|Staff]]. Otherwise, here are the steps required to accept the certificate:

*Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS CA Root Certificate] to download the file.
*open this file by double-clicking it
* The previous step will add the certificate for your own account, but it will not be trusted by macOS itself. If you have administrative access on your Mac, choose Always Trust: [[Image:UMIACSCA_2.png|500px]]
* Enter the administrator credentials to add this certificate for all users of the system: [[Image:UMIACSCA_3.png|500px]]
* Close the keychain access window.
* You may need to restart your browser for the change to take effect.

===Other Browsers (Unix)===

If you are using a browser other than Firefox in Unix, the process is more complicated than the above methods and may depend on your particular Unix distribution. If you need assistance with this please contact [[HelpDesk|UMIACS Staff]].

AddingUMIACSCertificateAuthority

2020-04-20T19:56:32Z

Hiteesh:

===Introduction===

When you visit webpages encrypted with SSL, you may be presented with a warning about the site's security certificate not being trusted. These are normally important screens to pay attention to on the internet as a whole and UMIACS goes to great lengths to maintain a secure environment for our users. However, it is not cost effective to provide commercial certs for all our public facing certificates. In order to keep costs down we provide a UMIACS CA (certificate authority) that enables your web browser to trust our secure webpages. The following steps explain how to import this certificate based on your preferred web browser.

===Windows===

For most Windows browsers (Chrome, Firefox, Edge and Internet Explorer), certificate authorities are handled by Windows itself. These are the steps required to accept the certificate:

*Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt UMIACS CA Root Certificate] to download the file.
*Open the file and click "Install Certificate"
[[File:UMIACSCA1.png]]
*In the dialog box opened, click "next"
*Choose "Place all certificates in the following store"
*Choose "Browse", in the dialog box opened, Choose "Trusted Root Certification Authorities" and click "Ok".
[[File:UMIACSCA2.png]]
*Click "Next" and then "Finish"
*If you get a Security Warning asking if you want to install this certificate, click "Yes".
[[File:UMIACSCA3.png]]
*You should Receive a success message similar to the following:
[[File:UMIACSCA4.png]]
*You may need to restart your browser for the change to take effect.

===Safari and Google Chrome (Mac macOS)===

For most macOS browsers (excluding Firefox), certificate authorities are handled by macOS itself. This process requires administrator access. If you do not have administrator access and you are using a UMIACS-supported Mac, please contact [[HelpDesk|Staff]]. Otherwise, here are the steps required to accept the certificate:

* Visit http://intranet.umiacs.umd.edu
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". Download and open this file by double-clicking it [[Image:UMIACSCA_1.png|500px]]
* The previous step will add the certificate for your own account, but it will not be trusted by macOS itself. If you have administrative access on your Mac, choose Always Trust: [[Image:UMIACSCA_2.png|500px]]
* Enter the administrator credentials to add this certificate for all users of the system: [[Image:UMIACSCA_3.png|500px]]
* Close the keychain access window.
* You may need to restart your browser for the change to take effect.

===Other Browsers (Unix)===

If you are using a browser other than Firefox in Unix, the process is more complicated than the above methods and may depend on your particular Unix distribution. If you need assistance with this please contact [[HelpDesk|UMIACS Staff]].

File:UMIACSCA4.png

2020-04-20T19:52:41Z

Hiteesh:

File:UMIACSCA3.png

2020-04-20T19:51:02Z

Hiteesh:

File:UMIACSCA2.png

2020-04-20T19:44:44Z

Hiteesh:

File:UMIACSCA1.png

2020-04-20T19:30:26Z

Hiteesh:

AddingUMIACSCertificateAuthority

2020-04-20T19:22:50Z

Hiteesh:

===Introduction===

When you visit webpages encrypted with SSL, you may be presented with a warning about the site's security certificate not being trusted. These are normally important screens to pay attention to on the internet as a whole and UMIACS goes to great lengths to maintain a secure environment for our users. However, it is not cost effective to provide commercial certs for all our public facing certificates. In order to keep costs down we provide a UMIACS CA (certificate authority) that enables your web browser to trust our secure webpages. The following steps explain how to import this certificate based on your preferred web browser.

===Windows===
Click [https://wiki.umiacs.umd.edu/umiacs/images/7/7d/CA-cert.crt CA-RooT.crt]

===Mozilla Firefox (cross-platform)===

Mozilla Firefox contains its own method of managing certificate authorities independent of your operating system. These are the steps required if you are using Firefox:

* Visit http://intranet.umiacs.umd.edu
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". [[Image:UMIACSCA_IE_1.png]] Firefox should open a "Downloading Certificate" dialog box automatically. It may look slightly different depending on your operating system or version of Firefox: [[Image:UMIACSCA_Firefox_1.png|458px]]
* Check all three boxes indicating that you fully trust this certificate authority
* Click ok.
* You may need to restart your browser for the change to take effect.

===Internet Explorer and Google Chrome (Windows)===

For most Windows browsers (excluding Firefox), certificate authorities are handled by Windows itself. These are the steps required to accept the certificate:

* Visit http://intranet.umiacs.umd.edu
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". Download and open this file [[Image:UMIACSCA_IE_1.png|border]]
* Click "Install Certificate..." towards the bottom of the dialog box [[Image:UMIACSCA_IE_2.png|376px]]
* Click Next
* Choose "Place all certificates in the following store"
* Choose "Trusted Root Certification Authorities" and click ok [[Image:UMIACSCA_IE_3.png|644px]]
* Click next and then finished. You should receive a success message similar to the following: [[Image:UMIACSCA_IE_4.png|200px]]
* You may need to restart your browser for the change to take effect.

===Safari and Google Chrome (Mac macOS)===

For most macOS browsers (excluding Firefox), certificate authorities are handled by macOS itself. This process requires administrator access. If you do not have administrator access and you are using a UMIACS-supported Mac, please contact [[HelpDesk|Staff]]. Otherwise, here are the steps required to accept the certificate:

* Visit http://intranet.umiacs.umd.edu
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". Download and open this file by double-clicking it [[Image:UMIACSCA_1.png|500px]]
* The previous step will add the certificate for your own account, but it will not be trusted by macOS itself. If you have administrative access on your Mac, choose Always Trust: [[Image:UMIACSCA_2.png|500px]]
* Enter the administrator credentials to add this certificate for all users of the system: [[Image:UMIACSCA_3.png|500px]]
* Close the keychain access window.
* You may need to restart your browser for the change to take effect.

===Other Browsers (Unix)===

If you are using a browser other than Firefox in Unix, the process is more complicated than the above methods and may depend on your particular Unix distribution. If you need assistance with this please contact [[HelpDesk|UMIACS Staff]].

AddingUMIACSCertificateAuthority

2020-04-20T19:19:15Z

Hiteesh:

===Introduction===

When you visit webpages encrypted with SSL, you may be presented with a warning about the site's security certificate not being trusted. These are normally important screens to pay attention to on the internet as a whole and UMIACS goes to great lengths to maintain a secure environment for our users. However, it is not cost effective to provide commercial certs for all our public facing certificates. In order to keep costs down we provide a UMIACS CA (certificate authority) that enables your web browser to trust our secure webpages. The following steps explain how to import this certificate based on your preferred web browser.

===Windows===
Click [[File:CA-cert.crt]]

===Mozilla Firefox (cross-platform)===

Mozilla Firefox contains its own method of managing certificate authorities independent of your operating system. These are the steps required if you are using Firefox:

* Visit http://intranet.umiacs.umd.edu
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". [[Image:UMIACSCA_IE_1.png]] Firefox should open a "Downloading Certificate" dialog box automatically. It may look slightly different depending on your operating system or version of Firefox: [[Image:UMIACSCA_Firefox_1.png|458px]]
* Check all three boxes indicating that you fully trust this certificate authority
* Click ok.
* You may need to restart your browser for the change to take effect.

===Internet Explorer and Google Chrome (Windows)===

For most Windows browsers (excluding Firefox), certificate authorities are handled by Windows itself. These are the steps required to accept the certificate:

* Visit http://intranet.umiacs.umd.edu
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". Download and open this file [[Image:UMIACSCA_IE_1.png|border]]
* Click "Install Certificate..." towards the bottom of the dialog box [[Image:UMIACSCA_IE_2.png|376px]]
* Click Next
* Choose "Place all certificates in the following store"
* Choose "Trusted Root Certification Authorities" and click ok [[Image:UMIACSCA_IE_3.png|644px]]
* Click next and then finished. You should receive a success message similar to the following: [[Image:UMIACSCA_IE_4.png|200px]]
* You may need to restart your browser for the change to take effect.

===Safari and Google Chrome (Mac macOS)===

For most macOS browsers (excluding Firefox), certificate authorities are handled by macOS itself. This process requires administrator access. If you do not have administrator access and you are using a UMIACS-supported Mac, please contact [[HelpDesk|Staff]]. Otherwise, here are the steps required to accept the certificate:

* Visit http://intranet.umiacs.umd.edu
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". Download and open this file by double-clicking it [[Image:UMIACSCA_1.png|500px]]
* The previous step will add the certificate for your own account, but it will not be trusted by macOS itself. If you have administrative access on your Mac, choose Always Trust: [[Image:UMIACSCA_2.png|500px]]
* Enter the administrator credentials to add this certificate for all users of the system: [[Image:UMIACSCA_3.png|500px]]
* Close the keychain access window.
* You may need to restart your browser for the change to take effect.

===Other Browsers (Unix)===

If you are using a browser other than Firefox in Unix, the process is more complicated than the above methods and may depend on your particular Unix distribution. If you need assistance with this please contact [[HelpDesk|UMIACS Staff]].

File:CA-cert.crt

2020-04-20T19:18:07Z

Hiteesh:

File:Mailman Step 2.png

2020-04-13T20:12:59Z

Hiteesh: Hiteesh uploaded a new version of File:Mailman Step 2.png

File:Mailman Step1.png

2020-04-13T20:12:23Z

Hiteesh: Hiteesh uploaded a new version of File:Mailman Step1.png

MailmanFAQ

2020-04-13T20:07:06Z

Hiteesh:

===How do I post to a mailing list?===
Members of a mailman list can post by sending mail to:

list-name@lists.umiacs.umd.edu
Please make sure to substitute list-name for the name of your list.

===How do I add users to a mailing list?===
* Login to the mailing list's adminstration page use your mailman admin password.

http://lists.umiacs.umd.edu/mailman/admin/MAILINGLISTNAME

* Click "Membership Management..." -> Choose "Mass Subscription".
[[File:Mailman_Step1.png]]
[[File:Mailman Step 2.png]]
* In the "Mass Subscriptions" panel, enter one address per line of users you would like to subscribe.
* Click "Submit Your Changes" button.
[[File:Mailman Step_3&4.png]]
* You can verify by choosing "Membership List" under "Membership Management..." and finding each user's address.
* After completion, click "Logout".

===How can someone subscribe without me doing anything?===
They just need to go to

http://lists.umiacs.umd.edu/mailman/listinfo/LISTNAME

and fill in the form. They can also subscribe/unsubscribe by email by sending to

LISTNAME-subscribe

or to unsubscribe,

LISTNAME-unsubscribe

In ALL of the above cases, the user will receive email confirming their action. They need to just reply to the mail for this to take affect.

===Is there an easy way to discard all messages waiting to be reviewed?===
If you have a list where non members can post but their messages are moderated, you'll have to deal with a lot of spam. After sometime, just a small percentage of them will be good posts.

The admindb page has a checkbox that allows you to discard all held messages that are marked Defer. On heavy lists with lots of spam holds, this makes clearing them much faster.

To make sure that all mail from non-members is automatically deleted, go to the privacy page followed by the sender-filter sub-page. At the bottom of the page, set to "discard" the value for "Action to take for postings from non-members for which no explicit action is defined."

On the same page, at the top, you can do the same thing for postings by members (if your list is moderated such that users can't post).

===How do I turn off HTML messages/attachments?===
On the admin page, go to the Content Filtering section.

Change "Should Mailman filter ..." to Yes.

If you leave the rest at default values, including

Yes for "Should Mailman convert text/html parts to plain text?"

your list will only distribute plain text messages with no attachments.

===How can I post from 2 or more addresses to a "members-only" list?===
If you're subscribed to a members-only list as USER@umiacs.umd.edu and accidentally post as USER@cfar.umd.edu, your message will not go through.

The solution is to actually subscribe both addresses to the list, but to disable delivery from all but one of the addresses. So in the above example, I'd subscribe USER@umiacs.umd.edu and USER@cfar.umd.edu, but I would disable delivery to USER@cfar.umd.edu.

You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled".

The list manager can disable delivery to an address by going to the membership page and clicking "no mail" next to the address in question.

===How do I change a member's password or send them their password?===
Go to the Membership Management page, click the address in question. The page that appears allows you to set a user's password or mail them their existing password by clicking on

"Email my password to me"

Note all the other options you can set for the user here.

Don't forget that members can have their password sent to them anytime they like by clicking the appropriate button on their personal page. There is no need for you to change their password if they forget their password. They just have to go to

http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME

e.g.:

http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu

===How can I restrict the list so only authorized persons can post?===
Turn on the moderation flag for all your existing users. Go to the Membership Management page, and use the Additional Member Tasks to turn on the mod flag for all users.

Then go to Privacy Options -> Sender filters and set the default_member_moderation flag to Yes so that new users are automatically set as moderated.

Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box.

Set the generic_nonmember_action to Reject or Discard.

===How do I unsubscribe users without them getting an unsubscribe message?===
By default, they will not get an unsubscribe message. You need only go to the membership page and click the "unsub" button next to each of their names and press "submit" or go to the Mass Removal subpage under Membership Management and add all the addresses into the window and click "submit".

===How do I edit a held message before approving it for the list?===
* Use the "forward this message" feature in the admindb page to forward the message to yourself.
* At the same time, discard the original held message. You may want to do this later, after you're sure the message was properly forwarded to you.
* Edit the message in your mail reader. You should include a notice in the message explaining that the list moderator has edited the message. Please use proper netiquette!
* Resend the message to the list using a Resent-To: header containing the list posting address. Also include an Approved: header containing the list's admin password.

===Why don't some messages get to the list?===
* Some lists may have spam filters turned on by staff to eliminate problems.
* These filters are under "Privacy options..." -> "Spam filters".
* The most common of these that will be applied is to restrict posts with [QUAR] in the subject.

File:Mailman Step 3&4.png

2020-04-13T20:06:49Z

Hiteesh:

File:Mailman Step1.png

2020-04-13T20:05:45Z

Hiteesh: Hiteesh uploaded a new version of File:Mailman Step1.png

File:Mailman Step 2.png

2020-04-13T20:03:11Z

Hiteesh:

File:Mailman Step1.png

2020-04-13T19:58:37Z

Hiteesh: Hiteesh uploaded a new version of File:Mailman Step1.png

File:Mailman Step1.png

2020-04-13T19:56:18Z

Hiteesh: