https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&feedformat=atom&user=RidgeUMIACS - User contributions [en]2026-06-01T16:24:01ZUser contributionsMediaWiki 1.43.7https://wiki.umiacs.umd.edu/umiacs/index.php?title=Mailman3ListAdmin&diff=13269Mailman3ListAdmin2026-05-12T18:17:40Z<p>Ridge: </p>
<hr />
<div>=='''Draft documentation'''==<br />
<br />
This is for future systems not live ones. <br />
<br />
==Mailman3 List Administration==<br />
You must have a local password for mailman that will be uses for all mailman activity. <br />
<br />
To set or reset your mailman password visit:<br />
<br />
https://lists.umiacs.umd.edu/accounts/password/reset/<br />
<br />
<br />
===Managing a List===<br />
To manage your list, go to:<br />
<br />
https://lists.umiacs.umd.edu/accounts/login/?next=/mailman3/lists/<br />
<br />
After signing in you will see the lists that you are associated with. Click on the name of any to interact with those lists. <br />
<br />
* Just because you are the list administrator doesn't mean you're subscribed to (or you have to be subscribed to) this list.<br />
* Messages sent out aren't necessarily delivered immediately; it could take up to 5 minutes.<br />
<br />
====Membership Management====<br />
https://lists.umiacs.umd.edu/mailman3/lists/LISTNAME.lists.umiacs.umd.edu/members/member/<br />
<br />
This is where you can unsubscribe users, hide their email addresses, and more.<br />
* To subscribe other people<br />
<br />
https://lists.umiacs.umd.edu/mailman3/lists/LISTNAME.lists.umiacs.umd.edu/mass_subscribe/<br />
<br />
Please note that if the user you are adding has a UMD address, you should use that address in order to comply with the [https://umd.service-now.com/itsupport/?sys_kb_id=6b102078dbbec8d06aa4151748961927&id=kb_article_view&sysparm_rank=2&sysparm_tsqueryId=c11ba448db4788906aa4151748961904#institutional-email-standard Institutional email standard].<br />
<br />
====Posting options====<br />
https://lists.umiacs.umd.edu/mailman3/lists/LISTNAME.lists.umiacs.umd.edu/settings/message_acceptance<br />
<br />
This is where you can specify who can post to the list (is it open or moderated?), and set rules for auto-acceptance or rejection.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Mailman3ListAdmin&diff=13268Mailman3ListAdmin2026-05-12T18:16:57Z<p>Ridge: Created page with "=='''Draft documentation'''== ==Mailman3 List Administration== You must have a local password for mailman that will be uses for all mailman activity. To set or reset your mailman password visit: https://lists.umiacs.umd.edu/accounts/password/reset/ ===Managing a List=== To manage your list, go to: https://lists.umiacs.umd.edu/accounts/login/?next=/mailman3/lists/ After signing in you will see the lists that you are associated with. Click on the name of any to..."</p>
<hr />
<div>=='''Draft documentation'''==<br />
<br />
==Mailman3 List Administration==<br />
You must have a local password for mailman that will be uses for all mailman activity. <br />
<br />
To set or reset your mailman password visit:<br />
<br />
https://lists.umiacs.umd.edu/accounts/password/reset/<br />
<br />
<br />
===Managing a List===<br />
To manage your list, go to:<br />
<br />
https://lists.umiacs.umd.edu/accounts/login/?next=/mailman3/lists/<br />
<br />
After signing in you will see the lists that you are associated with. Click on the name of any to interact with those lists. <br />
<br />
* Just because you are the list administrator doesn't mean you're subscribed to (or you have to be subscribed to) this list.<br />
* Messages sent out aren't necessarily delivered immediately; it could take up to 5 minutes.<br />
<br />
====Membership Management====<br />
https://lists.umiacs.umd.edu/mailman3/lists/LISTNAME.lists.umiacs.umd.edu/members/member/<br />
<br />
This is where you can unsubscribe users, hide their email addresses, and more.<br />
* To subscribe other people<br />
<br />
https://lists.umiacs.umd.edu/mailman3/lists/LISTNAME.lists.umiacs.umd.edu/mass_subscribe/<br />
<br />
Please note that if the user you are adding has a UMD address, you should use that address in order to comply with the [https://umd.service-now.com/itsupport/?sys_kb_id=6b102078dbbec8d06aa4151748961927&id=kb_article_view&sysparm_rank=2&sysparm_tsqueryId=c11ba448db4788906aa4151748961904#institutional-email-standard Institutional email standard].<br />
<br />
====Posting options====<br />
https://lists.umiacs.umd.edu/mailman3/lists/LISTNAME.lists.umiacs.umd.edu/settings/message_acceptance<br />
<br />
This is where you can specify who can post to the list (is it open or moderated?), and set rules for auto-acceptance or rejection.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=12603GitLab2025-04-09T13:47:36Z<p>Ridge: </p>
<hr />
<div>GitLab is source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all non-[[ClassAccounts |class account]] UMIACS users 5 projects, faculty can request an extension to 25 projects, with a hard limit of 800Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab.<br />
<br />
To get started, navigate to the following URL in your browser, you will be redirected to UMIACS Single Sign On where you can login with your UMIACS credentials:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/user/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/user/markdown.md<br />
<br />
==Repository URLs== <br />
Users can clone git repos over either SSH or HTTPS. '''We recommend using SSH because it is more convenient for most users.''' The blue "Clone" button in the upper-right corner of your GitLab project page will contain the clone URL for whichever authentication method you prefer.<br />
<br />
===SSH===<br />
To use SSH, add an SSH key to your GitLab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/user/ssh.md here]. Once you have the SSH key added, you can authenticate without having to enter any credentials from the machine and account for which you created the SSH key (if your key is not password-protected).<br />
<br />
===HTTPS===<br />
The HTTPS URL can be used as well, but you will need to setup Personal Access Tokens in order to connect. Instructions to create one can be found [https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html here]. Once you have a token, you can use that as your password when prompted. You will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.<br />
<br />
==Make GitLab projects public==<br />
Making projects public grants access to everyone. Projects can only made public by the owner. To make your projects on GitLab public, follow the steps below:<br />
<br />
1. Go to your project page.<br />
<br />
2. Click on '''Settings'''.<br />
<br />
3. Scroll down to '''Project Visibility'''. Choose '''Public''' from the drop-down menu.<br />
<br />
4. Scroll down and click on '''Save Changes'''<br />
<br />
5. Scroll down to '''Repository''' under '''Project Visibility''' and select '''Everyone with access''' from the drop-down menu.<br />
<br />
6. Click on '''Save Changes'''.<br />
<br />
Now your project has become public with its repository accessible by anyone.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Data_Storage&diff=12194Data Storage2024-11-06T16:29:56Z<p>Ridge: </p>
<hr />
<div>This is a landing page for all topics related to data storage that are available at UMIACS. It is under active development.<br />
<br />
==Where can I store my data?==<br />
There is no one answer. Different types of data are used differently and have different optimal storage strategies. Trying to pick a one size fits all option will lead to things being sub-optimal overall <br />
<p><br />
Before choosing where to store any of your data, consider how you may need to interact with that data in the short-term and in the long-term, and who you might need to share the data with. You can copy data between the different types of data storage listed below, but it may be unnecessarily cumbersome if you don't choose the right place for the "master copy" of your data.<br />
<br />
* '''[[LocalDataStorage | Local data storage]]''' is best suited for data that you are actively working on. Some examples are code that you are developing or using (perhaps to run computational jobs in [[SLURM]] with), results from computational jobs that have already run but have not yet been published in a paper, or files that need to be processed by another desktop-based or server-based application.<br />
*: Data on UMIACS' local storage can be moved between different UMIACS-supported hosts and shared with other [[Accounts#UMIACS_Account | UMIACS account]] holders using common methods such as <tt>cp</tt>, File Explorer, Finder, and more.<br />
<br />
* '''[[OBJ | UMIACS' Object Store]]''' is best suited for data that is going to remain static, but needs to remain accessible for very long periods of time, such as data referenced by published papers. It is also suitable for transferring specific versions of data in and out of UMIACS via large singular files, such as archive (tar/zip/etc.) files.<br />
*: Data in UMIACS' Object Store can be moved in and out of it, to local storage (whether UMIACS' or otherwise), via its [https://obj.umiacs.umd.edu/obj built-in web interface] or one of many [[S3Clients | compatible clients]]. Data can be shared publicly via simple download links or [[OBJ/WebHosting | static websites]] that can visualize the data in a more accessible way. UMIACS account holders can sponsor [[Accounts#Guest_/_Collaborator_Account | Collaborator accounts]] for external collaborators that may need to upload and download new versions of data without needing direct access to UMIACS-supported hosts.<br />
<br />
* '''[[CloudDataStorage | Cloud data storage]]''' is best suited for collaborative data, such as simple or rich text documents, PDF forms, spreadsheets, presentations, pictures, videos, and more. Many cloud storage service providers also provide web-based apps attached to their storage service that can be used to edit these types of data without ever having to download it to a specific device.<br />
*: The methods that can be used to move data in and out of cloud storage to local storage vary based on the specific service provider, but often involve web-based or mobile app-based upload and download. Data can be shared with others across the web via accounts associated with that service provider, and often publicly via simple download links.<br />
<br />
==How can I transfer my data?==<br />
* '''[[LocalDataStorage | Local data storage]]''' is typically best transferred using commands or programs available in the operating system on which it is stored or most commonly accessed from. A number of these commands are covered [[LocalDataTransfer | here]].<br />
<br />
* '''[[OBJ | UMIACS' Object Store]]''' has a [https://obj.umiacs.umd.edu/obj built-in web interface] for transferring data in and out of it, which is usually the best option for individual or relatively small amounts of files/folders. For bulk transfers, one of many [[S3Clients | compatible clients]] can be used.<br />
<br />
* '''[[CloudDataStorage | Cloud data storage]]''' transfer methods vary based on the service provider. Most major providers will provide simple upload/download functionality, which works well for individual or relatively small amounts of files/folders. For bulk transfers, [[Rclone]] is one program that [[HelpDesk | UMIACS staff]] often uses, as it has compatibility with many major providers.<br />
<br />
==How is my data retained?==<br />
* '''[[LocalDataStorage | Local data storage]]''' is retained by [[HelpDesk | UMIACS staff]] in a number of different ways, namely:<br />
*: [[Snapshots]]: Point-in-time copies of specific file systems, easily accessible for quick restores. Taken more often than daily and retained for up to a week (see page for more details).<br />
*: [[NightlyBackups]]: Daily copies of specific file systems, sent to a backup server managed by staff. Taken daily and retained for up to 90 days.<br />
*: [[Archives]]: Final copies of specific types of data, stored on an archive server managed by staff. Taken when specific types of data is decommissioned and retained for up to 5 years (see page for more details).<br />
<br />
* '''[[OBJ | UMIACS' Object Store]]''' is not retained in any way, but decommissioned data is sent to [[Archives]].<br />
<br />
* '''[[CloudDataStorage | Cloud data storage]]''' retention policies vary based on the service provider. You can often buy additional storage or storage protection for a set price per renewal period. There is also sometimes a Trash folder that stores accidentally deleted data for some period of time, often 30 days.<br />
*: For services that UMD accounts specifically provide access to, the [https://it.umd.edu Division of IT (DIT)] documents policies [https://itsupport.umd.edu/itsupport/en?id=kb_article_view&sysparm_article=KB0012739 here].<br />
<br />
==What are some data storage best practices?==<br />
# Store data that should persist indefinitely, whether local, Object Store, or cloud, in either a faculty member's storage allocation or a shared storage allocation. This reduces the likelihood that the data is lost when any one individual who has access to it has their account decommissioned due to an expiring appointment, inactivity, bad behavior, or otherwise. This is detailed further on [[Publishing Data | this page]], specifically as it pertains to publication, and by the Division of IT [https://itsupport.umd.edu/itsupport?id=kb_article_view&sysparm_article=KB0018225#mcetoc_1hntftl5o23 here], specifically as it pertains to Google Drive.<br />
#* As an extension of this, be aware of who the actual owner of a file is in cloud data storage services. Files not owned by you in cloud storage can appear to be present in shared storage allocations or in your own personal allocation, but may in fact just be links to files owned by other individuals. If those individuals have their account decommissioned, the links to those files will no longer work, as the actual file will have been removed. The <br />
# Be aware of what the retention policy is for data in cloud data storage services '''before''' deciding to store your data there. It is much harder to negotiate restoring data with cloud storage providers than it is with [[HelpDesk | UMIACS Staff]], so ensure you are OK with accepting the risk.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&diff=11290MonthlyMaintenanceWindow2023-09-18T14:55:47Z<p>Ridge: </p>
<hr />
<div>UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.<br />
<br />
The window for each month is calculated by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday] to allow us to marshal patches released that month from Microsoft, Red Hat, Apple, and other OS and application vendors and have enough time to get our systems prepared to reboot. This translates to the window being on the '''Thursday that occurs between the 17th and the 23rd (inclusive)''' of each month. The window lasts from '''5pm-8pm'''. A list of upcoming maintenance windows is as follows, with the upcoming window in bold.<br />
<br />
<br />
* '''September 21st 2023'''<br />
* October 19th 2023<br />
* December 21st 2023<br />
* January 18th 2024<br />
* February 22nd 2024<br />
* March 21st 2024<br />
* April 18th 2024<br />
* May 23th 2024<br />
* June 20th 2024<br />
* July 18th 2024<br />
* August 22nd 2024<br />
* September 19th 2024<br />
* October 17th 2024<br />
* November 21st 2024<br />
* December 19th 2024<br />
<br />
==Archives==<br />
* January 17th 2013 - BEGIN time of 8pm-12am for this window through February 20th 2020<br />
* February 21st 2013<br />
* March 21st 2013<br />
* April 18th 2013<br />
* May 23rd 2013<br />
* June 20th 2013<br />
* July 18th 2013<br />
* August 22nd 2013<br />
* September 19th 2013<br />
* October 17th 2013<br />
* December 19th 2013<br />
* January 23rd 2014<br />
* February 20th 2014<br />
* March 20th 2014<br />
* April 17th 2014<br />
* May 22nd 2014<br />
* June 19th 2014<br />
* July 17th 2014<br />
* August 21st 2014<br />
* September 18th 2014<br />
* October 23rd 2014<br />
* November 20th 2014<br />
* December 18th 2014<br />
* January 22nd 2015<br />
* February 19th 2015<br />
* March 19th 2015<br />
* May 21st 2015<br />
* June 18th 2015<br />
* July 23rd 2015<br />
* August 20th 2015<br />
* September 17th 2015<br />
* October 22nd 2015<br />
* November 19th 2015<br />
* December 17th 2015<br />
* January 21st 2016<br />
* February 18th 2016<br />
* March 12th 2016 (Adjusted date for AVW power outage)<br />
* April 21st 2016<br />
* May 19th 2016<br />
* June 23rd 2016<br />
* July 21st 2016<br />
* August 18th 2016<br />
* September 22nd 2016<br />
* October 20th 2016<br />
* November 17th 2016<br />
* December 22nd 2016<br />
* January 19th 2017<br />
* February 23rd 2017<br />
* March 23rd 2017<br />
* April 20th 2017<br />
* May 18th 2017<br />
* June 22nd 2017<br />
* July 20th 2017<br />
* August 17th 2017<br />
* September 21st 2017<br />
* October 19th 2017<br />
* December 21st 2017<br />
* January 18th 2018<br />
* February 22nd 2018<br />
* March 22nd 2018<br />
* April 19th 2018<br />
* May 17th 2018<br />
* June 21st 2018<br />
* July 19th 2018<br />
* August 23rd 2018<br />
* September 20th 2018<br />
* October 18th 2018<br />
* December 20th 2018<br />
* January 24th 2019<br />
* February 21st 2019<br />
* April 18th 2019<br />
* May 23rd 2019<br />
* June 20th 2019<br />
* July 18th 2019<br />
* August 22nd 2019<br />
* September 19th 2019<br />
* October 17th 2019<br />
* November 21st 2019<br />
* December 19th 2019<br />
* January 23rd 2020<br />
* February 20th 2020<br />
* April 23rd 2020 - BEGIN time of 5pm-7pm for this window through August 19th 2021<br />
* June 18th 2020<br />
* July 23rd 2020<br />
* August 20th 2020<br />
* September 17th 2020<br />
* October 22nd 2020<br />
* November 19th 2020<br />
* December 17th 2020<br />
* January 21st 2021<br />
* February 18th 2021<br />
* March 25th 2021 (Adjusted date for extended Spring Break)<br />
* April 22nd 2021<br />
* May 20th 2021<br />
* June 17th 2021<br />
* July 22nd 2021<br />
* August 19th 2021<br />
* September 23rd 2021 - BEGIN time of 5-8pm for this window and all others below<br />
* October 21st 2021<br />
* November 18th 2021<br />
* January 20th 2022<br />
* February 17th 2022<br />
* March 24th 2022 (Adjusted date for Spring Break)<br />
* April 21st 2022<br />
* May 19th 2022<br />
* June 23rd 2022<br />
* July 21st 2022<br />
* August 18th 2022<br />
* September 22nd 2022<br />
* October 20th 2022<br />
* November 17th 2022<br />
* January 19th 2023<br />
* February 23rd 2023<br />
* April 20th 2023<br />
* May 18th 2023<br />
* June 22nd 2023<br />
* July 20th 2023<br />
* August 17th 2023</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Nexus/CML&diff=11284Nexus/CML2023-09-11T20:23:22Z<p>Ridge: </p>
<hr />
<div>The [[CML]] standalone cluster's compute nodes have folded into [[Nexus]] as of the scheduled [[MonthlyMaintenanceWindow | maintenance window]] for August (Thursday 8/17, 5-8pm).<br />
<br />
The Nexus cluster already has a large pool of compute resources made possible through leftover funding for the [[Iribe | Brendan Iribe Center]]. Details on common nodes already in the cluster (Tron partition) can be found [[Nexus/Tron | here]].<br />
<br />
The CML cluster's standalone submission node <code>cmlsub00.umiacs.umd.edu</code> will be retired on Thursday, September 21st, 2023 during that month's maintenance window (5-8pm), as it is no longer able to submit jobs to CML compute nodes. Please use <code>nexuscml00.umiacs.umd.edu</code> and <code>nexuscml01.umiacs.umd.edu</code> for any general purpose CML compute needs after this time.<br />
<br />
Please see the [[#Timeline | Timeline]] section below for concrete dates in chronological order.<br />
<br />
Please [[HelpDesk | contact staff]] with any questions or concerns.<br />
<br />
==Usage==<br />
The Nexus cluster submission nodes that are allocated to CML are <code>nexuscml00.umiacs.umd.edu</code> and <code>nexuscml01.umiacs.umd.edu</code>. '''You must use these nodes to submit jobs to CML compute nodes.''' Submission from <code>cmlsub00.umiacs.umd.edu</code> is no longer available.<br />
<br />
All partitions, QoSes, and account names from the standalone CML cluster have been moved over to Nexus. However, please note that <code>cml-</code> is prepended to all of the values that were present in the standalone CML cluster to distinguish them from existing values in Nexus. The lone exception is the base account that was named <code>cml</code> in the standalone cluster (it is also named just <code>cml</code> in Nexus).<br />
<br />
Here are some before/after examples of job submission with various parameters:<br />
<br />
{| class="wikitable"<br />
! Standalone CML cluster submission command<br />
! Nexus cluster submission command<br />
|-<br />
|<code>srun --partition=dpart --qos=medium --account=tomg --gres=gpu:rtx2080ti:2 --pty bash</code><br />
|<code>srun --partition=cml-dpart --qos=cml-medium --account=cml-tomg --gres=gpu:rtx2080ti:2 --pty bash</code><br />
|-<br />
|<code>srun --partition=cpu --qos=cpu --pty bash</code><br />
|<code>srun --partition=cml-cpu --qos=cml-cpu --account=cml --pty bash</code><br />
|-<br />
|<code>srun --partition=scavenger --qos=scavenger --account=scavenger --gres=gpu:4 --pty bash</code><br />
|<code>srun --partition=cml-scavenger --qos=cml-scavenger --account=cml-scavenger --gres=gpu:4 --pty bash</code><br />
|}<br />
<br />
CML users (exclusively) can schedule non-interruptible jobs on CML nodes with any non-scavenger job parameters. Please note that the <code>cml-dpart</code> partition has a <code>GrpTRES</code> limit of 100% of the available cores/RAM on all cml## nodes in aggregate plus 50% of the available cores/RAM on legacy## nodes, so your job may need to wait if all available cores/RAM (or GPUs) are in use. It also has a max submission limit of 500 jobs per user simultaneously so as to not overload the cluster. This is codified by the partition QoS named '''cml'''.<br />
<br />
Please note that the CML compute nodes are also in the institute-wide <code>scavenger</code> partition in Nexus. CML users still have scavenging priority over these nodes via the <code>cml-scavenger</code> partition (i.e., all <code>cml-</code> partition jobs (other than <code>cml-scavenger</code>) can preempt both <code>cml-scavenger</code> and <code>scavenger</code> partition jobs, and <code>cml-scavenger</code> partition jobs can preempt <code>scavenger</code> partition jobs).<br />
<br />
==Partitions==<br />
There are three partitions available to general CML [[SLURM]] users. You must specify a partition when submitting your job.<br />
<br />
* '''cml-dpart''' - This is the default partition. Job allocations are guaranteed.<br />
* '''cml-scavenger''' - This is the alternate partition that allows jobs longer run times and more resources but is preemptable when jobs in other <code>cml-</code> partitions are ready to be scheduled.<br />
* '''cml-cpu''' - This partition is for CPU focused jobs. Job allocations are guaranteed.<br />
<br />
There is one additional partition available solely to Furong's sponsored accounts.<br />
<br />
* '''cml-furongh''' - This partition is for exclusive priority access to Furong's purchased A6000 node.<br />
<br />
==Accounts==<br />
The Center has a base SLURM account <code>cml</code> which has a modest number of guaranteed billing resources available to all cluster users at any given time. 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 billing resources corresponding to the amount that they invested.<br />
<br />
If you do not specify an account when submitting your job, you will receive the <code>cml</code> account. If your faculty sponsor has their own account, it is recommended to use that account for job submission.<br />
<br />
The current faculty accounts are:<br />
* cml-abhinav<br />
* cml-cameron<br />
* cml-furongh<br />
* cml-hajiagha<br />
* cml-john<br />
* cml-ramani<br />
* cml-sfeizi<br />
* cml-tokekar<br />
* cml-tomg<br />
<br />
<pre><br />
$ sacctmgr show account format=account%20,description%30,organization%10<br />
Account Descr Org<br />
-------------------- ------------------------------ ----------<br />
... ... ...<br />
cml cml cml<br />
cml-abhinav cml - abhinav shrivastava cml<br />
cml-cameron cml - maria cameron cml<br />
cml-furongh cml - furong huang cml<br />
cml-hajiagha cml - mohammad hajiaghayi cml<br />
cml-john cml - john dickerson cml<br />
cml-ramani cml - ramani duraiswami cml<br />
cml-scavenger cml - scavenger cml<br />
cml-sfeizi cml - soheil feizi cml<br />
cml-tokekar cml - pratap tokekar cml<br />
cml-tomg cml - tom goldstein cml<br />
... ... ...<br />
</pre><br />
<br />
Faculty can manage this list of users via our [https://intranet.umiacs.umd.edu/directory/secgroup/ Directory application] in the Security Groups section. The security group that controls access has the prefix <code>cml_</code> and then the faculty username. It will also list <code>slurm://nexusctl.umiacs.umd.edu</code> as the associated URI.<br />
<br />
You can check your account associations by running the '''show_assoc''' command to see the accounts you are associated with. Please [[HelpDesk | contact staff]] and include your faculty member in the conversation if you do not see the appropriate association. <br />
<br />
<pre><br />
$ show_assoc<br />
User Account MaxJobs GrpTRES QOS<br />
---------- ---------------- ------- ------------- --------------------------------------------------<br />
... ... ...<br />
tomg cml cml-cpu,cml-default,cml-medium<br />
tomg cml-scavenger cml-scavenger<br />
tomg cml-tomg cml-default,cml-high,cml-medium<br />
... ... ...<br />
</pre><br />
<br />
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. The billing number displayed here is the sum of [[SLURM/Priority#Modern | resource weightings]] for all nodes appropriated to that account.<br />
<br />
<pre><br />
$ sacctmgr show assoc account=cml format=user,account,qos,grptres<br />
User Account QOS GrpTRES<br />
---------- ---------- -------------------- -------------<br />
cml billing=7732<br />
... ...<br />
</pre><br />
<br />
==QoS==<br />
CML currently has 5 QoS for the '''cml-dpart''' partition (though <code>high_long</code> and <code>very_high</code> may not be available to all faculty accounts), 1 QoS for the '''cml-scavenger''' partition, and 1 QoS for the '''cml-cpu''' partition. If you do not specify a QoS when submitting your job using the <code>--qos</code> parameter, you will receive the '''cml-default''' QoS assuming you are using a CML account.<br />
<br />
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 cml-scavenger QoS, one more constraint that you are restricted by is the total number of TRES per user (over multiple jobs). <br />
<br />
<pre><br />
$ show_qos<br />
Name MaxWall MaxTRES MaxJobsPU MaxSubmitPU MaxTRESPU GrpTRES<br />
-------------------- ----------- ------------------------------ --------- ----------- ------------------------------ --------------------<br />
... ... ... ... ... ... ...<br />
cml-default 7-00:00:00 cpu=4,gres/gpu=1,mem=32G 2<br />
cml-medium 3-00:00:00 cpu=8,gres/gpu=2,mem=64G 2<br />
cml-high 1-12:00:00 cpu=16,gres/gpu=4,mem=128G 2<br />
cml-scavenger 3-00:00:00 gres/gpu=24<br />
cml-cpu 7-00:00:00 8<br />
cml-very_high 1-12:00:00 cpu=32,gres/gpu=8,mem=256G 8 gres/gpu=12<br />
cml-high_long 14-00:00:00 cpu=32,gres/gpu=8 8 gres/gpu=8<br />
cml 500 cpu=252,mem=2884G<br />
... ... ... ... ... ... ...<br />
</pre><br />
<br />
==Storage==<br />
There are 3 types of user storage available to users in the CML:<br />
* Home directories<br />
* Project directories<br />
* Scratch directories<br />
<br />
There are also 2 types of read-only storage available for common use among users in the CML:<br />
* Dataset directories<br />
* Model directories<br />
<br />
CML users can also request [[Nexus#Project_Allocations | Nexus project allocations]].<br />
<br />
===Home Directories===<br />
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 (30GB, cannot be increased) 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.<br />
<br />
'''NOTE''': To check your quota on this directory you will need to use the <code>quota -s</code> command.<br />
<br />
Your home directory data is fully protected and has both [[Snapshots | snapshots]] and is [[NightlyBackups | backed up nightly]].<br />
<br />
===Project Directories===<br />
You can request project based allocations for up to 6TB for up to 120 days with approval from a CML faculty member and the director of CML. <br />
<br />
To request an allocation, please [[HelpDesk | contact staff]] with the faculty member(s) that the project is under involved in the conversation. Please include the following details:<br />
* Project Name (short)<br />
* Description<br />
* Size (1TB, 2TB, etc.)<br />
* Length in days (30 days, 90 days, etc.)<br />
* Other user(s) that need to access the allocation, if any<br />
<br />
These allocations will be available from '''/fs/cml-projects''' under a name that you provide when you request the allocation. Near the end of the allocation period, staff will contact you and ask if you would like to renew the allocation for up to another 120 days (requires re-approval from a CML faculty member and the director of CML). If you are no longer in need of the storage allocation, you will need to relocate all desired data within two weeks of the end of the allocation period. Staff will then remove the allocation. If you or the original faculty approver do not respond to staff's request or within one month of the end of the allocation period, staff will remove the allocation.<br />
<br />
This data is backed up nightly.<br />
<br />
===Scratch Directories===<br />
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:<br />
* Network scratch directory<br />
* Local scratch directories<br />
<br />
====Network Scratch Directory====<br />
You are allocated 400GB of scratch space via NFS from <code>/cmlscratch/$username</code>. '''It is not backed up or protected in any way.''' 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.<br />
<br />
You may request a permanent increase of up to 800GB total space without any faculty approval by [[HelpDesk | contacting staff]]. If you need space beyond 800GB, you will need faculty approval and/or a project directory. Space increases beyond 800GB also have a maximum request period of 120 days (as with project directories), after which they will need to be renewed with re-approval from a CML faculty member and the director of CML.<br />
<br />
This file system is available on all submission, data management, and computational nodes within the cluster.<br />
<br />
====Local Scratch Directories====<br />
Each computational node that you 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, you must stage data to these directories within the confines of your jobs and stage the data out before the end of your jobs.<br />
<br />
These local scratch directories have a tmpwatch job which will '''delete unaccessed data after 90 days''', scheduled via maintenance jobs to run once a month during our monthly maintenance windows. Again, please make sure you secure any data you write to these directories at the end of your job.<br />
<br />
===Datasets===<br />
We have read-only dataset storage available at <code>/fs/cml-datasets</code>. If there are datasets that you would like to see curated and available, please see [[Datasets | this page]].<br />
<br />
The following is the list of datasets available:<br />
{| class="wikitable"<br />
! Dataset<br />
! Path<br />
|-<br />
| CelebA<br />
| /fs/cml-datasets/CelebA<br />
|-<br />
| CelebA-HQ<br />
| /fs/cml-datasets/CelebA-HQ<br />
|-<br />
| CelebAMask-HQ<br />
| /fs/cml-datasets/CelebAMask-HQ<br />
|-<br />
| Charades<br />
| /fs/cml-datasets/Charades<br />
|-<br />
| Cityscapes<br />
| /fs/cml-datasets/cityscapes<br />
|-<br />
| COCO<br />
| /fs/cml-datasets/coco<br />
|-<br />
| Diversity in Faces [1]<br />
| /fs/cml-datasets/diversity_in_faces<br />
|-<br />
| FFHQ<br />
| /fs/cml-datasets/FFHQ<br />
|-<br />
| ImageNet ILSVRC2012<br />
| /fs/cml-datasets/ImageNet/ILSVRC2012<br />
|-<br />
| LFW<br />
| /fs/cml-datasets/facial_test_data<br />
|-<br />
| LibriSpeech<br />
| /fs/cml-datasets/LibriSpeech<br />
|-<br />
| LSUN<br />
| /fs/cml-datasets/LSUN<br />
|-<br />
| MAG240M<br />
| /fs/cml-datasets/OGB/MAG240M<br />
|-<br />
| MegaFace<br />
| /fs/cml-datasets/megaface<br />
|-<br />
| MS-Celeb-1M<br />
| /fs/cml-datasets/MS_Celeb_aligned_112<br />
|-<br />
| OC20<br />
| /fs/cml-datasets/OC20<br />
|-<br />
| ogbn-papers100M<br />
| /fs/cml-datasets/OGB/ogbn-papers100M<br />
|-<br />
| roberta<br />
| /fs/cml-datasets/roberta<br />
|-<br />
| Salient ImageNet<br />
| /fs/cml-datasets/Salient-ImageNet<br />
|-<br />
| ShapeNetCore.v2<br />
| /fs/cml-datasets/ShapeNetCore.v2<br />
|-<br />
| Tiny ImageNet<br />
| /fs/cml-datasets/tiny_imagenet<br />
|-<br />
| WikiKG90M<br />
| /fs/cml-datasets/OGB/WikiKG90M<br />
|}<br />
<br />
[1] - This dataset has restricted access. Please [[HelpDesk | contact staff]] if you are looking to use this dataset.<br />
<br />
===Models===<br />
We have read-only model storage available at <code>/fs/cml-models</code>. If there are models that you would like to see downloaded and made available, please see [[Datasets | this page]].<br />
<br />
==Timeline==<br />
Each event will be completed within the timeframe specified.<br />
<br />
{| class="wikitable"<br />
! Date<br />
! Event<br />
|-<br />
| July 14th 2023<br />
| A single compute node <code>cml03</code> is moved into Nexus so submission can be tested<br />
|- <br />
| [[MonthlyMaintenanceWindow | August 17th 2023, 5-8pm]]<br />
| All other standalone CML cluster compute nodes are moved into Nexus in corresponding <code>cml-</code> named partitions<br />
|- <br />
| [[MonthlyMaintenanceWindow | September 21st 2023, 5-8pm]]<br />
| <code>cmlsub00.umiacs.umd.edu</code> is taken offline<br />
|- <br />
|}</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Accounts&diff=11154Accounts2023-08-03T13:52:14Z<p>Ridge: </p>
<hr />
<div>This page outlines the various account types at UMIACS and their management methods.<br />
<br />
'''Do not share any UMIACS-affiliated account for any purpose. Action may be taken against your account if you do so.'''<br />
<br />
==UMIACS Account==<br />
A traditional UMIACS account consists of the following components:<br />
; [[ActiveDirectory | Active Directory Account]]<br />
: Provides access to UMIACS-supported computers, email, [[SecGroups | secgroup]] controlled resources, web services, and the [[VPN]].<br />
; [[Jira | Jira Account]]<br />
: Provides access to the JIRA Request Tracker. Please note that it is possible to set a separate password for this account, at which point it will no longer be synced from your Active Directory Account. Changing your Jira password DOES NOT change your Active Directory Account password.<br />
<br />
==Guest / Collaborator Account==<br />
; [[Accounts/Collaborator | Collaborator Accounts]]<br />
: Sponsored account to provide temporary access to UMIACS Web Services for non-UMIACS collaborators.<br />
<br />
==Request a UMIACS account==<br />
Fill out the account request form located at the [https://intranet.umiacs.umd.edu/requests/accounts/new UMIACS Account Request webapp]. Please note that for the PI field you will be entering your PI/Professor/Sponsor's account name here at UMIACS. Also indicate any labs you are a member of in the notes field to speed up access to your lab's resources. <br />
<br />
Once the form is submitted, it will send an email with a link to verify your email address. You must click this link to verify your email address before the system will send email to your PI to review the account request. Accounts can take anywhere from a few hours to a day for installation, depending on how quickly your PI approves your account.<br />
<br />
==Password Requirements==<br />
We have the following policies in regards to our [[ActiveDirectory]] passwords:<br />
* Minimum Password Length : 8 Characters (more is allowed)<br />
* Minimum Character Classes : 3 Character Classes<br />
** English uppercase characters (A - Z)<br />
** English lowercase characters (a - z)<br />
** Base 10 digits (0 - 9)<br />
** Non-alphanumeric (For example: !, $, #, or %)<br />
** Unicode characters<br />
* Password cannot contain (or match a substring of 3+ sequential characters) of your username or any part of your first or last name.<br />
* Password was not previously used in last 5 passwords.<br />
* Password has not been [[CompromisedPasswordFiltering | compromised]] in a known data breach.<br />
<br />
It is your responsibility to secure your password. Please try to choose a strong password and use secure protocols.<br />
<br />
==Changing account password==<br />
===If you know your current password===<br />
# You can use the [https://intranet.umiacs.umd.edu/password UMIACS Password Web Application] to change your password.<br />
<br />
===If you do not know your current password===<br />
# You can [https://intranet.umiacs.umd.edu/password/forgot reset your password yourself] if you know your username and have already registered a mobile phone number and alternate E-mail address in our [https://intranet.umiacs.umd.edu/directory/info/ Directory Application].<br />
# If your account was a UMIACS Collaborator Account, your password can be reset by your sponsor via our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/ Requests Application].<br />
# You can stop by the UMIACS Help Desk in room 3109 Iribe Center with a photo ID.<br />
#* If you are unable to physically stop by the UMIACS Help Desk, you can have your account sponsor (PI) work with the UMIACS Help Desk to receive a temporary password on your behalf. The account sponsor will then be responsible for conveying the password to you in a secure manner. (e.g., Telephone, where they could identify you by voice)<br />
<br />
==Sponsored Accounts==<br />
You can view a list of the accounts you sponsor in the [https://intranet.umiacs.umd.edu/requests/accounts/sponsored/ UMIACS Account Management Web Application]. Clicking on an account's display name will bring you to a management page where you can see details such as the installation date or email forward. From here you can edit your relationship to the account.<br />
<br />
You can also request to remove your sponsorship or modify the expiration date, but these require staff action and are not immediate. <br />
<br />
==All Accounts Related Pages==<br />
{{Special:PrefixIndex/Accounts/}}</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=LabFacilities&diff=10355LabFacilities2022-04-08T18:08:50Z<p>Ridge: </p>
<hr />
<div>* [[CBCB | Center for Bioinformatics and Computational Biology]] ([http://www.cbcb.umd.edu CBCB]) <br />
* Center for Digital International Government ([http://www.umiacs.umd.edu/research/CDIG CDIG]) <br />
* Center for Automation Research ([http://www.cfar.umd.edu/ CfAR])<br />
* Center for Health-related Informatics and Bioimaging ([http://www.chib.umd.edu/ CHIB]) <br />
* Computational Linguistics and Information Processing ([https://wiki.umiacs.umd.edu/clip/index.php/Main_Page CLIP]) <br />
* Center for Machine Learning ([https://ml.umd.edu CML])<br />
* Computer Vision Laboratory ([http://www.cfar.umd.edu/cvl/ CVL]) <br />
* Distributed Systems Software Laboratory ([http://www.cs.umd.edu/projects/dssl DSSL]) <br />
* Fraunhofer Center at Maryland ([https://www.cese.fraunhofer.org/ FCMD])<br />
* Human Computer Interaction Laboratory ([http://hcil.umd.edu/ HCIL]) <br />
* Graphics and Visual Informatics Laboratory ([http://www.cs.umd.edu/gvil/ GVIL])<br />
* Language and Media processing laboratory ([http://lamp.cfar.umd.edu/ LAMP])<br />
* Laboratory for Parallel and Distributed Computing ([http://www.umiacs.umd.edu/labs/parallel/index.htm LPDC])<br />
* Laboratory for Telecommunication Sciences ([http://www.ltsnet.net/ LTS])<br />
* Lab for Broadband Mobile Communications ([http://www.umiacs.umd.edu/research/maxwell/ MAXWell])<br />
* Maryland Cybersecurity Center ([http://cyber.umd.edu/ MC2])<br />
* Joint Center for Quantum Information and Computer Science ([https://quics.umd.edu/ QUICS])<br />
* National Socio-Environmental Synthesis Center ([https://www.sesync.org/ SESYNC])</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Archives&diff=9161Archives2020-04-30T21:28:11Z<p>Ridge: </p>
<hr />
<div>=UMIACS Archives=<br />
<br />
When UMIACS archives data we hold onto the archive for a period of 5 years.<br />
<br />
In general we archive the following:<br />
<br />
* the primary drive from hosts with persistent local data (Windows, macOS)<br />
* accounts that are archived and deleted (including metadata, network home directory and GitLab)<br />
<br />
We may not archive the following:<br />
<br />
* tmp and scratch directories (as discussed on our page about [[LocalDataStorage |data sotrage]])<br />
* external drives that were attached to a machine<br />
* Data that migrated forward to a new machine<br />
* Data that was handed off into the care of the end-user or PI<br />
* Data from drives that failed and was not under backup protection, that is unavailable for us to archive<br />
* Data from self supported machines</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Archives&diff=9160Archives2020-04-30T21:26:36Z<p>Ridge: </p>
<hr />
<div>=UMIACS Archives=<br />
<br />
When UMIACS archives data we hold onto the archive for a period of 5 years.<br />
<br />
In general we archive the following:<br />
<br />
* hosts with persistent local data (Windows, macOS)<br />
* accounts that are archived and deleted (including metadata, network home directory and GitLab)<br />
<br />
We may not archive the following:<br />
<br />
* tmp and scratch directories (as discussed on our page about [[LocalDataStorage |data sotrage]])<br />
* external drives that were attached to a machine<br />
* Data that migrated forward to a new machine<br />
* Data that was handed off into the care of the end-user or PI</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Iribe/ConferenceRooms/Moderated&diff=8337Iribe/ConferenceRooms/Moderated2019-05-01T13:57:18Z<p>Ridge: </p>
<hr />
<div>These signature [[Iribe/ConferenceRooms | rooms]] have a primary coordinator and a backup moderator. The touch panels will not accept walk up reservations for these rooms; all reservations need to go through the moderation process. You may [[Iribe/ConferenceRooms/Reserve | create a reservation]] by adding the room in Google Calendar. The moderator will be notified and can approve your request.<br />
<br />
Instructions on reserving a room are [[Iribe/ConferenceRooms/Reserve | here]].<br />
<br />
{| class="wikitable"<br />
! Room<br />
! Occupancy<br />
! Primary Moderator<br />
! Backup<br />
|-<br />
| IRB-1127<br />
| 12<br />
| Danae Johnson<br />
| Stephanie Peters<br />
|-<br />
| IRB-2137<br />
| 12<br />
| Stephanie Peters<br />
| Danae Johnson<br />
|-<br />
| IRB-3137<br />
| 24<br />
| Elizabeth Hontz<br />
| Danae Johnson<br />
|-<br />
| IRB-3256<br />
| 8<br />
| Barbara Lewis<br />
| Danae Johnson<br />
|-<br />
| IRB-4105<br />
| 48<br />
| Stephanie Peters<br />
| Elizabeth Hontz<br />
|-<br />
| IRB-4107<br />
| 20<br />
| Stephanie Peters<br />
| Elizabeth Hontz<br />
|-<br />
| IRB-4109<br />
| 20<br />
| Stephanie Peters<br />
| Elizabeth Hontz<br />
|-<br />
| IRB-4137<br />
| 12<br />
| Elizabeth Hontz<br />
| Danae Johnson<br />
|-<br />
| IRB-4237<br />
| 12<br />
| Janice Perrone<br />
| Danae Johnson<br />
|-<br />
| IRB-5105<br />
| 24<br />
| Stephanie Peters<br />
| Emily Hartz<br />
|-<br />
| IRB-5137<br />
| 18<br />
| Stephanie Peters<br />
| Emily Hartz<br />
|-<br />
| IRB-5165<br />
| 16<br />
| Stephanie Peters<br />
| Emily Hartz<br />
|-<br />
| IRB-5237<br />
| 12<br />
| Dana Purcell<br />
| Danae Johnson<br />
|}<br />
<br />
=== Large Seminar Capabilities ===<br />
'''3137''' and '''4105''' are the two large seminar rooms.<br />
<br />
* Dual Display (Projector and LCD)<br />
* Dual camera conferencing via room PC<br />
* Laptop presentation via HDMI or Mersive Solstice<br />
* Blu-ray playback, tuner<br />
* Lectern<br />
<br />
===Small Seminar and Large Conference Room Capabilities ===<br />
Every other room on this page has the following setup.<br />
<br />
* Single Display (LCD)<br />
* Single camera conferencing via room PC<br />
* Laptop presentation via HDMI or Mersive Solstice</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=HelpDesk&diff=8199HelpDesk2019-03-31T20:17:37Z<p>Ridge: </p>
<hr />
<div>The UMIACS Help Desk provides Technical Support and Equipment procurement.<br />
<br />
; Help Desk Location<br />
: 3109 Brendan Iribe Center for Computer Science and Engineering<br />
; Help Desk Hours<br />
: 9:00am - 5:00pm Monday - Friday. (Excluding University Holidays)<br />
<br />
==How to Contact Support==<br />
; Email<br />
: [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]<br />
; Telephone<br />
: 301-405-1775<br />
; [[Jira | JIRA Request Tracker]]</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Accounts&diff=8198Accounts2019-03-31T20:14:35Z<p>Ridge: </p>
<hr />
<div>This page outlines the various account types at UMIACS and their management methods.<br />
<br />
==UMIACS Account==<br />
A traditional UMIACS account consists of the following components:<br />
; [[ActiveDirectory | Active Directory Account]]<br />
: Provides access to UMIACS-supported computers, email, secgroup controlled resources, web services, and the VPN.<br />
; [[Jira | Jira Account]]<br />
: Provides access to the JIRA Request Tracker. Please note that it is possible to set a separate password for this account, at which point it will no longer be synced from your Active Directory Account. Changing your Jira password DOES NOT change your Active Directory Account password.<br />
<br />
==Guest / Collaborator Account==<br />
; [[Accounts/Collaborator | Collaborator Accounts]]<br />
: Sponsored account to provide temporary access to UMIACS Web Services for non-UMIACS collaborators.<br />
<br />
==Request a UMIACS account==<br />
Fill out the account request form located at the [https://intranet.umiacs.umd.edu/requests/accounts/new UMIACS Account Request webapp]. Please note that for the PI field you will be entering your PI/Professor/Sponsor's account name here at UMIACS. Also indicate any labs you are a member of in the notes field to speed up access to your lab's resources. <br />
<br />
Once the form is submitted, it will return to you your initial password for your accounts, please keep it. If you forget your password, you can always come to the UMIACS Helpdesk in 3109 IRB with a photo ID to reset it. Accounts can take anywhere from a few hours to a day for installation, depending on how quickly your PI approves your account.<br />
<br />
==Password Requirements==<br />
We have the following policies in regards to our [[ActiveDirectory]] passwords:<br />
* Minimum Password Length : 8 Characters (more is allowed)<br />
* Minimum Character Classes : 3 Character Classes<br />
** English uppercase characters (A - Z)<br />
** English lowercase characters (a - z)<br />
** Base 10 digits (0 - 9)<br />
** Non-alphanumeric (For example: !, $, #, or %)<br />
** Unicode characters<br />
* Password cannot contain (or match a substring of 3+ sequential characters) of your username or any part of your first or last name.<br />
* Password was not previously used in last 5 passwords.<br />
* Password has not been [[CompromisedPasswordFiltering | compromised]] in a known data breach.<br />
<br />
It is your responsibility to secure your password. Please try to choose a strong password and use secure protocols.<br />
<br />
==Changing account password==<br />
===If you know your current password===<br />
* The [https://intranet.umiacs.umd.edu/password UMIACS Password Web Application] can be used to change the password for UMIACS and UMIACS Collaborator accounts.<br />
<br />
===If you do not know your current password===<br />
* [https://intranet.umiacs.umd.edu/password/forgot Reset your password], you will be required to have already registered a mobile phone number and alternate E-mail address in our [https://intranet.umiacs.umd.edu/directory/directory/info/ Directory Application].<br />
** UMIACS Collaborator Accounts can always be reset by the sponsor in our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/ Requests Application].<br />
* Stop by the UMIACS Help Desk in room 3142 A.V. Williams Building with a photo ID.<br />
* If you are unable to physically stop by the UMIACS Help Desk, you can have your Account sponsor (PI) stop by the UMIACS Help Desk to reset the password on your behalf. The account sponsor will then be responsible to conveying the password to you in a secure manner. (i.e. Telephone, where they could identify you by voice)<br />
<br />
==All Accounts Related Pages==<br />
{{Special:PrefixIndex/Accounts/}}</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GettingStarted&diff=8196GettingStarted2019-03-31T20:09:37Z<p>Ridge: /* Logging into your Account */</p>
<hr />
<div>== [[Accounts#UMIACS_Account | UMIACS Account]] Introduction ==<br />
<br />
UMIACS maintains several different systems and facilities. The basic [[UMIACS Account]] includes access to facilities including:<br />
<br />
* [[EMail | E-mail]] (Which is automatically [[BarracudaSpamFirewall | SPAM-Filtered]])<br />
* Several login machines ([[OpenLAB]])<br />
* Basic home directory space<br />
* [[OBJbox | Object Storage]] space<br />
* [[FileTransferProtocol | FTP]] space<br />
* The [[OpenLAB]] HPC cluster<br />
* [[VPN]], Printing ...<br />
<br />
The goal of the [[OpenLAB]] is to provide a basic computing environment for communications, authoring, file sharing, and general administrative computing. Use of facilities are subject to the [[OpenLAB]]'s Acceptable Use Policy.<br />
<br />
== Getting An Account ==<br />
<br />
If you do not already have an account, you will need to fill out the account request form located at https://intranet.umiacs.umd.edu/requests/accounts/new/ Please note that for the PI field you will be entering your PI/Professor/Sponsor's account name here at UMIACS. Also indicate any labs you are a member of in the notes field to speed up access to your lab's resources. <br />
<br />
Once the form is submitted, confirm you email address by checking your personal email, and wait for your PI to approve the account request. Accounts can take anywhere from a few hours to a day for installation, depending on how quickly your PI approves your account.<br />
<br />
== Logging into your Account ==<br />
<br />
Once your account has been installed, you can use [[SSH]] to login to openlab.umiacs.umd.edu. You can also login to other [[OpenLAB | OpenLab hosts]]<br />
<br />
== Account Maintenance ==<br />
<br />
There are a few web applications for managing your account:<br />
<br />
* <b>[https://intranet.umiacs.umd.edu/directory/info Directory Profile] </b> - Change your mail delivery/forward options, change your shells, and setting of office numbers.<br />
* <b>[https://intranet.umiacs.umd.edu/password UMIACS Change Password] </b> - Change your UMIACS password.<br />
<br />
== Where's my data? ==<br />
<br />
Your UNIX home directory is accessible from most machines from your [[NFShomes]]. You may have different home directories in different locations while using specific labs' machines. Your local data processing <b>is</b> different depending on the operating system of your desktop, please see:<br />
<br />
* [[LocalDataStorage#UNIX_Local_Storage | Unix/Linux Local Data Policies]]<br />
* [[LocalDataStorage#Windows_Local_Storage | Windows Local Data Policies]]<br />
<br />
Your can find out where your web space and FTP space are from [[NASUsers]]. and your lab may have data stored in a [[Subversion]] repository as well. If you need to access your data remotely, we recommend using [[SFTP]]. Many of our labs have specific network attached storage in addition to the default allocation a user is given.<br />
<br />
== Questions? ==<br />
<br />
Explore the rest of the wiki - if you have any problems or questions, you can contact the technical staff at<br />
<br />
[mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu] <br />
<br />
Or at the [[HelpDesk|UMIACS Helpdesk]] in A.V. Williams room 3142</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=7598GitLab2018-02-06T14:54:52Z<p>Ridge: </p>
<hr />
<div>GitLab is source code collaboration software based on [https://git-scm.com/ Git] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS Krb5 credentials in the "UMIACS Onsite/LDAP" tab:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
Note: There might be issues connecting to GitLab if you are using an older git client. Therefore, please make sure you update your git client. <br />
If you use TortoiseGit, please make sure it is updated to versions above TortoiseGit 2.1.x.x.<br />
<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help. <b>Note:</b> you will need to log in to view this page.<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/user/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/user/markdown.md<br />
<br />
==Repository URLs== <br />
Users can download and clone directories from the remote repository using git clone. There are two different URLs that can be used: HTTPS and SSH. <br />
You can view the URL underneath the Project title in the Project tab. Change the displayed URL by clicking on the URL type you want to see. <br />
===SSH===<br />
The SSH URL is more direct, though it is harder to set up. In order to do so, you will have to add an SSH key to your Gitlab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/ssh/README here]. Once you have the SSH key added, you can log in without having to enter any credentials from the machine and account for which you created the SSH key. <br />
===HTTPS===<br />
The HTTPS URL is easier to set up- you just clone directly from the repository using the HTTPS URL. However, you will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.<br />
<br />
==Make GitLab projects public==<br />
Making projects public grants access to everyone. Projects can only made public by the owner. To make your projects on GitLab public and make repo accessible to everyone, follow the steps below:<br />
1. Go to your projects page https://gitlab.umiacs.umd.edu/<username>/<yourProjectName>.<br />
For example: https://gitlab.umiacs.umd.edu/suzantrt/someNewAwesomeProject<br />
2. Click on '''Settings'''.<br />
<br />
3. Scroll down to '''Project Visibility'''. Choose '''Public''' from the drop-down menu.<br />
<br />
4. Scroll down and click on '''Save Changes'''<br />
<br />
5. Scroll down to '''Repository''' under '''Project Visibility''' and select '''Everyone with access''' from the drop-down menu.<br />
<br />
6. Click on '''Save Changes'''.<br />
<br />
<br />
Now your project has become public with its repository accessible anyone with access.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=EnvironmentalVariables&diff=7597EnvironmentalVariables2018-02-06T14:51:43Z<p>Ridge: </p>
<hr />
<div>In UNIX and Windows many of the commands run have variables that are parsed from a user's environment.<br />
<br />
==PATH(Unix)==<br />
<br />
The most common variable is the PATH variable, which will add additional paths to search for programs to be run from the command line. These can be set in many ways but we will cover the most popular: [[tcsh]] and [[bash]]. You can see your PATH variable by using the built-in echo command in the shell. When printing out environment variables you will need to prefix the variable with the $ sign.<br />
<br />
<pre><br />
$ echo $PATH<br />
/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin<br />
</pre><br />
<br />
In almost all cases you will want to append to either the beginning or end of your PATH variable and not replace it fully as this will most likely decrease the functionality of your shell. For example, if you wanted to add the path <tt>/opt/UMtorque/bin</tt> to the end of your PATH then you could do the following,<br />
<br />
;tcsh/csh<br />
:setenv PATH ${PATH}:/opt/UMtorque/bin<br />
;bash/sh<br />
:export PATH=${PATH}:/opt/UMtorque/bin<br />
<br />
These can be either typed into your shell directly or added to your shell's initialization files so every time you spawn a shell it will get this new PATH.<br />
<br />
==PATH(Windows)==<br />
To modify the Windows PATH Environmental Variable do the following: <br />
<br />
# Go to Control Panel and click on User Accounts. Then click on the User Accounts heading within User Accounts.<br />
# On the left pane, click Change my environment variables.<br />
# Under User Variables for <username> choose the PATH Variable.<br />
#* If there is none, click New and put PATH for the variable Name.<br />
# Click Edit and append the location you are trying to add. Different paths are separated by semicolons.<br />
<br />
To verify that the PATH variable has been modified properly do the following:<br />
<br />
# Open a new Command Prompt (Start -> Accessories -> Command Prompt).<br />
# Type in PATH<br />
<br />
The updated PATH should be printed.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=HPC&diff=7589HPC2018-02-06T14:40:29Z<p>Ridge: </p>
<hr />
<div>* [[SLURM | Slurm Schedular Documentation ]]</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MailmanFAQ&diff=7440MailmanFAQ2017-06-30T16:37:51Z<p>Ridge: </p>
<hr />
<div>===Is there an easy way to discard all messages waiting to be reviewed?===<br />
<br />
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. <br />
<br />
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.<br />
<br />
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."<br />
<br />
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).<br />
<br />
===How do I turn off HTML messages/attachments?===<br />
<br />
On the admin page, go to the Content Filtering section. <br />
<br />
Change "Should Mailman filter ..." to Yes. <br />
<br />
If you leave the rest at default values, including<br />
<br />
Yes for "Should Mailman convert text/html parts to plain text?"<br />
<br />
your list will only distribute plain text messages with no attachments.<br />
<br />
===How can I post from 2 or more addresses to a "members-only" list?===<br />
<br />
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.<br />
<br />
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.<br />
<br />
You can disable delivery to an address by going to the personal options page for that address and setting "Mail delivery" to "disabled". <br />
<br />
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.<br />
<br />
===How do I change a member's password or send them their password?===<br />
<br />
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 <br />
<br />
"Email my password to me"<br />
<br />
Note all the other options you can set for the user here.<br />
<br />
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<br />
<br />
http://lists.umiacs.umd.edu/mailman/options/LISTNAME/USERNAME%40DOMAINNAME<br />
<br />
e.g.:<br />
<br />
http://lists.umiacs.umd.edu/mailman/options/umiacs/johndoe%40umiacs.umd.edu<br />
<br />
===How can I restrict the list so only authorized persons can post?===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Set the member_moderation_action to Reject and add a nice rejection notice text to the following text box. <br />
<br />
Set the generic_nonmember_action to Reject or Discard.<br />
<br />
===How can someone subscribe without me doing anything?===<br />
<br />
They just need to go to <br />
<br />
http://lists.umiacs.umd.edu/mailman/listinfo/LISTNAME<br />
<br />
and fill in the form. They can also subscribe/unsubscribe by email by sending to<br />
<br />
LISTNAME-subscribe<br />
<br />
or to unsubscribe,<br />
<br />
LISTNAME-unsubscribe<br />
<br />
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.<br />
<br />
===How do I unsubscribe users without them getting an unsubscribe message?===<br />
<br />
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".<br />
<br />
===How do I edit a held message before approving it for the list?===<br />
<br />
* Use the "forward this message" feature in the admindb page to forward the message to yourself.<br />
<br />
* 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.<br />
<br />
* 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!<br />
<br />
* 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.<br />
<br />
===How do I add users to a mailing list?===<br />
<br />
* Login to the mailing list's adminstration page use your mailman admin password.<br />
<br />
http://lists.umiacs.umd.edu/mailman/admin/MAILINGLISTNAME<br />
<br />
* Click "Membership Management..." -> Choose "Mass Subscription".<br />
<br />
* In the "Mass Subscriptions" panel, enter one address per line of users you would like to subscribe.<br />
<br />
* Click "Submit Your Changes" button.<br />
<br />
* You can verify by choosing "Membership List" under "Membership Management..." and finding each user's address.<br />
<br />
* After completion, click "Logout".<br />
<br />
===Why don't some messages get to the list===<br />
<br />
* Some lists may have spam filters turned on by staff to eliminate problems<br />
<br />
* These filters are under "Privacy options..." -> "Spam filters"<br />
<br />
* The most common of these that will be applied is to restrict posts with [QUAR] in the subject</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=CoreServices&diff=7382CoreServices2017-04-19T20:48:06Z<p>Ridge: </p>
<hr />
<div>{| border="0" cellpadding="5" cellspacing="0"<br />
|-<br />
|[[Kerberos|Authentication (UMIACS KRB5/UNIX)]]<br />
|[[ActiveDirectory|Authentication (Active Directory/Windows)]]<br />
|[[OSSupport|Operating Systems Support]]<br />
|-<br />
|[[Email]]<br />
|[[MailingLists|Mailing Lists]]<br />
|[[Printing]]<br />
|-<br />
|[[Backups]]<br />
|[[NAS|Network Attached Storage]]<br />
|[[LocalDataStorage|Local Data Storage]]<br />
|-<br />
|[[Web|Web Services]]<br />
|[[FileTransferProtocol |File Transfer Protocol]]<br />
|[[RevisionControl|Revision Control (Git)]]<br />
|-<br />
|[[Programming|Programming Languages]]<br />
|[[HPC|High Performance Computing]]<br />
|[[VPN|Virtual Private Networking]]<br />
|}</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=LabFacilities&diff=7295LabFacilities2017-02-28T22:22:47Z<p>Ridge: </p>
<hr />
<div>* [[OpenLAB]]<br />
* [[CBCB | Compute Center for Bioinformatics and Computational Biology]] (CBCB) http://www.cbcb.umd.edu<br />
* Center for Digital International Government (CDIG) http://www.umiacs.umd.edu/research/CDIG<br />
* Center for Automation Research (CFAR) http://www.cfar.umd.edu<br />
* Center for Human Enhanced Secure Systems (CHESS) http://chess.umiacs.umd.edu/<br />
* Computational Linguistics and Information Processing (CLIP) https://wiki.umiacs.umd.edu/clip/index.php/Main_Page<br />
* Computer Vision Laboratory (CVL) http://www.cfar.umd.edu/cvl/<br />
* Distributed Systems Software Laboratory (DSSL) http://www.cs.umd.edu/projects/dssl<br />
* Fraunhofer Center at Maryland (FCMD) http://fc-md.umd.edu/<br />
* Graphics and Visual Informatics Laboratory (GVIL) http://www.cs.umd.edu/gvil/<br />
* Human Computer Interaction Laboratory (HCIL) http://www.cs.umd.edu/hcil<br />
* Language and Media Processing Laboratory (LAMP) http://lamp.cfar.umd.edu<br />
* Laboratory for Computational Cultural Dynamics (LCCD) http://www.umiacs.umd.edu/research/LCCD/<br />
* Laboratory for Parallel and Distributed Computing (LPDC) http://www.umiacs.umd.edu/research/LPDC<br />
* Maryland Information and Network Dynamics Lab (MIND) http://mindlab.umd.edu/<br />
* [https://wiki.umiacs.umd.edu/maxwell/index.php/Main_Page MaxWell - WiMaX Forum Applications Laboratory] (MaxWell) http://www.umiacs.umd.edu/research/maxwell/<br />
* Perceptual Interfaces and Reality Laboratory (PIRL) http://pirl.umd.edu/</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&diff=7252MonthlyMaintenanceWindow2017-01-17T16:40:30Z<p>Ridge: </p>
<hr />
<div>UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.<br />
<br />
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday]. This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month's window.<br />
<br />
The window is always going to be on a '''Thursday''' from '''8pm-12am'''. A tentative list of maintenance windows for 2016 is as follows with the upcoming window in bold.<br />
<br />
<br />
* '''January 19th 2017'''<br />
* February 23rd 2017<br />
* March 23rd 2017<br />
* April 21st 2017<br />
* May 18th 2017<br />
* June 22nd 2017<br />
* July 20th 2017<br />
* August 17th 2017<br />
* September 21st 2017<br />
* October 19th 2017<br />
* November: TBD, any emergency patching in November, will be scheduled based on need, otherwise November will be skipped this year. <br />
* December 21st 2017<br />
<br />
==Archives==<br />
* January 17th 2013<br />
* February 21st 2013<br />
* March 21st 2013<br />
* April 18th 2013<br />
* May 23rd 2013<br />
* June 20th 2013<br />
* July 18th 2013<br />
* August 22nd 2013<br />
* September 19th 2013<br />
* October 17th 2013<br />
* December 19th 2013<br />
* January 23rd 2014<br />
* February 20th 2014<br />
* March 20th 2014<br />
* April 17th 2014<br />
* May 22nd 2014<br />
* June 19th 2014<br />
* July 17th 2014<br />
* August 21st 2014<br />
* September 18th 2014<br />
* October 23rd 2014<br />
* November 20th 2014<br />
* December 18th 2014<br />
* January 22nd 2015<br />
* February 19th 2015<br />
* March 19th 2015<br />
* May 21st 2015<br />
* June 18th 2015<br />
* July 23rd 2015<br />
* August 20th 2015<br />
* September 17th 2015<br />
* October 22nd 2015<br />
* November 19th 2015<br />
* December 17th 2015<br />
* January 21st 2016<br />
* February 18th 2016<br />
* March 12th 2016 (Adjusted date for AVW power outage)<br />
* April 21st 2016<br />
* May 19th 2016<br />
* June 23rd 2016<br />
* July 21st 2016<br />
* August 18th 2016<br />
* September 22nd 2016<br />
* October 20th 2016<br />
* November 17th 2016<br />
* December 22nd 2016</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&diff=7251MonthlyMaintenanceWindow2017-01-15T14:14:24Z<p>Ridge: </p>
<hr />
<div>UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.<br />
<br />
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday]. This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month's window.<br />
<br />
The window is always going to be on a '''Thursday''' from '''8pm-12am'''. A tentative list of maintenance windows for 2016 is as follows with the upcoming window in bold.<br />
<br />
<br />
* '''January 19th 2017'''<br />
* February 23rd 2017<br />
* March 23rd 2017<br />
* April 21st 2017<br />
* May 18th 2017<br />
* June 22nd 2017<br />
* July 20th 2017<br />
* August 17th 2017<br />
* September 21st 2017<br />
* October 19th 2017<br />
* November 23rd 2017<br />
* December 21st 2017<br />
<br />
==Archives==<br />
* January 17th 2013<br />
* February 21st 2013<br />
* March 21st 2013<br />
* April 18th 2013<br />
* May 23rd 2013<br />
* June 20th 2013<br />
* July 18th 2013<br />
* August 22nd 2013<br />
* September 19th 2013<br />
* October 17th 2013<br />
* December 19th 2013<br />
* January 23rd 2014<br />
* February 20th 2014<br />
* March 20th 2014<br />
* April 17th 2014<br />
* May 22nd 2014<br />
* June 19th 2014<br />
* July 17th 2014<br />
* August 21st 2014<br />
* September 18th 2014<br />
* October 23rd 2014<br />
* November 20th 2014<br />
* December 18th 2014<br />
* January 22nd 2015<br />
* February 19th 2015<br />
* March 19th 2015<br />
* May 21st 2015<br />
* June 18th 2015<br />
* July 23rd 2015<br />
* August 20th 2015<br />
* September 17th 2015<br />
* October 22nd 2015<br />
* November 19th 2015<br />
* December 17th 2015<br />
* January 21st 2016<br />
* February 18th 2016<br />
* March 12th 2016 (Adjusted date for AVW power outage)<br />
* April 21st 2016<br />
* May 19th 2016<br />
* June 23rd 2016<br />
* July 21st 2016<br />
* August 18th 2016<br />
* September 22nd 2016<br />
* October 20th 2016<br />
* November 17th 2016<br />
* December 22nd 2016</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=6398Main Page2014-12-01T16:06:08Z<p>Ridge: </p>
<hr />
<div>==Announcements==<br />
<startFeed /><br />
<br />
Please see our [https://intranet.umiacs.umd.edu intranet] page for announcements.<br />
<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].<br />
<br />
If you would like to open a support ticket, please contact the UMIACS [[HelpDesk]].<br />
<br />
<br />
__NOTOC__</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&diff=5420MonthlyMaintenanceWindow2013-10-16T16:57:54Z<p>Ridge: </p>
<hr />
<div>UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.<br />
<br />
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday]. This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month's window.<br />
<br />
The window is always going to be on a '''Thursday''' from '''8pm-12am'''. A list of maintenance windows for 2013 and 2014 is as follows with the upcoming window in bold.<br />
<br />
* September 19th 2013<br />
* '''October 17th 2013'''<br />
* November 21st 2013<br />
* December 19th 2013<br />
* January 23rd 2014<br />
* February 20th 2014<br />
* March 20th 2014<br />
* April 17th 2014<br />
* May 22nd 2014<br />
* June 19th 2014<br />
* July 17h 2014<br />
* August 21st 2014<br />
* September 18th 2014<br />
* October 23rd 2014<br />
* November 20th 2014<br />
* December 18th 2014<br />
<br />
==Archives==<br />
* January 17th 2013<br />
* February 21st 2013<br />
* March 21st 2013<br />
* April 18th 2013<br />
* May 23rd 2013<br />
* June 20th 2013<br />
* July 18th 2013<br />
* August 22nd 2013</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=4886Main Page2013-01-08T19:24:17Z<p>Ridge: </p>
<hr />
<div>==Announcements==<br />
<startFeed /><br />
=UMIACS Monthly Maintenance Window Thursday January 17th 2013 8pm-12am=<br />
<br />
UMIACS staff will be taking ourregullarly scheduled maintenance<br />
window. This allows us to patch for security issues that have cropped<br />
up since our previous window. Attached is an iCal event that you may<br />
add to your calendar of choice for reminder of the maintenance window.<br />
<br />
All UNIX/Linux machines in the institute will be rebooted during the<br />
maintenance window (RHEL5, RHEL6, Ubuntu). Services such as IMAP, web<br />
servers, and the print service will all see small interruptions while<br />
machines are rebooting.<br />
<br />
All Microsoft Windows machines will reboot during the maintenance<br />
window. Windows services such as Exchange, printing, etc. will see<br />
small interruptions during the maintenance window.<br />
<br />
All Apple Mac OS X machines will reboot during the maintenance window.<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].<br />
<br />
__NOTOC__</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=4883Main Page2013-01-02T16:05:05Z<p>Ridge: </p>
<hr />
<div>==Announcements==<br />
<startFeed /><br />
<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].<br />
<br />
__NOTOC__</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=LocalDataTransfer&diff=4296LocalDataTransfer2012-05-28T20:29:11Z<p>Ridge: </p>
<hr />
<div>Depending on the amount of data you are trying to transfer there are different commands that you should use. The classic cp command has a number of edge cases in which it will not copy everything that is expected, so the '''only time''' that one should use the cp command is if the copy can be verified such as if you are moving a single file. The better choice for transfering data is by using tar/gtar. After transfering files or directories you can use rsync to check that everything moved correctly and it will update files that have been changed.<br />
<br />
==Transfer a single file==<br />
<br />
If you want to transfer a single file into another directory you can use the cp command. The cp command will take the file you need to transfer and make a copy of it in the directory you specify. If you do not specify a directory it will just make a copy of it in the current location.<br />
<br />
The format for the cp command is:<br />
<tt>cp file /target/</tt><br />
<br />
'''Example:''' To transfer the file foo.txt from your home directory into Documents<br />
<br />
<tt>cd</tt><br />
<br />
<tt>cp foo.txt ~/Documents</tt><br />
<br />
The end result will leave the original file in the home directory and create a copy of it in Documents.<br />
<br />
'''Important:''' The cp command should only be used for small file transfers. If you try to transfer a large amount it is possible that cp will not copy all the files over properly.<br />
<br />
<br />
==Transfer a directory or large amounts of data to another location==<br />
<br />
If you want to transfer a whole directory or a large amount of data to another location you can use the gtar command. This command will archive the all files (including those in subdirectories) within the current directory and re-create the files in the directory that you specify.<br />
<br />
The format for the gtar command is:<br />
<tt>gtar -cpf - . | gtar -C /dir -xpvf -</tt><br />
<br />
'''Example:''' To transfer all files from your documents to a folder in your home directory called foo:<br />
<br />
<tt>cd</tt><br />
<br />
<tt>gtar -cpf - . | gtar -C ~/foo -xpvf -</tt><br />
<br />
When you use this command it will display a list of the files it has transferred.<br />
<br />
This command will leave Documents the same, but create a full copy of all files and folders from Documents in foo.<br />
<br />
'''Note:''' This command will preserve permissions, attributes, and meta-data of all files transferred.<br />
<br />
===Transfer between two different hosts=== <br />
<br />
Include the command -ssh USERNAME@FULLYQUALIFIEDHOSTNAME- before the gtar command.<br />
<br />
If the other host is the one with the data to transfer you will need to include the command before the first gtar.<br />
<br />
If the other host is the one receiving the data, you will need to include the command after the pipe "|" and before the second gtar.<br />
<br />
'''Example:''' To transfer files from the directory /tmp/ on example1.umiacs.umd.edu to the folder /foo/ on your current host:<br />
<br />
<tt>ssh USERNAME@example1.umiacs.umd.edu gtar -cpf - /tmp | gtar -C /foo -xpvf -</tt><br />
<br />
If your data transfer is interrupted, you can use the rsync command listed below to copy the rest of the files without creating doubles of files that have already been transferred.<br />
<br />
Rsync can also be used for the initial transfer of data if you expect the transfer to be interrupted. Elsewise, this method should not be used as it takes more time and memory.<br />
<br />
To run rsync to copy files, the format for the command is the same as written below under "Verifying transfer."<br />
<br />
==Verifying transfer==<br />
<br />
To verify that your transfer copied everything you can use the rsync command, which will compare the two directories contents and will update the files in which it sees differences.<br />
<br />
The format for the rsync command is:<br />
<br />
<tt>rsync -aH /source/ /target</tt><br />
<br />
'''Example:''' To ensure that the files are the same in Documents and foo from the previous example:<br />
<br />
<tt>rsync -aH ~/Documents/ ~/foo</tt><br />
<br />
This command will compare the files and directories within Documents to the files and directories within foo. If there are files within Documents and its subdirectories that do not appear in foo, this command will copy the missing files from Documents to foo.<br />
<br />
'''Important:''' Make sure to include the slash after the name of the source directory, if you do not include it it will copy the directory folder over as well.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=LocalDataTransfer&diff=4295LocalDataTransfer2012-05-28T20:27:58Z<p>Ridge: </p>
<hr />
<div>Depending on the amount of data you are trying to transfer there are different commands that you should use. The classic cp command has a number of edge cases in which it will not copy everything that is expected, so the '''only time''' that one should use the cp command is if the copy can be verified such as if you are moving a single file. The better choice for transfering data is by using tar/gtar. After transfering files or directories you can use rsync to check that everything moved correctly and it will update files that have been changed.<br />
<br />
==Transfer a single file==<br />
<br />
If you want to transfer a single file into another directory you can use the cp command. The cp command will take the file you need to transfer and make a copy of it in the directory you specify. If you do not specify a directory it will just make a copy of it in the current location.<br />
<br />
The format for the cp command is:<br />
<tt>cp file /target/</tt><br />
<br />
'''Example:''' To transfer the file foo.txt from your home directory into Documents<br />
<br />
<tt>cd</tt><br />
<br />
<tt>cp foo.txt /nfshomes/YOURUSERNAME/Documents</tt><br />
<br />
The end result will leave the original file in the home directory and create a copy of it in Documents.<br />
<br />
'''Important:''' The cp command should only be used for small file transfers. If you try to transfer a large amount it is possible that cp will not copy all the files over properly.<br />
<br />
<br />
==Transfer a directory or large amounts of data to another location==<br />
<br />
If you want to transfer a whole directory or a large amount of data to another location you can use the gtar command. This command will archive the all files (including those in subdirectories) within the current directory and re-create the files in the directory that you specify.<br />
<br />
The format for the gtar command is:<br />
<tt>gtar -cpf - . | gtar -C /dir -xpvf -</tt><br />
<br />
'''Example:''' To transfer all files from your documents to a folder in your home directory called foo:<br />
<br />
<tt>cd</tt><br />
<br />
<tt>gtar -cpf - . | gtar -C /nfshomes/YOURUSERNAME/foo -xpvf -</tt><br />
<br />
When you use this command it will display a list of the files it has transferred.<br />
<br />
This command will leave Documents the same, but create a full copy of all files and folders from Documents in foo.<br />
<br />
'''Note:''' This command will preserve permissions, attributes, and meta-data of all files transferred.<br />
<br />
===Transfer between two different hosts=== <br />
<br />
Include the command -ssh USERNAME@FULLYQUALIFIEDHOSTNAME- before the gtar command.<br />
<br />
If the other host is the one with the data to transfer you will need to include the command before the first gtar.<br />
<br />
If the other host is the one receiving the data, you will need to include the command after the pipe "|" and before the second gtar.<br />
<br />
'''Example:''' To transfer files from the directory /tmp/ on example1.umiacs.umd.edu to the folder /foo/ on your current host:<br />
<br />
<tt>ssh USERNAME@example1.umiacs.umd.edu gtar -cpf - /tmp | gtar -C /foo -xpvf -</tt><br />
<br />
If your data transfer is interrupted, you can use the rsync command listed below to copy the rest of the files without creating doubles of files that have already been transferred.<br />
<br />
Rsync can also be used for the initial transfer of data if you expect the transfer to be interrupted. Elsewise, this method should not be used as it takes more time and memory.<br />
<br />
To run rsync to copy files, the format for the command is the same as written below under "Verifying transfer."<br />
<br />
==Verifying transfer==<br />
<br />
To verify that your transfer copied everything you can use the rsync command, which will compare the two directories contents and will update the files in which it sees differences.<br />
<br />
The format for the rsync command is:<br />
<br />
<tt>rsync -aH /source/ /target</tt><br />
<br />
'''Example:''' To ensure that the files are the same in Documents and foo from the previous example:<br />
<br />
<tt>rsync -aH /nfshomes/YOURUSERNAME/Documents/ /nfshomes/YOURUSERNAME/foo</tt><br />
<br />
This command will compare the files and directories within Documents to the files and directories within foo. If there are files within Documents and its subdirectories that do not appear in foo, this command will copy the missing files from Documents to foo.<br />
<br />
'''Important:''' Make sure to include the slash after the name of the source directory, if you do not include it it will copy the directory folder over as well.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Subversion&diff=4105Subversion2011-09-15T16:32:34Z<p>Ridge: </p>
<hr />
<div>UMIACS provides a centrally managed [[Subversion]] service.<br />
<br />
To have a [[Subversion]] repository created you need to just email [mailto:staff@umiacs.umd.edu staff] and provide the name of your repository and how much initial space you think you will need.<br />
<br />
We will give you a [[URL]] back with the server https://subversion.umiacs.umd.edu in it.<br />
<br />
By default we will configure all repositories to be private and require authentication for both reading and writing to the [[Subversion]] repository. Authentication is done against our [[LDAP]] and if requested we can enable a UMIACS user to manage the [[ApplicationResource|AR]] with our [[ApplicationResourceUtil]] found at https://intranet.umiacs.umd.edu/arutil.<br />
<br />
=Getting Started with Subversion=<br />
<br />
You will first need to check out your repository,<br />
<br />
svn co https://subversion.umiacs.umd.edu/my_url<br />
<br />
This will create a directory in your current working directory with the name of the last part of the URL you just checked out.<br />
<br />
cd my_url<br />
<br />
You can now add files by the '''svn import''' command, '''svn add''' can be used to add file that you have created but is not under revision control yet.<br />
<br />
For more information please see the defacto book on [[Subversion]] in [http://svnbook.red-bean.com/en/1.4/svn-book.html HTML] or [http://svnbook.red-bean.com/en/1.4/svn-book.pdf PDF]<br />
<br />
=Clients=<br />
<br />
Most Linux distributions include subversion clients in the distribution including all our [[OSSupport|Red Hat Enterprise Linux]] clients.<br />
<br />
==Collab.net Subversion Packages==<br />
<br />
These are well packaged subversion command line packages. You can find ones for Windows, Mac OS X and Solaris. Please see the community downloads for Mac OS X.<br />
<br />
http://www.open.collab.net/downloads<br />
<br />
==Graphical Clients==<br />
<br />
===OS Integration===<br />
<br />
* Windows - http://tortoisesvn.tigris.org<br />
* Mac OS X - http://scplugin.tigris.org<br />
<br />
===Other Clients===<br />
<br />
http://subversion.tigris.org/links.html#clients</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Email&diff=4066Email2011-07-25T15:25:26Z<p>Ridge: </p>
<hr />
<div>__NOTOC__<br />
===Introduction===<br />
<br />
Depending on the environment you'll be working in, you have two primary choices for mail. You can decide on our PC based solution [[#Microsoft Exchange Email]] or a [[UNIXEmail|IMAP Email]] solution. Both provide scanning for Virus and Spam through our [[BarracudaSpamFirewall|Barracuda Spam Firewall]]<br />
<br />
Alternatively if you already have a Email provider you like we offer the ability to forward your Email.<br />
<br />
You can update your Email preference through our [https://intranet.umiacs.umd.edu/chinfo Directory Profile] Tool.<br />
<br />
===Microsoft Exchange Email===<br />
If you are accustomed with Microsoft Outlook and/or need a shared calendar then we offer the UMIACS Exchange service. If you work primarily on a PC, collaborate with primarily PC-based users, expect to email MIME attachments or just feel most comfortable with a PC based mail solution, the exchange mailserver is likely the best solution for you. Among other things, it also supports IMAP, vacation (auto-response) and virus filtering capabilities.<br />
<br />
[[SettingUpOutlook2007/2010withExchange|Setting Up Outlook 2007/2010 with Exchange]]<br />
<br />
[[SettingUpOutlook2003withExchange|Setting Up Outlook 2003 with Exchange]]<br />
<br />
[[SettingupiPhoneAccesstoExchange|Setting Up iPhone Access with Exchange]]<br />
<br />
[[AccessingExchangeviaThunderbird|Setting Up Thunderbird with Exchange]]<br />
<br />
[[WorkingWithOutlook|Working with Outlook]]<br />
<br />
The link for the Exchange web interface is https://exchange.umiacs.umd.edu/owa. It is also on the front page of our intranet site (https://intranet.umiacs.umd.edu). Please note that the web interface works best in IE.<br />
<br />
===[[UNIXEmail|IMAP Email]]===<br />
Our IMAP service is available as a simple multi-platform way of reading your mail. It provides powerful server-side mail filtering. You can configure you own client or use our [[Webmail]] server to read your email.<br />
<br />
===Support Matrix===<br />
<br />
{|style="color:green;background-color:#ffffcc;" cellpadding="10" cellspacing="0" border="1"<br />
|-style="color:black;"<br />
|<br />
|Pine<br />
|Mutt<br />
|Thunderbird<br />
|Mail.app<br />
|Outlook/Exchange<br />
|-<br />
|Windows 7<br />
|Yes(1)<br />
|<br />
|Yes<br />
|<br />
|Yes<br />
|-<br />
|Windows XP<br />
|Yes(1)<br />
|<br />
|Yes<br />
|<br />
|Yes<br />
|-<br />
|RHEL 3/4/5<br />
|Yes<br />
|Yes<br />
|Yes<br />
|<br />
|Yes(2)<br />
|-<br />
|Ubuntu<br />
|Yes<br />
|Yes<br />
|Yes<br />
|<br />
|Yes(2)<br />
|-<br />
|Mac OS X<br />
|Yes<br />
|Yes<br />
|Yes<br />
|Yes<br />
|Yes(3)<br />
|}<br />
<br />
# - We support pine on Windows through [http://www.washington.edu/pine/getpine/pcpine.html PC Pine]<br />
# - Microsoft Exchange support is only available through the Outlook Web Access which is severely limited on non-IE browsers.<br />
# - Microsoft Exchange support for Mail/Contacts/Calendar requirers Mac OS X 10.6 or later.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&diff=3984WebSpace2011-05-25T23:24:41Z<p>Ridge: </p>
<hr />
<div>UMIACS provides web space hosting for research/lab pages and user pages.<br />
<br />
==Main Website and Lab Pages==<br />
<br />
<pre>http://www.umiacs.umd.edu</pre><br />
<br />
Users can access the main website and lab sites for editing in two ways:<br />
* From <b>Unix</b> as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])<br />
* From <b>Windows</b> as \\umiacs-webftp.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]<br />
<br />
==Personal Web Space==<br />
<br />
<pre>http://www.umiacs.umd.edu/~username</pre><br />
<br />
Users can access their website for editing two ways:<br />
<br />
* From <b>Unix</b> as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])<br />
* From <b>Windows</b> as \\umiacs-webftp.umiacs.umd.edu\www-users - and remotely accessed by the same file share over the [[VPN]]<br />
<br />
In general, large datasets related to a Labs research should go into the specific lab's web tree, not the individual users. Remember that users' webpage is not permanently maintained once the user leaves UMIACS.<br />
<br />
==Adding A Password Protected Folder To Your Web Space==<br />
<br />
1) Create the directory you want to password protect or '''cd''' into the directory you want to password protect<br />
<br />
2) Create a file called ''.htaccess'' ('''vi .htaccess''') in the directory you wish to password protect.<br />
<br />
3) In the file you just created type the following lines<br />
<br>'''AuthUserFile ''/your/directory/here/''.htpasswd'''<br />
<br>'''AuthName "Secure Document"'''<br />
<br>'''AuthType Basic'''<br />
<br>'''require user username'''<br />
<br />
For example, if you were going to protect the '''/fs/users/www/username/private''' directory and you want the required name to be '''class239''', then your file would look like this:<br />
<br>'''AuthUserFile /fs/users/www/username/private/.htpasswd'''<br />
<br>'''AuthName "Secure Document"'''<br />
<br>'''AuthType Basic'''<br />
<br>'''require user class239'''<br />
<br />
4) Create a file called ''.htpasswd'' in the same directory as ''.htaccess''. You create this file by typing in '''htpasswd -c .htpasswd ''username''''' in the directory area to be protected.<br />
<br />
In the example above, the username is '''class239''' so you would type '''htpasswd -c .htpasswd class239''' <br />
<br />
You will be prompted to enter the password you want. The ''.htpasswd'' file will be created in the current directory and will contain an encrypted version of the password.<br />
<br />
To later change the username, edit the ''.htaccess'' file and change the username. If you want to later change the password, just retype the above line in step 3 and enter the new password at the prompt.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MacOSPrinting&diff=3935MacOSPrinting2011-04-07T23:24:01Z<p>Ridge: /* Advanced */</p>
<hr />
<div>__NOTOC__<br />
We support printing from user managed Mac OS X 10.5/10.6 machines. Please note that you have to be on a UMIACS network directly or connected to the [[VPN]].<br />
<br />
[[Image:osx-print00.png|right|100px]]<br />
=System Preferences=<br />
To start you need to open up you will need to open your System Preferences from your Dock or the Applications folder. Once you have opened it you will need to click '''Print & Fax''' from the Hardware pane.<br />
<br />
[[Image:osx-print01.png|right|100px]]<br />
=Print & Fax=<br />
When the '''Print & Fax''' window appears you will need to create a new local printer by clicking the '''+''' icon in the lower left corner of the first pane in the window.<br />
<br />
=Add Printer=<br />
This will bring up a Add Printer dialog. Please ensure that the that you have selected IP.<br />
<br />
* Set Protocol to '''Internet Printing Protocol - IPP'''<br />
* Set Address to '''print.umiacs.umd.edu'''<br />
* Set the queue to =printers/queue= in this example for cps3142 it would be '''printers/cps3142'''. You have to make sure the queue is prefixed by '''printers/'''<br />
* Set Name to the queue you are trying to use<br />
* It will always select '''Generic Postscript Printer'''. If you need to access the more advanced features of a queue/printer you will need take extra steps, please see the Advanced section at the bottom of this page.<br />
* Select Add<br />
<br />
[[Image:osx-print02.png]]<br />
<br />
You should now be able to print to this printer/queue from any Mac OS X print menu.<br />
<br />
=Advanced=<br />
<br />
You will need to first download a copy of the Postcript Printer Definition file from the print server. This can be fetched with any normal browser by going to<br />
<br />
http://print.umiacs.umd.edu/printers/queue.ppd<br />
<br />
Where '''queue''' is the queue/printer you want to get extra features from. For example here is a few links to our major public printers.<br />
<br />
* http://print.umiacs.umd.edu/printers/cps3142.ppd - AV Williams Building room 3142<br />
* http://print.umiacs.umd.edu/printers/ps3142.ppd - AV Williams Building room 3142<br />
* http://print.umiacs.umd.edu/printers/cps4430a.ppd - AV Williams Building room 4430<br />
* http://print.umiacs.umd.edu/printers/cps296-3120Hb.ppd - Biomolecular Sciences Building room 3120H<br />
<br />
Please save this file to your hard disk as you will need use the file chooser to select it in the next step. If you don't see the queue you want please just reconstruct the URL above and substitute in your queue name.<br />
<br />
Next go back to the '''Print & Fax''' dialog and click the '''Options & Supplies...''' button for the queue you want to modify.<br />
<br />
[[Image:osx-print03.png]]<br />
<br />
You will need to navigate to the Driver tab and select the option '''Other...''' from the Print Using option. This will bring up a file chooser that you will need to select the file you downloaded from.<br />
<br />
[[Image:osx-printingadv00.png]]<br />
<br />
This will fill in all the default options and you can then click Okay. If you have questions or need help please contact [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MacOSPrinting&diff=3934MacOSPrinting2011-04-07T23:20:49Z<p>Ridge: /* Advanced */</p>
<hr />
<div>__NOTOC__<br />
We support printing from user managed Mac OS X 10.5/10.6 machines. Please note that you have to be on a UMIACS network directly or connected to the [[VPN]].<br />
<br />
[[Image:osx-print00.png|right|100px]]<br />
=System Preferences=<br />
To start you need to open up you will need to open your System Preferences from your Dock or the Applications folder. Once you have opened it you will need to click '''Print & Fax''' from the Hardware pane.<br />
<br />
[[Image:osx-print01.png|right|100px]]<br />
=Print & Fax=<br />
When the '''Print & Fax''' window appears you will need to create a new local printer by clicking the '''+''' icon in the lower left corner of the first pane in the window.<br />
<br />
=Add Printer=<br />
This will bring up a Add Printer dialog. Please ensure that the that you have selected IP.<br />
<br />
* Set Protocol to '''Internet Printing Protocol - IPP'''<br />
* Set Address to '''print.umiacs.umd.edu'''<br />
* Set the queue to =printers/queue= in this example for cps3142 it would be '''printers/cps3142'''. You have to make sure the queue is prefixed by '''printers/'''<br />
* Set Name to the queue you are trying to use<br />
* It will always select '''Generic Postscript Printer'''. If you need to access the more advanced features of a queue/printer you will need take extra steps, please see the Advanced section at the bottom of this page.<br />
* Select Add<br />
<br />
[[Image:osx-print02.png]]<br />
<br />
You should now be able to print to this printer/queue from any Mac OS X print menu.<br />
<br />
=Advanced=<br />
<br />
You will need to first download a copy of the Postcript Printer Definition file from the print server. This can be fetched with any normal browser by going to<br />
<br />
http://print.umiacs.umd.edu/printers/queue.ppd<br />
<br />
Where '''queue''' is the queue/printer you want to get extra features from. For example here is a few links to our major public printers.<br />
<br />
* http://print.umiacs.umd.edu/printers/cps3142.ppd - AV Williams Building room 3142<br />
* http://print.umiacs.umd.edu/printers/ps3142.ppd - AV Williams Building room 3142<br />
* http://print.umiacs.umd.edu/printers/cps4430a.ppd - AV Williams Building room 4430<br />
* http://print.umiacs.umd.edu/printers/cps296-3120Hb.ppd - BioSciences Building room 3120H<br />
<br />
Please save this file to your hard disk as you will need use the file chooser to select it in the next step. If you don't see the queue you want please just reconstruct the URL above and substitute in your queue name.<br />
<br />
Next go back to the '''Print & Fax''' dialog and click the '''Options & Supplies...''' button for the queue you want to modify.<br />
<br />
[[Image:osx-print03.png]]<br />
<br />
You will need to navigate to the Driver tab and select the option '''Other...''' from the Print Using option. This will bring up a file chooser that you will need to select the file you downloaded from.<br />
<br />
[[Image:osx-printingadv00.png]]<br />
<br />
This will fill in all the default options and you can then click Okay. If you have questions or need help please contact [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3861Main Page2011-02-23T20:49:38Z<p>Ridge: /* Anouncements */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<br />
===Exchange Outage: Feb 23. 2011===<br />
We are currently experiencing an outage of our Exchange Email and Calendaring <br />
service. This is not a planned outage and the technical staff is working to resolve<br />
the issue. The service will be brought back on line as soon as possible, but do not<br />
currently have a good estimate as to when that will be. <br />
<br />
===UMIACS data center outage Feb 27 2011 8am-5pm===<br />
When: Sunday February 27, 2011 8am-5pm<br />
<br />
UMIACS needs to take the final downtime in the project to upgrade the<br />
south side AV Williams Bldg UPS. This will require our main data center<br />
to be shut down for approximately 8 hours. During this time no UMIACS<br />
services will be available including email (exchange or imap), web<br />
services, networked file systems and remote access. Additionally<br />
workstations throughout AVW will be unavailable since they require file<br />
systems and services that are hosted in our data center.<br />
<br />
We will support email queuing during the outage so<br />
we will not bounce or warn any users of delivery. However, this will not <br />
provide any support to read or send email. <br />
<br />
If you have any questions or comments please contact staff@umiacs.umd.edu.<br />
<br />
===New UNIX Print System===<br />
We are pleased to announce the immediately available [[CUPS]] print system for our UNIX (rhel/ubuntu) users. Please contact staff@umiacs.umd.edu with any issues.<br />
<br />
<startFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3860Main Page2011-02-23T15:52:52Z<p>Ridge: /* Anouncements */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<br />
===UMIACS data center outage Feb 27 2011 8am-5pm===<br />
When: Sunday February 27, 2011 8am-5pm<br />
<br />
UMIACS needs to take the final downtime in the project to upgrade the<br />
south side AV Williams Bldg UPS. This will require our main data center<br />
to be shut down for approximately 8 hours. During this time no UMIACS<br />
services will be available including email (exchange or imap), web<br />
services, networked file systems and remote access. Additionally<br />
workstations throughout AVW will be unavailable since they require file<br />
systems and services that are hosted in our data center.<br />
<br />
We will support email queuing during the outage so<br />
we will not bounce or warn any users of delivery. However, this will not <br />
provide any support to read or send email. <br />
<br />
If you have any questions or comments please contact staff@umiacs.umd.edu.<br />
<br />
===New UNIX Print System===<br />
We are pleased to announce the immediately available [[CUPS]] print system for our UNIX (rhel/ubuntu) users. Please contact staff@umiacs.umd.edu with any issues.<br />
<br />
<startFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3764Main Page2010-11-24T17:29:55Z<p>Ridge: /* Help Desk closing early Wednesday, November 24th, at 3:30 PM */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
===Help Desk Thanksgiving Holiday Hours===<br />
The UMIACS Help Desk in AVW3142 will be closing our doors early, (3:30pm on Wednesday) to prepare for the upcoming holiday weekend. After this time the best way to get help will be to send mail to staff@umiacs.umd.edu. Additionally the Help Desk will be closed and there will be no staff on site Thursday and Friday, as a part of the University being closed for the Thanksgiving Holiday. We will re-open as usual Monday, November 29th at 9AM.<br />
<br />
===AV Williams Building x300 and x400 wings, November 20th 10pm - Nov 21st 6pm===<br />
Facilities Management plans to complete replacement of the AV Williams North UPS on Sunday Nov 21. This work will require a power outage of the North side of the AV Williams Building, which includes offices in the x300 and x400 wings and the secondary data centers in 4464 and 1446. Staff will shut the Chimera Cluster, Crocco Cluster, RDEC Cluster, and Lattice Grid down before the outage starting at 10pm on 11/20 and will be on-site to bring them back online afterwards. We will make every effort to bring them back online by the start of the business day on Monday November 22nd.<br />
<br />
The main UMIACS data center will not lose power and all of the Institute's core services will be available during the work.<br />
<br />
Please send mail to staff@umiacs.umd.edu with any questions or concerns.<br />
<br />
===Comcast DNS Issues===<br />
We are currently experiencing issues with Comcast home internet in PG county not correctly handling DNS resolution for UMIACS hostnames, that can seem to be affecting connectivity to UMIACS. <br />
<br />
If you are having problems getting to UMIACS hosts you can use our name servers to resolve those specific host names then connect using the IP addresses you lookup. Our name servers are 128.8.120.19, 128.8.120.50, and 128.8.132.75 to use this information to get the ip address of the host somehost.umiacs.umd.edu you would use the command "nslookup somehost.umiacs.umd.edu 128.8.120.19", from a linux, windows or mac command prompt. <br />
<br />
Unfortunately the problem seems to lie in an interaction of Comcast's name servers with those run by OIT, but we are looking into ways we can interact with those parties to get this issue resolved. <br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3743Main Page2010-11-16T02:32:05Z<p>Ridge: /* Anouncements */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
===AV Williams Building x300 and x400 wings, November 20th 10pm - Nov 21st 6pm===<br />
Facilities Management plans to complete replacement of the AV Williams North UPS on Sunday Nov 21. This work will require a power outage of the North side of the AV Williams Building, which includes offices in the x300 and x400 wings and the secondary data centers in 4464 and 1446. Staff will shut the Chimera Cluster, Crocco Cluster, RDEC Cluster, and Lattice Grid down before the outage starting at 10pm on 11/20 and will be on-site to bring them back online afterwards. We will make every effort to bring them back online by the start of the business day on Monday November 22nd.<br />
<br />
The main UMIACS data center will not lose power and all of the Institute's core services will be available during the work.<br />
<br />
Please send mail to staff@umiacs.umd.edu with any questions or concerns.<br />
<br />
===Comcast DNS Issues===<br />
We are currently experiencing issues with Comcast home internet in PG county not correctly handling DNS resolution for UMIACS hostnames, that can seem to be affecting connectivity to UMIACS. <br />
<br />
If you are having problems getting to UMIACS hosts you can use our name servers to resolve those specific host names then connect using the IP addresses you lookup. Our name servers are 128.8.120.19, 128.8.120.50, and 128.8.132.75 to use this information to get the ip address of the host somehost.umiacs.umd.edu you would use the command "nslookup somehost.umiacs.umd.edu 128.8.120.19", from a linux, windows or mac command prompt. <br />
<br />
Unfortunately the problem seems to lie in an interaction of Comcast's name servers with those run by OIT, but we are looking into ways we can interact with those parties to get this issue resolved. <br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3638Main Page2010-09-14T22:19:21Z<p>Ridge: /* UMIACS Web/FTP Filesystem migration */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
<br />
===UMIACS Web/FTP Filesystem migration===<br />
<br />
'''When: Tuesday 9/21 10pm - Wednesday 9/22 2am'''<br />
<br />
We are going to be migrating the main UMIACS web and ftp file system to a new backend storage system which will require both the file systems to be read-only and then offline for a very short period. There will only be a 15 minute window at the tail end of the maintenance window where we will not be serving web and ftp content. No other services within UMIACS will be affected. <br />
<br />
Please send any questions or comments to [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].<br />
<br />
===Comcast DNS Issues===<br />
We are currently experiencing issues with Comcast home internet in PG county not correctly handling DNS resolution for UMIACS hostnames, that can seem to be affecting connectivity to UMIACS. <br />
<br />
If you are having problems getting to UMIACS hosts you can use our name servers to resolve those specific host names then connect using the IP addresses you lookup. Our name servers are 128.8.120.19, 128.8.120.50, and 128.8.132.75 to use this information to get the ip address of the host somehost.umiacs.umd.edu you would use the command "nslookup somehost.umiacs.umd.edu 128.8.120.19", from a linux, windows or mac command prompt. <br />
<br />
Unfortunately the problem seems to lie in an interaction of Comcast's name servers with those run by OIT, but we are looking into ways we can interact with those parties to get this issue resolved. <br />
<br />
===UMIACS Staff Jira===<br />
We have upgraded our request tracker to [[Jira]]. Please email [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu] if you have questions or comments.<br />
<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3451Main Page2010-07-21T23:21:42Z<p>Ridge: </p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
===Comcast DNS Issues===<br />
We are currently experiencing issues with Comcast home internet in PG county not correctly handling DNS resolution for UMIACS hostnames, that can seem to be affecting connectivity to UMIACS. <br />
<br />
If you are having problems getting to UMIACS hosts you can use our name servers to resolve those specific host names then connect using the IP addresses you lookup. Our name servers are 128.8.120.19, 128.8.120.50, and 128.8.132.75 to use this information to get the ip address of the host somehost.umiacs.umd.edu you would use the command "nslookup somehost.umiacs.umd.edu 128.8.120.19", from a linux, windows or mac command prompt. <br />
<br />
Unfortunately the problem seems to lie in an interaction of Comcast's name servers with those run by OIT, but we are looking into ways we can interact with those parties to get this issue resolved. <br />
<br />
===UMIACS Staff Jira===<br />
We have upgraded our request tracker to [[Jira]]. Please email [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu] if you have questions or comments.<br />
<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3351Main Page2010-07-06T21:57:12Z<p>Ridge: </p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
===UMIACS Staff Jira===<br />
We have upgraded our request tracker to [[Jira]]. Please email [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu] if you have questions or comments.<br />
<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3350Main Page2010-07-02T16:39:30Z<p>Ridge: </p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
===UMIACS Email IMAP Downtime July 5th 2010 10pm-2am===<br />
We are going to be upgrading UMIACS Email IMAP service that is served by imap.umiacs.umd.edu. The current chassis is off support and we are nearing its storage capacity. We will be migrating to a new chassis that has a significant additional amount of storage. Please note that while this upgrade is underway you will *NOT* be able to access your IMAP mailboxes in UMIACS. Mail will be delayed and queued up durning the outage but will be delivered once service has been restored.<br />
<br />
This will have no effect on our Exchange users or our users who forward their mail off site.<br />
<br />
Please contact [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu] if you have any issues or concerns.<br />
<br />
===UMIACS Help Desk Holiday Hours===<br />
The Help Desk will be closed on July 5th, due to the University's observance of the July 4th Holiday<br />
<br />
Additionally, the Help Desk will be closing at 3pm on Friday, July 2, as the staff prepares for the long weekend. <br />
<br />
===UMIACS Staff Jira===<br />
We have upgraded our request tracker to [[Jira]]. Please email [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu] if you have questions or comments.<br />
<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3282Main Page2010-05-19T18:02:20Z<p>Ridge: /* NOD.umiacs.umd.edu downtime, May 7, 10am */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
<br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=3099Main Page2010-02-26T18:46:29Z<p>Ridge: </p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
===UMIACS NFS Problems===<br />
This afternoon we experienced a problem with directory service configuration for most of our NFS service, that created problems accessing NFS services. After resolving the core issue, some of our NFS servers continued to have difficulties which now seem to have been resolved.<br />
<br />
If you continue to have any difficulties, please contact staff, by sending email to staff@umiacs.umd.edu, or calling 301-405-1775<br />
<br />
<br />
===ONStor Upgrade Mon March 1st 2010 8pm-12am=== <br />
Staff will be upgrading the last of our 2 ONStor clusters which provide NFS and CIFS file service to many of our labs and centers. Because they are clustered and highly available we expect to be able to upgrade the cluster without any downtime. There may be however some short hiccups when we fail servers over they should just show up as delays in file service. The following are the virtual servers that will be affected by this upgrade:<br />
<br />
* umiacsfs02 (nfshomes)<br />
* umiacsfs01 (legacyfs file systems)<br />
* umiacsfs00 (/usr/local and /opt file systems)<br />
* umiacs-webftp (ftp and web trees)<br />
* clampfs00<br />
* lccdfs00<br />
<br />
If you have any questions please email [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]<br />
<br />
<endFeed /><br />
<br />
'''Please see our [[HelpDesk]] for additional support.'''<br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=2894Main Page2009-12-22T18:35:38Z<p>Ridge: /* Anouncements */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
===CLIP File System Downtime, Dec 22===<br />
Tuesday<br><br />
December 22<br><br />
10am<br><br />
<br />
duc<br><br />
hadoop<br><br />
gale<br><br />
parse-lm<br><br />
ncbi2<br><br />
ace<br><br />
sdr<br><br />
qa2<br><br />
<br />
===Helpdesk Hours for Dec 21 (mon) Dec 22 (tue)===<br />
The UMIACS Helpdesk will operate on shortened help desk hours on Dec 21 and 22. We will only be open from 1:30pm - 3:30pm but we will be fielding email requests (staff@umiacs.umd.edu). <br><br />
<br />
===Helpdesk Closed from December 23 till January 4th===<br />
The UMIACS Helpdesk and UMD campus will be closed from December 23rd till January 4th at 9am.<br />
<br />
===Outage of Biomolecular Sciences Building Emergency Electrical Systems===<br />
FM has posted an outage of the emergency electrical systems for the Biomolecular Sciences Building on 12/28/2009 from 7:30 am until 1:30 pm. This should not effect regular building power, but some hallway lights tied to the emergency power and the building's elevator, are likely to be out of service. <br />
<br />
While we have been assured by FM and NTS that this outage should not effect the normal building power or the network connectivity within the building, previous unplanned outages effecting the emergency electrical have also effected the building's external network connectivity, so there is a chance that network problems could arise with this outage. If there is an outage someone from staff will work to resolve any issues that remain, but will be unable to do anything to restore access until the end of the outage. <br />
<br />
Machines in AV Williams should be unaffected by this, so if you have concerns about the outage of need to get access to your files during the outage, for most data machines in AV Williams can be used. If you are unsure about what machines, if any, you can use to access your data, if the BSB network is down, please mail staff with the path to the data you are concerned about and we will let you know if what possible alternate methods of accessing your data exist.<br />
<br />
<endFeed /><br />
<br />
'''Please see our [[HelpDesk]] for additional support.'''<br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=2872Main Page2009-11-24T21:08:59Z<p>Ridge: </p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /> <br />
===Help Desk Holiday Hours===<br />
The UMIACS Help Desk will be operating with an amended schedule due to the Thanksgiving Holiday, On Wednesday 11/25 the Help Desk will be closing at 3pm and on Thursday and Friday, 11/26 and 11/27, the help desk will be closed. The help desk will re-open at it's normally scheduled time on Monday 11/30.<br />
<endFeed /><br />
<br />
'''Please see our [[HelpDesk]] for additional support.'''<br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=2526Main Page2009-04-24T13:21:35Z<p>Ridge: /* Anouncements */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
<br />
===Network down time for A.V. Williams 31XX Thursday April 30th 5am===<br />
We will be finishing a network equipment upgrade this Thursday, April <br />
30th beginning at 5am for the 3100 wing of the A.V Williams Building. <br />
These upgrades will provide gigabit ethernet access for all ports that <br />
have not already been upgraded in UMIACS offices and labs numbered <br />
31XX. The downtime is expected to last no more than 20 minutes, most <br />
workstations will only see a few short blips in service. <br />
<br />
The UMIACS help desk in avw 3142 will be opening earlier at 8:00am to <br />
accommodate any users with problems, we will be monitoring all supported <br />
workstations and desktops for problems associated with losing their <br />
connectivity. Thank you for your patience through this outage<br />
<br />
===New [[OpenLAB]] Desktop===<br />
We have added a new mac, Koala, to the desktops available in AVW 4462. Koala is replacing our old OpenLAB mac, Grizzly, and runs Mac OS X 10.5.<br />
<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is main place to find documentation and information about your account and technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].<br />
<br />
==Additional Support==<br />
<br />
If you need additional assistance, please contact the UMIACS Technical Staff.<br />
<br />
The Technical Staff can be reached by sending email to [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].<br />
<br />
If you have a problem with your email or a problem that would be better addressed by speaking to directly to a staffer, you can call or visit our Help Desk, <br />
<br />
Monday - Friday <br />
9:00am - 12:30pm and 1:30pm - 5:00pm. <br />
<br />
The Help Desk is located in Room [[AVW3142|3142]] of the A.V. Williams Building, and can be reached by phone at 301-405-1775.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=2458Main Page2009-03-12T17:20:09Z<p>Ridge: </p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
==OpenLAB Upgrade==<br />
Our OpenLAB facilities are being upgraded.<br />
<br />
Phase 1 has been completed, please use openlab.umiacs.umd.edu for all your remote login needs.<br />
<br />
Phase 2 has been completed.<br />
<br />
UPDATE: the migration has been postponed until March 16th 2009 due to a vendor problem.<br />
<br />
Phase 3 will be performed on Monday March 16th 2009. All home directories ([[NFShomes]]) will be unavailable for 3 hours from 10pm-1am. Please see [[OpenLABUpgrade]] for more information.<br />
<br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is main place to find documentation and information about your account and technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].<br />
<br />
==Additional Support==<br />
<br />
If you need additional assistance, please contact the UMIACS Technical Staff.<br />
<br />
The Technical Staff can be reached by sending email to [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].<br />
<br />
If you have a problem with your email or a problem that would be better addressed by speaking to directly to a staffer, you can call or visit our Help Desk, <br />
<br />
Monday - Friday <br />
9:00am - 12:30pm and 1:30pm - 5:00pm. <br />
<br />
The Help Desk is located in Room [[AVW3142|3142]] of the A.V. Williams Building, and can be reached by phone at 301-405-1775.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=2287Main Page2008-11-26T13:47:04Z<p>Ridge: /* Anouncements */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
*The UMIACS Help Desk is closing today (11/26) at 12:30 so that staff can prepare for the break. Staff will be on site until the institute closes, so for any urgent issues that crop up before the end of the day, please email staff. <br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is main place to find documentation and information about your account and technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].<br />
<br />
==Additional Support==<br />
<br />
If you need additional assistance, please contact the UMIACS Technical Staff.<br />
<br />
The Technical Staff can be reached by sending email to [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].<br />
<br />
If you have a problem with your email or a problem that would be better addressed by speaking to directly to a staffer, you can call or visit our Help Desk, <br />
<br />
Monday - Friday <br />
9:00am - 12:30pm and 1:30pm - 5:00pm. <br />
<br />
The Help Desk is located in Room [[AVW3142|3142]] of the A.V. Williams Building, and can be reached by phone at 301-405-1775.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=2183Main Page2008-09-22T17:08:23Z<p>Ridge: /* Anouncements */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
=BSB Electrical Outage 9/25 -9/26=<br />
Facilities management has requested an electrical outage for the Biomolecular Sciences Building thursday night. This Outage is expected to last longer any of the machines' UPS units, so as a matter of best practice the Technical staff tentatively plans to shutdown all machines in the building starting at 11pm. And will have someone on site at 7am to begin bringing machines back for the Friday workday. <br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is main place to find documentation and information about your account and technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].<br />
<br />
==Additional Support==<br />
<br />
If you need additional assistance, please contact the UMIACS Technical Staff.<br />
<br />
The Technical Staff can be reached by sending email to [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].<br />
<br />
If you have a problem with your email or a problem that would be better addressed by speaking to directly to a staffer, you can call or visit our Help Desk, <br />
<br />
Monday - Friday <br />
9:00am - 12:30pm and 1:30pm - 5:00pm. <br />
<br />
The Help Desk is located in Room [[AVW3142|3142]] of the A.V. Williams Building, and can be reached by phone at 301-405-1775.</div>Ridgehttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&diff=2182Main Page2008-09-22T17:06:35Z<p>Ridge: /* Anouncements */</p>
<hr />
<div>__NOTOC__<br />
==Anouncements==<br />
<startFeed /><br />
Facilities management has requested an electrical outage for the Biomolecular Sciences Building thursday night. This Outage is expected to last longer any of the machines' UPS units, so as a matter of best practice the Technical staff tentatively plans to shutdown all machines in the building starting at 11pm. And will have someone on site at 7am to begin bringing machines back for the Friday workday. <br />
<endFeed /><br />
<br />
==Technical Reference==<br />
<br />
Welcome to UMIACS Wiki. This is main place to find documentation and information about your account and technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].<br />
<br />
We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].<br />
<br />
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.<br />
<br />
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].<br />
<br />
==Additional Support==<br />
<br />
If you need additional assistance, please contact the UMIACS Technical Staff.<br />
<br />
The Technical Staff can be reached by sending email to [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu].<br />
<br />
If you have a problem with your email or a problem that would be better addressed by speaking to directly to a staffer, you can call or visit our Help Desk, <br />
<br />
Monday - Friday <br />
9:00am - 12:30pm and 1:30pm - 5:00pm. <br />
<br />
The Help Desk is located in Room [[AVW3142|3142]] of the A.V. Williams Building, and can be reached by phone at 301-405-1775.</div>Ridge