CS IT Support Wiki - User contributions [en]

Template:Red

2024-06-21T16:29:47Z

Phil: Adjust the red color to match Reasonable Colors

<noinclude>This template just turns a span of text red.

<code><nowiki>{{red|This text will be colored red}}</nowiki></code> → {{red|This text will be colored red}}
</noinclude><includeonly>{{{1}}}</includeonly>

Category:Test

2024-06-12T15:45:23Z

Phil: Blanked the page

Category:Test

2024-06-12T15:45:07Z

Phil: Created page with "Test category; please ignore. Category:All"

Test category; please ignore.

[[Category:All]]

Using Shibboleth

2024-06-11T20:39:48Z

Phil: idp.jh.edu → login.jh.edu

[http://shibboleth.net Shibboleth] is software that allows one website to use another website for login information, so that people who want to log in to a Shibboleth-based site are transparently redirected to a central login site to enter their account name and password and are then sent back to the original site along with their login credentials. This means that people don't have to remember individual login information for each site they want to access, and the individual sites don't have access to people's passwords.

(In JHU terms, for example, a webpage hosted on www.cs.jhu.edu, the CS Department webserver, could request that a visitor log in using his or her JHED credentials. The CS webserver would direct the visitor's browser over to JHU's login servers, which would then approve the login and send the browser back to the original webpage. The CS-based webpage would then receive the JHED login information without actually having to know anything about the person's JHED password or details of the login. Shibboleth also allows CS webpages to permit logins with either CS ''or'' JHED credentials.)

This page describes how to use the Shibboleth resources available within the Computer Science department on your own webpages. For information about logging in to a site that uses Shibboleth, see [[Shibboleth]].

== Terminology ==

Shibboleth has a few terms that is uses for specific parts of the software. The central server that allows people to log in is called an ''Identity Provider'' or ''IdP''. The web server that wants to use those login credentials is called a ''Service Provider'' or ''SP''. Every IdP and SP is uniquely identified by its ''EntityID''. An EntityID looks like a URL (the main CS webserver's EntityID is <nowiki>https://www.cs.jhu.edu/shibboleth</nowiki>), but it doesn't have to actually go to a website.

Shibboleth only provides ''authentication'', which means that it provides a trusted source of account names. Shibboleth provides information that is equivalent to saying things like "the person at this browser has proven that they own the JHED ID that I will tell you about." It is up to you to configure your own ''authorization'' and determine which JHED IDs and CS accounts will be allowed to access your webpages.

== Shibboleth Servers Available in CS ==

Johns Hopkins operates an IdP that allows logins with [https://my.jh.edu/portal/web/help/what-is-jhed JHED IDs]. If you want to set up your own server to use the JHU IdP, you'll have to contact [http://www.it.johnshopkins.edu/services/directoryservices/jhea/Shibboleth/ the Enterprise Auth team], but our webserver (www.cs.jhu.edu) is already set up to use JHED IDs, so websites hosted there only need the configuration documented below.

The CS department runs an IdP for logins using CS Grad Net accounts. If you want to run your own web server that uses CS accounts, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance. The CS department webserver (www.cs.jhu.edu) is already set up to use CS Grad Net accounts, so websites hosted there only need the configuration documented below.

The CS department's webserver (www.cs.jhu.edu) is configured as an SP for both JHED and CS Grad Net accounts.

== Account Information ==

Shibboleth provides a bit of information about the logged-in account, but the provided information differs between JHED and CS accounts. One thing that's the same for both is the username data, which is provided in the <tt>REMOTE_USER</tt> CGI environment variable.

If a person logs in via JHED, their <tt>REMOTE_USER</tt> username will be their JHED ID followed by "@johnshopkins.edu". Thus, a person with a JHED ID of "jdoe1" would be identified as "jdoe1@johnshopkins.edu".

If a person logs in via a CS Grad Net account, their <tt>REMOTE_USER</tt> username will be their CS Grad Net account name followed by "@cs.jhu.edu". Thus, a person with a CS Grad Net account name of "janedoe" would be identified as "janedoe@cs.jhu.edu".

== Session Length ==

Once someone logs into a CS-hosted webpage via Shibboleth, the CS webserver establishes a session to remember the login. So long as the session exists, the person will be able to continue accessing Shibboleth-protected pages without having to log in again.

Sessions are removed after one of two things occurs:

* Two hours pass without any activity from the logged-in person (i.e. the person didn't access any pages for two hours)
* Eight hours pass since the person's most recent login

== How to Use the www.cs.jhu.edu ''SP'' ==

You have two choices about how to use Shibboleth with your www.cs.jhu.edu webpages.

The first option is to put all of the authorization into a <tt>.htaccess</tt> file and let the www.cs.jhu.edu webserver manage everything. With this option, the webserver itself will determine who is allowed to see your pages. If you want to protect plain HTML files (i.e. you're not using [[Setting Up CGI Scripts on the CS Webservers|CGI]], [[Running PHP Scripts on the CS Webservers|PHP]] or something similar), this is the only option available to you. Even if you have dynamic content, your programs don't have to know anything about logins or authorization if you use this authorization approach.

The second option is to tell the www.cs.jhu.edu webserver that you want Shibboleth available but that your programs will decide what to do with the Shibboleth login information. This option can be more difficult to set up, but it gives you more flexibility in your treatment of the information you get from Shibboleth.

=== Option One: Webserver Authorization ===

Under <tt>public_html</tt>, you need to create a file named <tt>.htaccess</tt> ''in the top level directory'' where you want to restrict access. For example, if you wanted to require logins for any page under <nowiki>http://www.cs.jhu.edu/</nowiki>~''account''/secret, you would create the file as <tt>~/public_html/secret/.htaccess</tt>. Unless you simply want to give anyone with a JHED or CS account access, you'll also need to make a file named <tt>.htgroup</tt> that contains a group name and the accounts that should be members of that allowed group.

The <tt>.htaccess</tt> file should contain the following:

<pre>
# This activates shibboleth
AuthType Shibboleth
<IfVersion < 2.4>
ShibCompatWith24 On
</IfVersion>

# Shibboleth only works if the webpage is accessed via HTTPS (not HTTP). The
# following setting will redirect any clients from HTTP to HTTPS so that logins
# will always work. (If you don't use this and someone accesses the page via
# HTTP, they'll get a "No peer endpoint available to which to send SAML
# response" error message from the IdP.)
ShibRequestSetting redirectToSSL 443

# This requires everyone to log in before they can see the protected pages. If
# you don't have this line, people still won't be able to see the pages, but
# they won't be prompted to log in, so they'd have no way to get access.
ShibRequestSetting requireSession 1

# In order to access the pages, the person must be a member of the group named
# "allowed". You can use a different name for the group if you prefer; just
# make sure the group name matches what's in the .htgroup file.
Require group allowed

# This is the file that contains the definition of the "allowed" group. The
# path name must be fully qualified, so replace "<account>" with your account
# name. The file doesn't have to be under ~/public_html (and it's generally
# recommended that it go elsewhere) but putting it here simplifies the
# permissions necessary for the webserver to see it.
AuthGroupFile /users/<account>/public_html/secret/.htgroup

# This ensures that no one can see the contents of the group file.
<Files .htgroup>
Order Deny,Allow
Deny from all
</Files>
</pre>

Your <tt>.htgroup</tt> file contents will vary more depending on who you need to give access to. To continue the above example, if the people with ''JHED IDs'' '''jdoe1''' and '''fbar3''' should be given access as well as the person with ''CS account'' '''mumble''', put the following into <tt>~/public_html/secret/.htgroup</tt>:

<pre>
allowed: jdoe1@johnshopkins.edu fbar3@johnshopkins.edu mumble@cs.jhu.edu
</pre>

The format of the file is described in the Apache [http://httpd.apache.org/docs/2.2/mod/mod_authz_groupfile.html#authgroupfile AuthGroupFile] directive.

When you're done, set the [[File Permissions for Webpages|appropriate permissions on the files]] with the following command from the command line in the directory where you've saved them:

chmod 0604 .htaccess .htgroup

==== Using Only JHED IDs ====

By default, people logging into your site will be able to choose whether to use JHED or CS accounts. If you only want them to use JHED IDs, add this line anywhere in your <tt>.htaccess</tt> file:

<pre>
ShibRequestSetting entityID https://login.jh.edu/idp/shibboleth
</pre>

==== Using Only CS Accounts ====

By default, people logging into your site will be able to choose whether to use JHED or CS accounts. If you only want them to use CS Grad Net accounts, add this line anywhere in your <tt>.htaccess</tt> file:

<pre>
ShibRequestSetting entityID https://gidp.cs.jhu.edu/idp/shibboleth
</pre>

=== Option Two: Web Application Authorization ===

There is a lot more potential variation for this option, so only the most general information can be covered. If you need further assistance, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] with your questions.

At the very least, you will need a <tt>.htaccess</tt> file in the root directory of your web application. In it you will need at least the following directives:

<pre>
AuthType shibboleth
<IfVersion < 2.4>
ShibCompatWith24 On
</IfVersion>
Require shibboleth
</pre>

Those will make Shibboleth information available to the application, but will not restrict access or even trigger Shibboleth authentication. (If you want to require Shibboleth authentication, add a line containing <tt>ShibRequestSetting requireSession 1</tt>.)

==== Custom Programming ====

If you're writing your own application, all you really need is to look at the contents of the <tt>REMOTE_USER</tt> environment variable to get the authenticated username (as [[#Account Information|described above]]). The particulars of how you grant access based on that username are up to you.

===== Logins =====

To trigger a login, direct the person on the website to the URL <tt><nowiki>https://www.cs.jhu.edu/Shibboleth.sso/Login</nowiki></tt>. (Obviously, if your page is already being accessed on <nowiki>https://www.cs.jhu.edu</nowiki> you don't need the protocol and hostname in your link.)

There are a few URL parameters you can use in conjunction with this. The <tt>target</tt> parameter gives the URL that the person should return to after logging in. If you don't use this, they'll be returned to the main https://www.cs.jhu.edu page, which is almost certainly not what you want.

The <tt>entityID</tt> parameter can be used to pick either JHED or CS as your authentication source (rather than allowing visitors to choose from between them, which is the default). Set <tt>entityID</tt> to <tt><nowiki>https://login.jh.edu/idp/shibboleth</nowiki></tt> for JHED IDs and <tt><nowiki>https://gidp.cs.jhu.edu/idp/shibboleth</nowiki></tt> for CS Grad Net accounts.

As an example, here's a link that would use only JHED IDs and would return people to <nowiki>https://www.cs.jhu.edu/~example/myapp</nowiki> after they've logged in:

<nowiki>https://www.cs.jhu.edu/Shibboleth.sso/Login?target=https://www.cs.jhu.edu/~example/myapp&entityID=https://login.jh.edu/idp/shibboleth</nowiki>

===== Logouts =====

We recommend that you '''''not use''' explicit logouts'' and instead just rely on the implicit length of sessions in the SP and IdP. The concept of "logging out of Shibboleth" is a surprisingly complicated one, for reasons sketched out on the [[Shibboleth#Logging Out|Shibboleth]] page (and detailed on the Shibboleth wiki's [https://wiki.shibboleth.net/confluence/display/SHIB2/SLOIssues Single Logout Issues] page).

If, despite the above, you really want to have a logout link in your webapp, you can link to <tt><nowiki>https://www.cs.jhu.edu/Shibboleth.sso/Logout</nowiki></tt>. That link takes at least one URL parameter: <tt>return</tt> gives a URL to which the person logging out may be sent after logout. As of March 2014, neither JHED nor CS uses that parameter, but it's useful to include it in case the Shibboleth implementations are changed in the future.

==== Integration with Other Applications ====

If you're using a third-party program, like [https://mediawiki.org MediaWiki] or [https://wordpress.org/ WordPress], you'll have to see if there are existing plugins or documentation for Shibboleth. You can also email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance; the IT group has experience with Shibboleth integration for at least MediaWiki and DokuWiki.

[[Category:Webpages and Webservices]]

[[Category:Security]]

Working Remotely

2024-06-07T14:40:52Z

Phil:

{{red|THIS PAGE IS '''''UNDER CONSTRUCTION'''''. If you're looking for info on connecting to the JHU VPN, please visit: [https://support.cs.jhu.edu/wiki/VPN_-_JHU our JHU VPN page]. }}

==INTRO==

:There may be instances where you as a JHU faculty, student, or staff member need to work remotely, off-campus, and off the JHU Network.

:We are used to the usual tools while we work in our offices, including your work computer, desk telephone, etc. You might also have papers in your office (hopefully, secured) that include passwords and other related credentials.

:When forced to work remotely, you have to consider how you will access the above items, when needed. At home, you might have a computer that needs access to the JHU Network. Remotely, it could be your phone or a laptop that is the tool you need to use.

:Being prepared in advance for working remotely is essential. You should consider listing all the tools you would need to work at home or abroad. You might need to make modifications of your home computer or laptop to reach JHU's Network. You might need a safe repository for your account credentials so that you can access them when off the JHU Network (some might store a spare set of passwords securely at home, for instance.)

:This page is mostly geared to pointing you in a direction to allow you access to the JHU Network, as many JHU IT-based services require you to be on the JHU Network to access them.

==WSE IT Remote Work Info Page==

:The Whiting School IT group has put together a page regarding working from home. We recommend you to take some time out and read through it for excellent info on a variety of technical situations you might be in when working remotely and how to effectively handle those situations.

::[https://wseit.engineering.jhu.edu/get-help/wse-remote-work-info https://wseit.engineering.jhu.edu/get-help/wse-remote-work-info]

VPN - JHU

2024-06-07T14:40:03Z

Phil:

==INTRO==

:Several JHU IT-based resources require your computer to be connected to the JHU network for access. For example, JHU-located share drives and certain JHU websites/services. If you're outside of JHU, for instance, at home or at a hotel, you are not on the JHU network, and therefore, cannot access the JHU Network-only resources.

:Enter the '''VPN'''. A VPN ('''''V'''irtual '''P'''rivate '''N'''etwork'') is a way to access resources of another network, for example, a business's network, without physically residing on that network. You can connect to a VPN from home/mobile, and it will look to your computer and to the business's server as if you were on that server's network, even if physically, you're not.

:JHU hosts its own VPN. The JHU VPN will allow JHU users' home/mobile/etc. computers who are ''outside'' of the JHU network to connect to JHU as if they were physically on campus.

 

==Connecting to the JHU VPN==

===STEP 1: Setting Up Multi-Factor Authentication===



:JHU requires [https://it.johnshopkins.edu/services/directoryservices/jhea/AzureMFA/AzureLoginMFA '''M'''ulti-'''F'''actor '''A'''uthentication (MFA)] to access some of its services... ''including the JHU VPN''. JHU uses ''Microsoft Azure'' for providing JHU's Multi Factor Authentication service.

:(Besides this page we're providing you, WSE IT has put together a document discussing MFA [http://wseit.engineering.jhu.edu/get-help/multi-factor-authentication here] as well.)

:To get started with MFA, you will need to visit the Azure MFA Resource Center's '''''[https://livejohnshopkins.sharepoint.com/sites/Office365Hub/SitePages/Multi-Factor-Authentication.aspx Enrollment Page]''''' to enroll. 

:That page and its video will show you how to enroll your JHED ID with the Azure MFA. The video is very helpful in explaining the process. You are encouraged to watch it all the way through.

====Authenticators====

:As part of the MFA setup process, you will end up having to choose an '''authenticator''' method to use. There are several authenticator methods:

* Text your phone: When JHU needs you to enter your MFA code during login to JHU's MFA-required pages/apps, they will text your phone with the MFA code that you will use to enter into whatever prompt they send you.

* Use an app/program: Alternatively, you can choose to install an authenticator program on your computer (or phone.) The authenticator program, when run, will provide the 6-digit number to enter when you are prompted at JHU for your MFA code. JHU suggests you use the Microsoft Authenticator App (for Windows) to generate that numerical code. You can download Microsoft Authenticator according to instructions from the enrollment process video. Additionally, you can choose to run other authenticators to run (under Windows) instead, including a program called WinAuth. Macs, Androids and IPhones have various authenticators available as well. Note that the codes are generated using time-based factors... so, the code you generate needs to be entered soon (up to a minute) when you are prompted, otherwise, you need to generate another code.

:Please install your Authenticator program before continuing.

::NOTE: If you want to change your authenticator method or manage your MFA at some point, please first visit the main [https://it.johnshopkins.edu/services/directoryservices/jhea/AzureMFA/AzureLoginMFA Azure MFA page] and then click on ''Manage Azure MFA''.

You will need your MFA configured in order to access the JHU VPN in the next step.

{{red|'''NOTE:''' If you have any issues with setting up Multi-factor authentication, ''you should contact'' [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support JHU IT's support helpdesk]}}

 

===STEP 2: Installing and Running the JHU VPN Client Program, JH Pulse Secure===

:Please visit the [https://cds.johnshopkins.edu/vpn JHU VPN Resource page.]

:Once there, Under '''VPN Quick Links''' on the right, choose '''Request VPN Access'''. It's possible you might already have VPN access (and if you think you already do, you can skip below the next step.) {{red|'''NOTE:''' As of 2020, we're told that you might not need to request VPN access, as access is now granted automatically.}}

:Next, below the VPN Quick Links section on that page, you'll find '''VPN CLient Installs (for New VPN Installs).''' Click on the operating system you're downloading for. This will download the '''''Pulse Secure''''' software that will run on your computer as your gateway to the JHU VPN.

:Install the Pulse Secure package.

:Run the Pulse Secure program. The following is for a Windows systems running Pulse Secure. Other operating systems may be similar.

* Look for ''Connections''.

* If for some reason, there are no connections listed, follow the steps directly below...
** Click on the + symbol right next to the word Connections.
** The + sign opens up the '''Add Connections''' section.
***Leave the '''Type''' as is.
***Give the VPN connection a '''Name''' (e.g. ''JHU VPN''), just so you can identify it.
***Then, enter in the '''Server URL''' (which is basically, the VPN address. Use '''vpn.''jh''.edu''' (Notice that it's "jh" and not "jhu" in the server name.)
***Now, click Add, and you should have a new connection ready to go.

*Choose the JHU VPN from your list of connections.

*Click Proceed

* You will be prompted for your JHED credentials. Enter them.

*You'll see '''Enter code'''. This is where you need your MFA ''Authenticator'' code from Step 1 above. So, depending how you set up your MFA, you might receive a code via Text or you might need to run your Authenticator program (e.g., Microsoft Authenticator, WinAuth, etc.) and enter in the 6-digit code it provides you.
** You MFA code changes every minute, so if you don't type in your code in time, refresh your Authenticator and try the next code it gives you.

* Once you enter that code, Pulse Secure will complete making the VPN connection.

*When you are done for the work day, go back to the Pulse Secure App and click Disconnect.
**Note that when you are on the VPN, you are now passing all your computer's network traffic through JHU before it goes out to the rest of the Internet. When you are done using the VPN, disconnecting from Pulse Secure will allow your computer's network traffic to run through your ISP's network directly out to the Internet (as it normally does.)

{{red|'''NOTE:''' If you have any issues with installing or using the JH Pulse Secure client on your computer, ''you should contact'' [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support JHU IT's support helpdesk].}}

 

==Changing your default JHU VPN authentication Method==

:By default, the new JHU VPN (hosted by Microsoft Azure) seems to make texting your phone the way to provide you your MFA authentication code to use to connect to the VPN. Some users might want to change from the texting method to using an '''Authenticator app''' (e.g., Microsoft Authenticator, WinAuth, or similar) instead, as it was before JHU moved to using Azure.

: To change your default authentication method, simply log into [https://mysignins.microsoft.com/security-info https://mysignins.microsoft.com/security-info] ''Once logged in, if you're not directed directly to the Security Info page, simply click '''Security info''' on the left.'' You'll see a list of your authentication options, and you can change the default option to using a Hardware Token (Authenticator App) instead of the Phone (text) option. You can also add additional methods if you choose to.

{{red|'''NOTE:''' If you have any issues with setting up your Authenticators, ''you should contact'' [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support JHU IT's support helpdesk]}}

 

[[Category:Security]]
[[Category:Networking]]

Services Provided By CS IT

2024-06-07T14:38:38Z

Phil:

===SCOPE OF SERVICES===

{{messagebox|CS IT Staff members work in a hybrid schedule, so some of the staff might be working remotely, while others may be on campus at Malone Hall.  We will continue to be available ''M-F, 8:30 to 5pm'', but although we might be on campus, some of our services may only be provided via online means. Please see: [[Obtaining_CS_IT_Services_Remotely | Obtaining CS IT Services Remotely page]] for further information.|type=warning}}

The [https://www.cs.jhu.edu/it-support CS IT Support Group] offers a variety of IT services to its customers (CS Faculty, students, staff, etc.)

Our goal is to provide friendly, helpful IT support in a timely manner. We are very customer-oriented and strive for keeping our users informed and up-to-date with the status of support requests and the status of our CS computing infrastructure as a whole.

We provide a documentation wiki we call the '''CS IT Support Wiki''' at [https://support.cs.jhu.edu https://support.cs.jhu.edu] with extensive details on the many services we provide. (The page you're reading now is a part of the CS IT Support Wiki.)

We are available via email at '''{{mailto|support}}'''.

'''For general user support, {{red|we are available ''M-F 8:30am - 5pm.}}''''' (Please see the yellow bar near the top of this page.)

We also provide a '''[[Notices]]''' page available at [[Notices | https://support.cs.jhu.edu/wiki/Notices]] providing the status of our servers, computing labs, etc.

As the CS IT group resides in Malone Hall, most of our support and services are directed there.

Our main areas of IT Support include:

* The educational mission of the CS Dept.(computing resources for coursework, including its computing lab Linux systems.)
* The day-to-day operations of the CS Dept. (IT support for the CS Office's administrative computers.)
* Providing CS infrastructure-based services (email, web space, networking, printing)

To support the above, our specific CS IT Support services can be broken down into three categories:
* [[#Computer Systems We Manage/Maintain/Support | Specific Computer Systems We Manage/Maintain/Support]]
* [[#CS Online Services | CS Online Services]]
* [[#Infrastructure|Infrastructure]]

Below is a comprehensive list of the services that the CS IT Support Group provides to our users. You can find more specific details about these services within the categories found in our aforementioned [https://support.cs.jhu.edu CS IT Support Wiki]. If you have additional questions, please email us at our {{mailto|support|support}} address.

 

==Computer Systems We Manage/Maintain/Support==

We maintain...

* All of the Fedora Linux-based [[:Category:Computers_Available_on_the_CS_Network | computer systems]] located in our [[:Category:Labs | CS Teaching Computer Labs]], as well as our department's main [[:Category:Linux_Clients|compute servers]].

* CS Office staff (MH 160) Windows systems (CS IT does not provide support for Macs.)

* Centralized servers providing CS online services.

:''''' NOTES:'''''
<ul style="list-style-type:circle; list-style-image:none; margin-left:4em">
<li>CS IT '''does ''not'' offer''' direct support for ''individual's'' '''or''' [https://support.cs.jhu.edu/wiki/Category:Research_Computing ''research lab's'' computer systems] (laptops, desktops, servers, tablets, smartphones, network equipment, etc.) Instead...</li>

:<li>CS Faculty and researchers and their students typically '''self-maintain''' their own systems. '''(This includes [[Malone_G29_Server_Room | server room]] rack setup and server installs.)''' See [https://support.cs.jhu.edu/wiki/Category:Research_Computing Research Computing] for more information.</li>

:<li>If you're having an issue with or need to configure [[Personal_or_Research_Lab-owned_Computer_Issues | ''your own'' or ''research lab's'' system]], we might be able to offer you advice, but, for any support work to be done on them, you may want to consider the following options:
<ol>

:<li> Try contacting [[Contacting_WSE_IT_Support| WSE's (Whiting School of Engineering) IT group]]. They can look at your system, but if it is something they cannot address, they might be able to provide you with other resources for further troubleshooting or repair. In some cases, WSE IT can help administer your system. </li>
:<li> or try [[Contact_JHU_IT_Support | contacting JHU's IT Helpdesk]].</li>
:<li> '''Mac''' users might want to visit [https://store.jhutechstore.com JHU's Technology Store] in the ''Levering Hall Room 113'', as they offer some technical support for Apple products. ''See our CS IT Support Wiki's page on [[Personal or Research Lab-owned Computer Issues]]''</li>
</ol></li>

<li> CS IT '''does not''' purchase, spec, or price out computer-related equipment for ''other than'' the CS Office Staff systems, the CS Teaching Computer Labs located in Malone Hall, and for CS central infrastructure support in Malone Hall. If you need the department to purchase a computer for you, you'll need to speak with your PI, advisor, or someone in the CS Dept office (MH 160.)</li>

<li> CS IT '''does not''' provide cables (USB, Video, adapters, other computing supplies) ''other than'' Ethernet cables. If you're looking for different cables/adapters, thumb drives, SD cards, etc., please visit [https://studentaffairs.jhu.edu/computing/hopkins-technology-store/ JHU's Technology Store] in the Levering Hall's Sherwood Room.
:<li> '''Ethernet cables: '''We do have ethernet cables that we can make available, as needed.'''
:<li> '''Power cables: '''We do have a limited number of power cables we can make available, as needed.
:<li> '''Thumb drives:'''   Currently, we have a limited number of thumb drives that we can '''''lend out''''' for '''''short-term''''' use. Otherwise, you can try the Technology Store mentioned above.
:<li> '''Mac Users:''' The [https://studentaffairs.jhu.edu/computing/hopkins-technology-store/ JHU Technology Store] has a wide range of Apple products available.
:<li>'''Other computing supplies:''' Also, in a pinch, there is a [https://www.microcenter.com/site/stores/parkville.aspx?storeid=125 local Micro Center store], or of course, you can try [https://www.amazon.com Amazon].)
</ul>
 

==CS Online Services==

CS IT provides the following online services to CS-affiliated users.

* '''[[:Category:Accounts | CS Linux Shell Login Accounts]]:''' We can provide you a Linux shell login [[Obtaining_CS_Computer_Accounts | account]] for our CS Lab clients and compute servers. This provides a user a ''home directory'' on our servers. A CS Linux account provides you a [[:Category:Mail | CS email address]] and [[:Category:Webpages_and_Webservices | webpage space.]] We maintain [[:Category:Backups | backups]] of home directories.

* '''[[:Category:Mail |CS Email Services]]:''' CS runs its own email services and can provide you with a CS email address, if requested. (A CS Linux shell login account ''automatically'' provides you a CS email address.) You can choose to [[Forwarding_Mail|forward]] CS email to your preferred email address.) For receiving CS mail, we provide both [[:Category:Receiving_Email | IMAP and POP services.]] We also make available a web interface for CS email access we call [[Webmail | webmail]]. CS also provides [[:Category:Mailing_Lists | mailing list services.]] Additionally, we filter our emails in a variety of ways to [[:Category:Spam|combat spam]]. All email ''stored on our email servers'' is backed up regularly.

::'''NOTE:''' CS IT does '''not''' maintain the ''JHU Exchange email service.'' If you have issues with JHU Exchange email (or calendar), please [[Contacting_JHU_IT_Support | open a trouble ticket with JHU IT]].

* '''[[Requesting a Static IP Address on the CS Network|CS-based DNS Service]]:''' We can set up hostnames in the cs.jhu.edu domain for your CS-affiliated system.

* '''[[:Category:Webpages_and_Webservices | CS-Web Services]]:''' We provide space (via a linux shell login) and instructions for creating webpages accessible through our CS webservers.

* '''[[:Category:MySQL | MySQL Database Service]]:''' CS hosts its own MySQL database service and can provide you a database for you to design and maintain. Our databases are backed up regularly.

* '''CS-provided File Storage:''' CS provides storage in the form of home directories for those with Grad Net and Ugrad Net [https://support.cs.jhu.edu/wiki/Category:Accounts CS Linux accounts] (although CS Ugrad accounts are subject to [[Disk Quotas|disk quotas]]). CS Grad Net accounts may access their home directories as [[Mapping CS Home Directories Using SAMBA (SMB)|network shares]] (for example, via Windows systems.) CS Grad Net accounts also have storage for (limited) ''large'' data available on our [[Grad_Net_Static_Datashare|Grad Net Static Datashare]].

::'''NOTE:''' CS IT does '''not''' maintain the ''JHOneDrive (Microsoft OneDrive) storage service''. If you have issues with JHOneDrive, please [[Contact_JHU_IT_Support | contact JHU IT Support.]] Alternatively, you can [[Contacting_WSE_IT_Support | contact WSE IT's Help Desk]] for JHOneDrive assistance as well.

* '''[[:Category:Virtual_Machines_(VMs) | Virtual Machine Services (VMs)]]:''' CS hosts a Virtual Machine server for coursework and light research. CS faculty, instructors, and students may request a VM be created for CS class use and CS-related school projects. A VM we create for the requester is then configured and maintained by the requester. VMs ''are not'' centrally backed up.

:'''''NOTE:'''''

:: Please remember that other than for the ''CS office staff's systems'', the ''CS Teaching Lab computer systems'', and the ''CS infrastructure servers'', CS IT ''does not'' provide direct support (repairs/configuration/troubleshooting/etc.) for [https://support.cs.jhu.edu/wiki/Personal_or_Research_Lab-owned_Computer_Issues other people's/labs' computers].

 

==Infrastructure==

===Network===
Malone Hall contains several different networks used by different groups within the building. Three of these are [[:Category:Networking | networks available for CS user access.]]

CS IT provides:

* Network jack-activation for CS-related offices, including initial troubleshooting of the actual network port.

* Static or dynamic IPs. '''Note:''' ''We'' '''do not''' ''configure an [https://support.cs.jhu.edu/wiki/Personal_or_Research_Lab-owned_Computer_Issues individual's] or [https://support.cs.jhu.edu/wiki/Personal_or_Research_Lab-owned_Computer_Issues research lab's] computers' network configuration.'' Due to the differences in network configurations amongst the variety of operating systems that exist now, we merely provide you the IPs and related information with general [[:Category:Networking | CS Networking documentation.]]

* We can provide you a network (ethernet) cable, if needed. Please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] to request an ethernet cable.

:'''''NOTES:'''''

:: We do not manage WiFi in Malone Hall. For WiFi, please see [[Wireless Networking]].

:: CS '''''does not''''' have its own perimeter firewall, however, '''''JHU does'''''. For firewall issues, please see [[Requesting Open Ports on the JHU Firewall]].
 

===Printing===

* We provide access to the [[:Category:Printing|CS IT-Managed printers]] located on each floor of Malone Hall, in addition to the department's copier in Malone Hall 154.

* We also change toner in the CS IT-managed printers when necessary. 

* Our [[:Category:Linux Clients|CS Grad and Ugrad Teaching Computer Labs' Linux systems]] are configured to print to the printer residing in each lab.

:'''''NOTES:'''''

:: The CS IT group '''does not''' supply or change paper in the printers we manage. Users can obtain paper from the CS Admin Office, Malone 160.

:: Our CS IT-managed printers are currently available to anyone to print to from your own system on the CS (and some JHU) networks.

:: The CS IT group '''does not''' configure [https://support.cs.jhu.edu/wiki/Personal_or_Research_Lab-owned_Computer_Issues user-owned or research labs-owned computers] to print to our printers.
 

===Additional Infrastructure And Service Notes===
:'''''Audio/Visual''''' (including '''conference room''' and '''office A/V''') services and support in Malone Hall are handled by other groups within JHU. Please see: [[:Category:Audio-Visual | Audio-Visual]].

:'''''Power, HVAC-related, and other physical issues''''' in a room or office are handled by [http://www.jhfre.jhu.edu/ JHU Facilities] You can also submit a [https://maximo.jhu.edu/ezrequest/login/homewood Facilities Request] '''NOTE:''' You '''may''' need to be on a ''JHU network'' on the ''JHU VPN'' to access the Facilities Request page.

:Support for '''''office telephones''''' are handled by [https://it.johnshopkins.edu/it-services/network-getting-connected/telecommunications/ JHU Telecommunications]. JHU also provides [https://johnshopkins.service-now.com/serviceportal?id=kb_article&sys_id=c551f9951bc47bc081e3a79b2d4bcb43 a page about '''''cell phones''''']

:For '''''office furniture issues,''''' please visit the front desk person in Malone Hall 160, who can direct you to the appropriate staff member.

:'''''Malone Hall room scheduling''''' is handled by the CS Dept's Administrative staff. Please visit [http://engineering.jhu.edu/siteauth/malonerooms/request.html http://engineering.jhu.edu/siteauth/malonerooms/request.html]

:'''''Maryland Hall 310 Classroom's Computers''''' are handled by others at JHU, '''''not by CS IT'''''. Please see: [[Maryland Hall 310 Classroom]]

:'''''Cables, adapters, computer supplies, and Apple (incl. Mac & Ipad) products''''' are available from the [https://studentaffairs.jhu.edu/computing/hopkins-technology-store JHU Technology Store], located in the Levering Hall's Sherwood Room.

:'''''Electronics And Paper Recycling''''' is handled by [https://www.jhfre.jhu.edu/services/plant_operations/recycling JHU Recycling]. Email them directly at [mailto:recycling@jhu.edu recycling@jhu.edu]

:'''''Mail/Shipping/Receiving:''''' Please speak to a member of the CS office staff in Malone Hall 160.

:'''''J-Cards/J-Card Readers:''''' Contact the J-Card people. Info at: [https://studentaffairs.jhu.edu/jcard https://studentaffairs.jhu.edu/jcard]

[[Category:Support Options]]
[[Category:Research Computing]]

Requesting Software Installation On A CS Lab Linux Computer

2024-06-07T14:36:50Z

Phil:

If you need a software package installed onto one of our CS [[:Category:Linux_Clients|Linux clients]] for your coursework, follow these steps:

* {{red| Check the computer to make sure that ''the software isn't already installed''. It's surprising how many people don't do this first.}}

* If the software is not on the computer, please fill out the [https://support.cs.jhu.edu/forms/sw-request '''Software Request Form'''] (also available from our [[Forms|Forms page]].)
** You must fill in the form ''completely'' and click '''''Submit'''''.

We will let you know if the request was approved and when the software is installed.

==NOTES==

* Not all software is approved for installation.

* Please do not try to install software on our machines. In some rare cases, if you need certain software available that our group doesn't maintain, we will discuss alternatives with you. Contact [mailto:support@cs.jhu.edu CS IT Support] in those cases.

* ''Please provide '''several business days notice''' for software to be installed.''

[[Category:Software]]
[[Category:Computers Available on the CS Network]]
[[Category:Linux Clients]]
[[Category:Software Available On The CS Linux Clients]]

Redirect Your Webpage To Another Website

2024-06-07T14:36:16Z

Phil:

==INTRO==

:You want to take your personal website on our server, for example:

:::your Grad/Research account's webpage: '''<nowiki>http://www.cs.jhu.edu/~mary</nowiki>'''

:::::or

::: your Ugrad account's web page: '''<nowiki>http://ugrad.cs.jhu.edu/~mary</nowiki>'''

:and have all requests for your page ''redirected'' to another website, for example:

:::'''<nowiki>http://some-other-webserver.com/~mary</nowiki>'''

==Method To Redirect Your Personal CS Webpage To A Different Site==

:'''Add a ''redirect'' line''' to the '''''.htaccess''''' file in your ''public_html'' directory on your Grad and/or Ugrad account, depending on which URL above you want to use. (Remember, if you have both a Grad and a Ugrad account, and you want to have the redirect work for both, you need to follow the following instructions ''for both accounts''.)

:{{red|'''IMPORTANT!''' There are some ''special lines of code'' already in the .htaccess file that make ''PHP'' work on our systems. Please '''''do not erase''''' that code from the file. Just add the following '''Redirect''' line. }}

:The '''Redirect''' line to should look similar to this:

::<code>Redirect 307 /~mary <nowiki>http://some-other-webserver.com/~mary</nowiki></code>

:In the example above, anyone surfing to '''<nowiki>http://www.cs.jhu.edu/~mary</nowiki>''' (Grad account) or to '''<nowiki>http://ugrad.cs.jhu.edu/~mary</nowiki>''' (Ugrad account) will get redirected to '''<nowiki>http://some-other-webserver.com/~mary</nowiki>'''

:You can ''change'' or ''remove'' the redirection at any time simply by editing the .htaccess file. However...

===NOTES:===

::* If you want to ''stop/remove'' the redirection you need to remove your '''Redirect''' line from the '''.htaccess''' file. '''''Do not''''' remove the other existing lines from the file.

::* Please {{red|'''''do not''''' delete the '''.htaccess''' file.}} If you do, you'll break PHP.

[[Category:Webpages and Webservices]]

Preventing Your Programs From Overrunning Our Computers

2024-06-07T14:35:32Z

Phil:

== Introduction ==

:As part of being a Computer Science student, you will no doubt create and run your own programs on our [[:Category:Linux_Clients|CS Linux Systems]]. You also might be downloading programs from elsewhere and running then on our systems as well.

:It's possible that software you write (or software you've downloaded and run) could, when running, exceed the existing resources on our systems.

== Computing System Resources that Could Be Exceeded ==

* Memory (RAM)

* CPU (processing power)

* Disk space
** ''Ugrad Net'' users have a [[Disk Quotas|disk quota]] to prevent that.
** ''Grad/Research Net'' users do not have specific disk quotas but must realize that they share their disk space with faculty, staff, etc. So, they must pay close attention to the disk space they use.
** Disk space not only included your home directory, but can also include your use of the Linux systems's '''/tmp''' directory as well.

==Typical Symptoms of Exceeding Computer Resources on Our Linux Systems==

* Timeouts ssh'ing into the computer.

* Programs run ''much'' slower than usual

* Programs stop running because they run out of RAM or swap disk space.

==Who Is Affected When Your Program Uses Up Resources on One of Our Linux Systems?==

:{{red|Because all our our CS Linux computers are '''multiuser''' systems, programs that exceed the computer's resources, slowing down the system, could potentially affect '''''all''''' the users logged into those systems, remotely, or at the actual computer console.}}

:Exceeding the computer's resources could also affect programs running in the background, perhaps as part of the computer's own system software or other users' batch jobs.

:'''''So... always be aware that you are not necessarily the only one logged into a system when you're running your own programs.'''''

==Tips to Prevent Your Programs from Exceeding the System Resources on Our Computers==

* Try to design your programs and/or datasets so that their running memory requirements '''do not exceed''' the capabilities of the system they're running on. Therefore, become familiar with the specs of our CS Linux systems:
** [[Linux_Clients_on_the_CS_Grad/Research_Net|Specs on our Grad/Research Net Linux Computers]]
** [[Linux_Clients_on_the_CS_Undergrad_Net|Specs on our Ugrad Net Linux Computers]]

* Try to '''avoid using the system's complete RAM memory''' as much as possible. Put safeguards into your programs to monitor your use of memory.

* Try to '''run your programs during low-demand times of da'''y (mornings are best; late evenings are the most busy.)

* Try '''not to tie up the computer's resources for longe'''r than the program needs to run.

:: '''Do not forget that you are running programs.''' One of the biggest areas we've had issues with is that some users start their programs in the background and forget that the programs are still running. And in some cases, the programs have issues and start using more resources than actually needed.

::'''Therefore... ''please make sure you check in on your running programs often, and use monitoring tools to make sure you are not exceeding resources.'''''

==Monitoring Your Processes' Memory and CPU Usage with Linux Commands==
:Use the '''top''' or '''htop''' programs to see your program's stats.
:* '''top'''
:** top -u ''username''
:* '''htop'''
:** htop -u ''username''
:** htop --user=''username''
:* '''ps'''
:** ps -u ''username''

==Ending or Modifying Your Running Process Using Linux Commands==

===Ending a Process===

:* '''kill''' - Send a signal to a process, usually to stop the process from running (which is why it's named "kill")
:** First, determine process ID (PID)
:** Start by sending the HUP [https://www.tecmint.com/how-to-kill-a-process-in-linux signal]
:*** Example: Kill process with PID 15476 using signal HUP:
:**** <code>kill -HUP 15476</code>
:** If the process is still running, use the TERM signal. (This is the default signal if one is not specified.)
:*** e.g.: <code>kill -TERM ''15476''</code>
:** If the process is ''still'' running, use the KILL signal. This forces the process to exit, without allowing it to clean up after itself, so it's recommended only of the other two signals don't have an effect. (Some online references refer to "<code>kill -9</code>"; that the same as "<code>kill -KILL</code>".)
:*** e.g.: <code>kill -KILL ''15476''</code>

:* '''pkill''' - send a signal to ''all'' processes that match the given criteria.
:** As with <code>kill</code>, you can choose from the HUP, TERM, and KILL signals. For <code>pkill</code>, it's often easiest to just start with the default signal (which is TERM).
:** To signal all of you processes, use the <code>-u</code> parameter along with your account name. (This will end ''all'' of your processes, including the shell you're using to run it.)
:*** e.g.: <code>pkill -u ''username''</code>

:* From within '''top''' command
:** Find desired process ID (PID)
:** press '''k''' (for ''kill'')
:** enter PID at prompt.
:** enter signal number to use (as with <code>kill</code> above, it often works best to try 1 (HUP) first, then 15 (TERM), followed by 9 (KILL).

===Modifying a Process's Running Priority===

Every process on our systems has a priority, which defaults to 0, signifying a neutral priority. Higher numbers, up to 20, represent ''lower'' priorities; the programs are being "nice" and allowing other programs to run more often. A priority of 10 is twice as nice as a priority of 5, and half as nice as a priority of 20. (Negative numbers, from -1 down to -20, represent very ''high'' priorities and are reserved for system processes.)

To ''change'' a process' priority, use the '''<code>renice</code>''' command:

<kbd>renice <var>priority</var> <var>pid</var></kbd>

:"<var>priority</var>" gives the new priority for the process, from 1 to 20. Note that ''you can only ever raise the priority number''; once a process is at, say, 10, you can raise it to 15 but you cannot lower it to 5.

:"<var>pid</var>" is the process ID for your process. You can get that from <code>top</code> or <code>ps</code>, [[#Monitoring Your Processes' Memory and CPU Usage with Linux Commands|as described above]].

To set a process' priority ''when you start it'', use the '''<code>nice</code>''' command:

<kbd>nice <var>your program ...</var></kbd>
<kbd>nice -n <var>priority</var> <var>your program ...</var></kbd>

If you don't give a priority via the <code>-n</code> parameter, it defaults to a priority of 10.

==And, Worth Mentioning Again...==
: Please remember that because these are multiuser systems, ''other users could be logged into the system and could be affected if your running program exceeds the computer's resources.''

[[Category:Linux Clients]]
[[Category:Computers Available on the CS Network]]
[[Category:Troubleshooting]]

Overleaf Software Licensing

2024-06-07T14:35:00Z

Phil:

[https://www.overleaf.com Overleaf] is a web-based online text editor based upon [https://www.latex-project.org LaTex]. WSE is now able to provide a ''WSE-wide'' site license for the software. Those in WSE that are already paying license fees on their own should be able to switch over to WSE's license.

Overleaf's JHU page to request a license can be found at [https://www.overleaf.com/edu/jhu https://www.overleaf.com/edu/jhu]

You can also visit [https://software.wse.jhu.edu/apps/software.cgi?selection=bySpecificTitle&name=Overleaf WSE's page that references Overleaf] {{red|'''NOTE:''' You must either be connected to the JHU VPN or be connected directly to a JHU network to access this page.}}

==Licensing Notes==

* New users who sign up for Overleaf using their JHU email address will be prompted to confirm their affiliation through the SSO login page.

* Existing users with a JHU email address will be encouraged to log in through the SSO. For entitled users from the Whiting School of Engineering that already have a paid Overleaf subscription, they will also see a notification in their dashboard letting them know that they have access to this subscription and can cancel their personal subscription.

Any questions about the license or problems with obtaining a license should be directed to [mailto:wsehelp@jhu.edu wsehelp@jhu.edu]

[[Category:Software]]

Obtaining CS MySQL Accounts

2024-06-07T14:34:33Z

Phil:

:
:This is for access to the department's '''general use''' MySQL server, '''''mysql.cs.jhu.edu'''''

::'''NOTE''': '''If you are a student of ''the CS-offered Database class,'' you will need to get [[CS_Database_Class_(315/415/615)_Information | a different MySQL account for the course database server (called ''dbase.cs.jhu.edu'')]] from your TA.'''

{{messagebox|'''CS Linux Account Required:''' Only those with [[Obtaining_CS_Computer_Accounts|CS Linux accounts]] will be able to apply for a [[Obtaining_CS_MySQL_Accounts|MySQL account]] for our '''mysql.cs.jhu.edu''' server.|type=warning}}

* For MySQL-based access to our MySQL server, ''mysql.cs.jhu.edu'', please fill out a MySQL Account Form which can be downloaded from the [[Forms#Apply for a MySQL Account on the CS Dept's Main MySQL Server | CS forms webpage]]



* When your MySQL account is created (which will have the same username as your CS Linux account), a default database will be created for you, and that ''database name will be '''the same''' as your MySQL account name.''

* Later, if you need an ''additional'' database set up at some point for your MySQL account, send an email to {{mailto|support}} letting us know your MySQL username and the ''proposed'' name of your database.

==Submitting the CS MySQL Form==
:Please '''scan the completed form into a pdf.''' Then, e-mail it to {{mailto|support}}

::{{red|'''''IMPORTANT!''''' When you email the account form to us, please have the '''''Subject Line''''' include ''"CS MySQL Account Form"'' followed by ''your name''}}

::'''NOTE:''' If you don't have a scanner, you can always use an app like ''camscanner'' on Android and iPhone or [https://support.apple.com/en-us/HT210336 ''Notes app''] on iPhone. And if those options do not work, then, snap a clear picture of the filled-out form and email it to us.


:Please allow 2-3 business days for your MySQL form to be processed. Steve DeBlasio will then email you when your MySQL database is ready.

::{{red|'''BE AWARE: If you are expecting e-mail from the CS IT Support team, and if you use [http://www.gmail.com Gmail], make sure you check your Gmail Junk folder. Gmail likes to file some e-mails from CS into Gmail Junk folders.''' }}

==Once You Receive Your MySQL account==

:Once you receive your MySQL account, please return to [[Dept. MySQL Server]] for info on accessing the server.

[[Category:Accounts]]
[[Category:MySQL]]

Obtaining CS Computer Accounts

2024-06-07T14:33:28Z

Phil:

:{{red|CS IT will handle many computer account issues now '''remotely''', via email (never send passwords through email, though!) or Zoom. So, please make sure you have [https://support.cs.jhu.edu/wiki/Zoom Zoom] installed on your computer or mobile device. And, plan to have your J-Card in-hand. (If no J-Card, you'll at least need a picture ID.) If you have any questions, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] }}



A CS Linux account provides:

:* A Linux shell and disk space for ''course work'' and ''light research''.

:* A CS-based [[:Category:Mail | email address]].

:* Directory space to [[:Category:Webpages_and_Webservices | host a webpage]].

'''''NOTES:'''''
* A CS Linux account ''is not'' related to a JHED account. (JHED accounts are part of JHU's own accounts system.)

* The [[Linux_Clients_on_the_CS_Grad/Research_Net | CS ''Grad Net'' Linux client computers]] and [[Linux_Clients_on_the_CS_Undergrad_Net | ''Ugrad Net'' Linux client computers]] are similar in terms of the software/applications installed, ''but they use '''separate''' user accounts. ''


 
Below, you'll see the process to obtain a CS ''Linux'' account for access to the [[:Category:Computers_Available_on_the_CS_Network|Computers Available on the CS Network]].

==Obtaining The CS Account Form==



You can download a copy of the [https://www.cs.jhu.edu/formfiles/newacctform.pdf CS Linux/Windows Account Form] from our [[Forms]] page.

Once you've downloaded it, come back to this page for further instructions.

 

==Filling Out The CS Account Form==




Please print and fill out the form '''''COMPLETELY''''', and '''sign both sides of the form'''. ''Please be legible.''

(Some of you might edit the PDF directly, but you still need to sign both sides of the form before submitting the form.)

You then need to obtain any [[#Signatures|authorized signatures]]. {{red|(Please see our updates to obtaining signatures in that section below.)}}

Additionally, make sure you list your [http://www.it.johnshopkins.edu/services/email JHU-assigned e-mail address] on the account form. Many of our CS mailing lists use that address.

There is a section there for ''Permanent (non-JHU/non-CS) Email Address''. Please fill that in. Note: If you will not be accessing your CS email directly, we encourage you then to [https://support.cs.jhu.edu/wiki/Forwarding_Mail forward] your CS email to an address you do check frequently (whichever is your preferred email address... it could be your permanent email address or your @jhu.edu email address) so that you do not miss any emails that may be sent to your @cs.jhu.edu email address. 

Under “Local Address”, please list your local resident street address while attending (or working at) JHU. 

 

===Indicating Your JHU Affiliation Type===

The CS Account form requires you to choose your JHU affiliation.

===== Grad Student, Faculty/Instructor, Staff, Researchers, or Postdoc CS Computer Accounts =====
:On the CS Linux/Windows Account Form, if you're a ''CS Grad student'' or ''CS Faculty/Instructor'', ''Staff'', ''Researcher'' or ''Postdoc'', please make sure you've checked off that you want a '''Linux Grad''' account, which will supply you with your CS e-mail address and an account to access the [[Linux Clients on the CS Grad/Research Net|Grad/Research Net Linux]] computers that are supported by CS IT (including the Linux computers in the Master's Lab).

:If you are teaching or TA'ing a CS Undergrad Course, and, as a result, also '''''require''''' a CS Ugrad account for yourself, you can check off '''Ugrad Linux'''. But, if you do end up needing a Ugrad account, please realize that your CS Grad/Research Net account is your primary account (email, webpage, etc.) And, the Undergrad Net machines are subject to [[Disk Quotas|disk quotas]].

:''CS Grad students'' (PhD and Masters) should also indicate their expected graduation year on the form next to their student affiliation.

:''CS Staff members:'' In addition to checking off the Linux box you should also check off the ''Windows'' box at the top.

:'''''If you already have a''''' '''Grad/Research''' Linux account, and then ''later'' '''''require''''' a '''Ugrad''' Linux account (TA'ing a Ugrad course, for instance), please fill out the form again indicating which other accounts you need,  You'll fill in your current username after the '''''"Already have a CS acct..."''''' line on the form. (It might be helpful to write something along the top of the form indicating "Requesting an additional account.")

:'''''If you already have a''''' '''Ugrad''' Linux account, and then later, become part of the CS Graduate program (Masters or PhD) and are applying for a Grad Linux account (which is probably why you're reading this section now), please fill out the form again indicating which other accounts you need, You'll fill in your current username after the "Already have a CS acct..." line on the form. (It might be helpful to write something along the top of the form indicating "Requesting an additional account.") However, if you do get a CS Grad/Research Net Linux account, your CS Ugrad Net e-mail will no longer be in service (although, you will have access to your old e-mail). You would now have CS Grad/Research Net mail. If you're receiving a Grad account, you should move your Ugrad files over to your new Grad account and let us know, so that we can remove your Ugrad account.

===== CS Undergrad/CS Minor Student Accounts =====
:If you are a ''CS Undergraduate student'' or ''CS Minor student'', you will need a CS Undergrad Account to access the [[Linux Clients on the CS Undergrad Net|Undergrad Net Linux]] computers.


: CS Undergrad/Minor students should also indicate their expected graduation year on the form next to their student affiliation.

:'''''If you already have a''''' '''Ugrad''' Linux account, and then later, become part of the CS Graduate program and would need a '''Grad''' Linux account, please fill out the form again indicating which other accounts you need,  You'll fill in your current username after the '''''"Already have a CS acct..."''''' line on the form. (It might be helpful to write something along the top of the form indicating "Requesting an additional account.") However, if you do get a ''CS '''Grad/Research''' Net'' Linux account, your ''CS '''Ugrad''' Net'' ''e-mail'' will no longer be in service (although, you will have access to your old e-mail). You would now have ''CS Grad/Research Net'' mail. If you're receiving a Grad account, you should move your Ugrad files over to your new Grad account and let us know, so that we can remove your Ugrad account.

:Note: CS Linux  machines have [[Disk Quotas|disk quotas]]. Please remove files you no longer need on your account after you are finished with them.

===== Class/Course Accounts =====
:If you are provided a ''class account by your instructor, or if you apply for one yourself'', please note that class accounts are up for removal after the semester is complete.

:'''''If you already only have a''''' '''CS class account''', but have entered into the CS Undergrad program, you are eligible to obtain a '''CS Ugrad''' Linux account, To do so, fill out the CS Account Form again from scratch, but this time, follow the section above for CS Undergrad/Minor students.. (But, do indicate somewhere along the top that you had been using a class account and what that account is.)

:Note: CS Linux  machines have [[Disk Quotas|disk quotas]]. Please remove files you no longer need on your account after you are finished with them.

===== Concurrent Students =====

:If you start as a ''CS Concurrent Student'' (grad/ugrad at the same time) or if you were already a CS Ugrad student with a CS Ugrad account and become a Grad student, please make arrangements with CS IT Support to obtain a ''CS Grad/Research Net'' Linux account, if you'd like. However, if you do get a ''CS '''Grad/Research''' Net'' Linux account, your ''CS '''Ugrad''' Net'' ''e-mail'' will no longer be in service (although, you will have access to your old e-mail). You would now have ''CS Grad/Research Net'' mail. Your CS Ugrad account, however, will remain while you have a Grad account, until you graduate.

===== Other =====

:If you're not sure you fit into one of the listed categories on the form, ''for example "research scientist"'', please choose "Other" and specify your position within JHU, and a reason you need the account, if applicable. You will still need to get an [[#Signatures| authorized signature]] on your form.
 

=== Choosing your CS Account Username ===

:{{red|'''NOTE:''' We do '''not''' change CS usernames/accounts once created.}}

:'''''CS Faculty, Instructors, Staff, Post Docs, Researchers, and some others:''''' You can generally request your own username. You should request up to three possible usernames, and we will use what we can, depending upon what's available. However, we highly recommend you choose to make your CS account username the same as your JHED ID.

:'''''CS Ugrad, Masters, and PhD Students:''''' A CS username will be assigned to you, based upon your current JHED ID.

:'''''Non-CS students taking a CS Course:''''' We will assign you a special course-based username for your CS course account. ''That course account will only be valid the semester the course is taught and will be removed upon course completion.''

:'''''Others:''''' When in doubt, your can choose to request us to use your JHED ID username as your CS username too.
 

== Signatures ==

We require '''at least two''' and up to '''three''' signatures on each account form.
*You will sign the '''front''' of the form ''and'' read and sign the '''back''' of the form.
*Several of you will also need to obtain an '''authorized signature''' as appropriate (and as described on the form.) {{red| But, read below for changes in this policy.}}

{{red|'''UPDATE:''' In recent years, we had made some changes regarding signatures, and those changes are still in place... Instead of you having to obtain the authorized signatures on the form, in several cases (for example, students), we will take care of that for you. Please see below for details. '''''(So, all you need to do is fill out the form, make sure you sign both sides, ''read the section below about any signatures needed'', obtain any required signatures, per below, and then [[#Submitting The Account Form| submit the form to us]].)''''' }}

* ''CS Grad (Masters & PhD) students:'' You ''do '''not''' need'' an authorized signature. We will obtain any approvals for your account from CS Admin staff. Just make sure '''you''' sign the front and back in the appropriate spots. 

* ''CS Undergrads/CS Minors:'' You ''do '''not''' need'' an authorized signature. We will obtain any approvals for your account from CS Admin staff. Just make sure '''you''' sign the front and back in the appropriate spots.  

* ''CE (Computer Engineering) students:'' You ''do '''not''' need'' an authorized signature. We will obtain any approvals for your account from CS Admin staff. Just make sure '''you''' sign the front and back in the appropriate spots.

* ''Non-CS student taking a CS class:'' Until further notice, you do '''not''' need your CS professor (CS Faculty/CS Instructor) to sign the form. '''Your account will last for the semester.'''  {{red| '''NOTE:''' }} Under the Non-CS Student section, if you're taking a CS course and you list your Course name and #, in that same section, '''please also list your CS professor's name''' as well. This will speed up processing.

* ''New CS faculty/instructors/staff:'' Please get '''Laura Graham''' or the '''CS Dept. Chair''' to sign your account form. 

* ''Postdocs, visiting faculty, or research scientists, etc.:'' Please have a '''CS Faculty Member''' (or possibly, '''Laura Graham''') sign the form. 

* ''Students from other depts that are not associated with CS who are requesting a CS account on our system:'' You must have a [https://www.cs.jhu.edu/faculty ''CS Faculty''] member sign the account form. That CS Faculty member is sponsoring your account. If you're an undergrad student, you would have access to our ''CS Ugrad Network'' systems. If you're a grad student, you would have access to our ''CS Grad Network'' systems. {{red|We will attempt to obtain this approval for you, however, you need to indicate somewhere on the form '''which''' [https://www.cs.jhu.edu/faculty CS faculty] member will sponsor your account. You do may need an authorized signature, as long as we are able to obtain any approvals for your account. Just make sure '''you''' sign the front ''and'' back in the appropriate spots for your account. If you choose to gather the authorized faculty signature yourself by sending your filled-out/signed form to the faculty member to sign, then please have that faculty member scan and email the completed form to [mailto:support@cs.jhu.edu support@cs.jhu.edu]), that will speed up processing.}}

If you have any issues regarding signatures, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] to discuss alternatives.



 

==Submitting The Account Form==




*First, make sure you ''signed'' '''both''' sides of the form. Also, if you need to, obtain any [[#Signatures|authorized signatures]]



* Please '''scan both sides ''into a single'' pdf.''' Then, attach the pdf to an email and send that to [mailto:support@cs.jhu.edu support@cs.jhu.edu]
:::{{red|'''''IMPORTANT!''''' When you email the account form to us, please have the '''''Subject Line''''' include '''''your name''''' and the words '''''"CS Account Form"''''}}

::'''NOTE:''' If you don't have a scanner, you can always use an app like [https://www.camscanner.com CamScanner] on Android and iPhone or [https://support.apple.com/en-us/HT210336 Notes app] on iPhone. As a last resort, you can ''neatly'' take a photo of both sides of the form.





== Processing your CS Account Form And Receiving Your CS Account==



'''''Please allow at least 2-3 business days for your account to be created, as we have to obtain the authorized approval.'''''

* After your account is created, you will be contacted ''via e-mail'' at one of the e-mail addresses you listed on the form (so, check all of them) by [mailto:steve@cs.jhu.edu Steve DeBlasio]. He will send you instructions for pick-up of the account information, which will now be done remotely.
::{{red|'''BE AWARE: If you are expecting e-mail from the CS IT Support team, and if you use [http://www.gmail.com Gmail], make sure you check your Gmail Junk folder. Gmail likes to file some e-mails from CS into Gmail Junk folders.''' }}

* {{red|For remote account pick-up, as mentioned above, Steve DeBlasio will provide you instructions. He will meet with you over [https://support.cs.jhu.edu/wiki/Zoom Zoom] Please make sure you have Zoom installed on your computer or mobile device. And, you will need to have your J-Card (or other picture ID if you do not have a J-Card) in-hand, as he will need to see it when you meet with Steve via Zoom.}}




==''Do Not'' Share Your CS Password!==
:Please don't share your CS account password with anyone. No one else ever needs to know your account password, not even CS IT Support. If you're requesting information about an account, you can just give the account name; that's enough for authorized people to look up information about the account. Sharing the password with other people is potentially a security risk.

:Even if you think the person you're contacting is trustworthy, since they should never need your password, it's good practice to never send it (not even via email or text.) That makes it impossible to accidentally send it to the wrong person, among other things.

==And finally...==

If you have any problems filling out the account forms or have not received notice that your account is ready in a reasonable amount of time (at least 2 ''business days'' after submitting the form), please email [mailto:support@cs.jhu.edu support@cs.jhu.edu].

[[Category:Accounts]]

Multi-Factor Authentication - JHU

2024-06-07T14:29:38Z

Phil:

==INTRO==

:JHU IT now has new authentication security protection measures in place for several of their central services in the form of [https://it.johnshopkins.edu/services/directoryservices/jhea/AzureMFA/AzureLoginMFA '''M'''ulti-'''f'''actor '''A'''uthentication (MFA)].

:For example, both your online JHU W2 and Employee Self Service (ESS) in MyJH use it. The [[VPN - JHU|JHU VPN]] system from JHU requires MFA as well. ("Two factor authentication" is a type of MFA you might have heard of before.) We will see more and more JHU sites/services requiring MFA, and you will need to configure your MFA access.

:JHU uses ''Microsoft Azure'' for providing JHU's Multi Factor Authentication service.

==Details About The JHU Multi Factor Enrollment And Use Process==

:For more details on JHU's implementation of MFA and and instructions on how to configure and use it, please visit WSE IT's documentation on the subject at:

::[http://wseit.engineering.jhu.edu/get-help/multi-factor-authentication http://wseit.engineering.jhu.edu/get-help/multi-factor-authentication]

:JHU's Azure MFA page to enroll or manage your MFA configuration can be found at:

:: [https://it.johnshopkins.edu/services/directoryservices/jhea/AzureMFA/AzureLoginMFA https://it.johnshopkins.edu/services/directoryservices/jhea/AzureMFA/AzureLoginMFA]




:'''Also,''' we will outline the basic steps to set up MFA directly below...

== Setting Up Multi-Factor Authentication==



:To get started with MFA, you will need to visit the Azure MFA Resource Center's '''''[https://t.jh.edu/mfa Enrollment Page]''''' to enroll. 

:That page and its video will show you how to enroll your JHED ID with the Azure MFA. The video is very helpful in explaining the process. You are encouraged to watch it all the way through.

===Authenticators===

:As part of the MFA setup process, you will end up having to choose an '''authenticator''' method to use. There are several authenticator methods:

* '''Text your phone for approval to connect to the website.''' Called Push-To-Approve, your phone would receive a text from the secured JHU website asking you to approve the connection. You would use the Microsoft Authenticator app to respond to that prompt. {{red|As of Fall, 2022 (estimated November 16, 2022), JHU is removing the method that some users have used, called '''''"Notify me through App (Push to Approve)"''''', where JHU would text you to ''approve'' the connection access. Instead, you will need to use one of the below methods, where you'll need to enter a numerical authentication code (what JHU calls, ''Number Match''.)}}

* '''Text your phone for a numerical code:''' {{red| Being implemented Fall, 2022}} When JHU needs you to enter your MFA code during login to JHU's MFA-required pages/apps, they will text your phone with the MFA code that you will use to enter into whatever prompt they send you. You ''may'' need to do this via a Microsoft Authenticator app you'd run on your device. This is called the "Number Match" method.

* '''Use an app/program:''' {{red|This method will continue to remain}} With this method, ''you are not texted by the website.'' Instead, the website will prompt you to enter a code. On an authenticator app you'd install on your phone or computer, you would run the authenticator app, and that will provide a 6-digit number code to enter when you are prompted at JHU for your MFA code. JHU suggests you use the Microsoft Authenticator App (for Windows) to generate that numerical code. You can download Microsoft Authenticator according to instructions from the enrollment process video. Additionally, you can choose to run other authenticators to run (under Windows) instead, including a program called WinAuth. Macs, Androids and IPhones have various authenticators available as well. Note that the codes are generated using time-based factors... so, the code you generate needs to be entered soon (up to a minute) when you are prompted, otherwise, you need to generate another code.

:

==Adding An MFA Authentication Method Or Changing Your Default MFA Authentication Method==

:Once you have your MFA set up... By default, the MFA authentication process seems to make texting your phone the way JHU provides you your MFA code. Some users might want to change this from ''receiving a text from JHU'' to using an ''authenticator app'' (e.g., WinAuth on PC or a similar app on a phone, for instance, as described above) instead.

:* To change your default authentication method, simply log into [https://mysignins.microsoft.com/security-info https://mysignins.microsoft.com/security-info] ''Once logged in, if you're not directed directly to the Security Info page, simply click '''Security info''' on the left.'' You'll see a list of your authentication options, and you can change the default option to using a Hardware Token (Authenticator App) instead of the Phone (text) option.

:* It is also recommended to add an additional authentication method -- should your phone (or your app) be unavailable, you will have an alternative method with which to authenticate with MFA. To '''add a new/additional''' authentication method, again log into [https://mysignins.microsoft.com/security-info https://mysignins.microsoft.com/security-info] ''(and click Security info on the left, if needed)'' and choose ''Add method'' (it is preceded by a blue plus sign.)

{{red|'''NOTE:''' If you have any issues with setting up Multi-factor authentication, ''you should contact'' [[Contacting_JHU_IT_Support | JHU IT Support]].}}

[[Category:Security]]

Matlab

2024-06-07T14:28:42Z

Phil:

==Running MATLAB in the CS Computing Labs==

'''[https://www.mathworks.com/products/matlab.html MATLAB]''' is available on the '''Linux''' machines in both the MH 122 Ugrad Lab/Collaboration Room and the G61 Masters/Ugrad Lab. MATLAB is also available on the dept's compute servers (gradx, gradz, ugradx, ugradz.)

While seated at one of the Linux machines in the CS Labs (or ssh'd into one of those systems or the compute servers), open a terminal (shell) and run <code>matlab &</code>

== MATLAB Personal Licenses ==

Students have been inquiring regarding licenses for MATLAB.

:{{red|'''NOTE:''' The CS Dept's IT group '''''does not''''' provide personal licenses for MATLAB.}}

The Whiting School of Engineering (WSE) now provides licenses that can be used on JHU-owned ''or'' personal machines. Please see: [https://software.wse.jhu.edu/siteauth/apps/software.cgi?selection=bySpecificTitle&name=Matlab https://software.wse.jhu.edu/siteauth/apps/software.cgi?selection=bySpecificTitle&name=Matlab] '''NOTE: You must be on the JHU network or be connected via the JHU VPN to access that page.''' and you might be prompted to log in with your JHED ID to access that page.

If you have questions regarding obtaining personal MATLAB licenses, please contact WSE's IT at [mailto:wsehelp@jhu.edu wsehelp@jhu.edu] or JHU's software group at [mailto:software@jhu.edu software@jhu.edu]



[[Category:Software]]
[[Category:Obtaining Software For Your Own Or Research Lab Computer]]
[[Category:Software Available On The CS Linux Clients]]

Malone G29 Server Room

2024-06-07T14:28:19Z

Phil:

The Computer Science Department has a server room in Malone Hall Room G29. This page is for CS faculty/researchers who have already been allocated space in that room or want to request space in the room. It also describes how to make the best use of your space allocation.

Please read the below sections first. Then, if you would like your server hosted in our server room or have questions that are not answered here or need to make arrangements with us if you've been allocated space in the server room, please email us at [mailto:support@cs.jhu.edu support@cs.jhu.edu].

== Services Provided (and Not Provided) by CS IT Staff ==

=== Things We Will Do for You ===

CS IT will:

* Provide you and your designees J-Card access to the room
* Provide you up to two '''1-gigabit''' network connections for your rack
* Provide you access to the floor power
* Add you to a ''Malone server room mailing list'' for server room-related announcements, etc.
** (However, you should continue to check the CS IT Support Wiki [[Notices]] page if you experience issues such as network, etc. that could be affecting your systems in the server room.)

=== Things You Will Need to Do Yourself ===

CS IT will ''not'':

* Install your systems on your rack
* Make network or power connections to your systems on your rack
* Administer your systems

:{{red|'''NOTE:''' CS IT Support does not administer research systems. Please see our [https://support.cs.jhu.edu/wiki/Services_Provided_By_CS_IT Scope Of Services] and [https://support.cs.jhu.edu/wiki/Category:Research_Computing Research Computing] pages for more details.}}

== Physical Space ==

Each rack is labeled with a letter and number. If we assign you a rack, we will provide you the rack letter/number combo.

'''NOTE:''' Previously racks were labeled for the faculty member responsible for the equipment in that rack. As of 2024, racks are being converted to shared racks, shared by faculty members/researchers.

== Airflow/Cooling ==

The server room is set up in a ''"hot aisle/cold aisle"'' configuration. The front of each rack, which is the end with the single, wider door, faces a "cold aisle". The cold aisles are also marked by perforations in the floor tiles. Cold air from the air conditioning units enters the aisles through these perforations. The back of each rack faces a "hot aisle", which does not have perforated floor tiles.

When installing equipment in your rack, ''you should orient the equipment so that the fans pull air in from the cold aisle and exhaust air out to the hot aisle.'' This ensures good cooling efficiency for the entire room. Equipment installed backwards may overheat and may cause adjacent equipment to also overheat.

== Networking ==

We can provide up to two network connections to each rack. You will need to [mailto:support@cs.jhu.edu email us] to request the connections. If you will be using CS Department IP addresses, you will also need to follow [[Requesting a Static IP Address on the CS Network|our procedure for requesting a static IP address]].

If you will have more than two devices connected to the network on your rack, you will need to procure your own network switch (or switches) and install it (or them) in your rack.

Our network connections are '''1-gigabit''' ethernet running over RJ-45 terminated copper cables. If you need other accommodations, please contact us and we'll see what arrangements we can make.

== Access to the Server Room ==

Server room access is controlled by J-Card. In order to grant someone access, the faculty owner of the rack space should [mailto:support@cs.jhu.edu email us] and request it. The request needs to contain the name and JHED ID of the person who should be granted access, as well as an estimate of how long you expect the person to be using the room.

== Other Notes ==

The server room is fairly loud. If you want to use ear protection while you're working there, you can use one of the headsets that are hanging on the wall all the way to the right after you enter the room. Please return the headsets to their hangers when you're done with them.

'''''Please turn the server room lights off when you're done in the room.'''''

[[Category:Malone Hall]]
[[Category:Misc]]
[[Category:Research Computing]]

MH 122 Projectors

2024-06-07T14:27:18Z

Phil:

The undergrad lab/collaboration room in Malone Hall room 122 has various projectors available for presentation use:

* A ''ceiling mounted projector'' in the main room is connected to the ''ugrad1'' lab machine and has an HDMI connector on top of the ugrad1/ugrad2 table for use with laptops.

* ''"Short-throw" projectors'' in each of the three small breakout rooms have connectors to be used with laptops. The wall closest to each breakout room projector acts as the screen.

The main room projector is controlled from the '''small Crestron control panel''' ''on the ugrad1/ugrad2 collaboration table''.

{{red| '''NOTE:''' When you are done using any of the projectors for your session, ''please remember to shut them down afterwards''. If you were using the main room projector, please also raise the screen.}}

== Using the Main Projector With The ugrad1 Linux Lab Computer ==

There is a '''small ''Crestron'' control panel''' on the collaboration table next to '''''ugrad1's''''' monitor.

* Lower the projector screen.
** Press the down arrow on the screen control panel, which is on the wall below the clock.

* Activate the projector.
** If the projector is off, touch the power icon on the right border of the tabletop control panel to turn it on. The green power LED on the projector will begin blinking.

* Send ugrad1's video output to the projector.
** On the control panel, touch the computer icon in the lower lefthand corner (right next to the home icon).
** Touch the "Linux PC" button.

* {{red| '''IMPORTANT!''' When you're done with the projector, please '''''shut it down''''' by pressing the power symbol button on the right border of the Crestron control panel to ''shut down the projector'', then press the up arrow on the screen control panel to ''raise the screen.'' }}

=== Video Configuration ===

The ugrad1 lab machine ''defaults to a side-by-side configuration'' for the monitor and projector. You can move windows to the projector by dragging them off the left side of the monitor screen.

In some cases, it may be more convenient to have the projector function as a ''mirror'' of the monitor. To activate this with the default login environment (Mate Desktop):

:* Go to the ''"System"'' menu at the top of the screen.
:* Open the ''"Preferences"'' submenu.
:* Open the ''"Hardware"'' submenu.
:* Click on the ''"Displays"'' entry.
:* In the ''"Monitor Preferences"'' window that opens, check the checkbox labeled ''"Same image in all monitors"''.
:* Click the ''"Apply"'' button.
:* In the ''"Does the display look OK?"'' dialog box that comes up, click the "Keep This Configuration" button.

If you make changes to the monitor and projector layout, those changes will be remembered and reapplied every time you log into ugrad1.

=== Audio Configuration ===

The audio for ugrad1 can be directed through the room's speaker systems, but it is not set to do that by default. Here's how to set it up:

:* From the ''"Applications"'' menu, go to ''"Sound & Video"'' and start ''"PulseAudio Volume Control"''.
:* Go to the ''"Configuration"'' tab.
:* For the ''"GK106 HDMI Audio Controller"'' device, select the ''"Digital Stereo (HDMI 3) Output"'' profile. It should be the only one that is not ''"Unplugged"''.
:* To make all sounds go through the room's speakers:
:** Go to the ''"Output Devices"'' tab, find the '''HDMI''' controller and click its button with a checkmark in a green circle. (The tooltip for the button is ''"Set as fallback"''.
:* If you only want one program to use the room's speakers (e.g. a video playback program):
:** Start that program.
:** Go to the ''"Playback"'' tab in the '''PulseAudio Volume Control program''', find your program in the list and ''change its playback device to the HDMI output.''

 

== Using the Main Projector with a Laptop ==

* Lower the projector screen.
** Press the down arrow on the screen control panel, which is on the wall below the clock.

* Plug your laptop into the HDMI cable on top of the table closest to the printer.
** If you only have DisplayPort, DVI, or VGA connectors on your laptop, you'll need an adapter.

* Activate the projector.
** If the projector is off, touch the power icon on the right border of the tabletop control panel to turn it on. The green power LED on the projector will begin blinking.

* Send your laptop's video output to the projector.
** On the control panel, touch the computer icon in the lower lefthand corner (right next to the home icon).
** Touch the "HDMI" button.

* At this point you may configure the projector as a second monitor on your laptop. It will probably appear as a monitor named ''"Crestron Electronics, Inc 36"''.

* {{red| '''IMPORTANT!''' When you're done with the projector, please '''''shut it down''''' by pressing the power symbol button on the right border of the Crestron control panel to ''shut down the projector'', then press the up arrow on the screen control panel to ''raise the screen.'' }}

 

== Using the Breakout Room Projectors ==

Each breakout room has VGA and HDMI connectors on the wall. There are also audio jacks to be used in conjunction with the VGA connectors.

* Connect your laptop to either the HDMI or VGA connector.
* Press the appropriate button on the input selection panel to the left of the connectors.

* {{red| '''IMPORTANT!''' When you're done, please press the '''''"PWR OFF"''''' button on the input selection panel ''to turn off the projector''. }}

[[Category:Labs]]
[[Category:Audio-Visual]]

Linux Clients on the CS Undergrad Net

2024-06-07T14:26:22Z

Phil:

The following is a list of Linux machines available for students, faculty, researchers, or staff. These Linux machines can be accessed remotely via [[Connecting to CS Systems with SSH|<code>ssh</code>]], <code>scp</code> or [[VNC]].

If you're working remotely, although you are welcome to log into '''''any''''' of our Linux clients, it's recommended that you try ''ugradx.cs.jhu.edu'' first, as it can handle more concurrent use than any of the lab machines. All of the systems are identically configured, however, so ''anything you can do on one of them can be done on all of the others'', too.

===NOTES===

:* All Ugrad Net systems end with '''''.cs.jhu.edu''''' as in, '''''ugrad1.cs.jhu.edu'''''

:* [[:Category:Accounts|Accounts]], [[:Category:Mail|mail]], [[:Category:Webpages_and_Webservices|web]], and home directories on the Ugrad Net machines ''are different than'' those on the [[Linux Clients on the CS Grad/Research Net|Grad]] systems.

:* Ugrad Net linux clients have [[Disk Quotas|disk quotas]] on the Ugrad home directories.

:* If you are unable to reach one of the systems below, please first see if it is part of an outage by visiting our [[Notices|''Notices'' page]], otherwise, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

:* '''These Linux clients are primarily used for ''educational (coursework)'' purposes.''' Therefore, since you are sharing these systems (CPU, memory, etc.) with other users, please make sure that you do not overload the processors on these systems. When your are completed running your processes, please make sure you stop those processes.

 

==Available Ugrad Linux Systems==

* '''ugrad1''' through '''ugrad24'''
**standard ''Fedora 38'' Linux clients
** split between both [[:Category:Labs|CS Undergraduate Labs (Malone 122 and G61.)]]
** Each client has 8 cores (one 4-core i7 CPU with hyperthreading) and 16 GiB RAM.
** Each system includes an NVIDIA-based GPU that may be used with CUDA and OpenCL (already installed) for coursework.
** ''These systems are also available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers.''
** '''{{red| NOTE: From June 5, 2024 through August 6, 2024, ugrad1 through ugrad12 will only be available remotely, via ssh.}}'''

* '''ugradx'''
**''Fedora 38'' Linux-based compute server.
** 24 cores (two 64-bit 6-core CPUs with hyperthreading), 288 GiB RAM
**''only available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers.''

* '''ugradz'''
** ''Fedora 38'' Linux-based compute server.
** 32 CPU cores, 48 GiB RAM.
** ''Only available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers.''
** Only accessible from the Hopkins network or VPN; not accessible directly from the Internet.

'''ssh key fingerprints''' for these machines can be found on the [[SSH Key Fingerprints for Grad and Ugrad Net Linux Computers]] page

[[Category:Linux Clients]]

Lab And Other Website Hosting

2024-06-07T14:26:00Z

Phil:

==INTRO==

In addition to hosting [[Creating a Webpage|personal webpages]] accessed as <code><nowiki>http://www.cs.jhu.edu</nowiki>/~<var>account</var></code>, we can also host entire websites, with custom URLs (e.g. <code><nowiki>http://</nowiki><var>your-lab-name</var>.cs.jhu.edu</code>).

:'''''This service is only available to CS Faculty.'''''

To request a hosted website, you must decide on a ''website name'' and ''file storage method'' for the website files. Both choices are ''described below''. Then you need to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] with a complete description of your request.

If you choose the [[#Dedicated Website Account|Dedicated Website Account file storage method]] ''described below'', you'll also need to ''print out'', ''fill out'', and ''sign'' a [https://support.cs.jhu.edu/forms/vhost-form.pdf Computer Science Department ''Website'' Account Form].  You can then scan and email it to [mailto:support@cs.jhu.edu support@cs.jhu.edu]

{{red|'''NOTE:''' CS IT does '''not''' create or edit webpage content for users. You are responsible for your own website design and troubleshooting.}}

== Website Name Options ==

This choice governs what URLs people use for accessing your website. There are four options available.

=== www.cs.jhu.edu Subdirectory ===

:Your website name can exist as part of the <code>www.cs.jhu.edu</code> website, e.g. <code>www.cs.jhu.edu/<var>your-lab</var></code>.

=== CS Domain Name ===

:Your website name can exist under the <code>cs.jhu.edu</code> domain, e.g. <code><var>your-lab</var>.cs.jhu.edu</code>.

:If you request this option, we will set it up for you when we set up your website. We will set up SSL access (i.e.''https''://-style URLs) as well.

=== JHU Domain Name ===

:You can also set up a website name within the <code>jhu.edu</code> domain, e.g. <code><var>your-lab</var>.jhu.edu</code>.

:We ''cannot'' set this up for you automatically. If you want this option, we'll put you in contact with the appropriate people who manage the <code>jhu.edu</code> domain; you'll have to request the name from them. Once the hostname is set up for you, we'll set up SSL access (i.e., ''https''://-style URLs) as part of the website.

=== Other Domain Name ===

:Finally, you can use any second-level domain you want to register, e.g. <code><var>your-lab</var>.org</code>.

:If you chose this option, you will be entirely responsible for making and maintaining the domain registration. If you want SSL (https:// URLs), we'll provide you an appropriate Certificate Signing Request, but you will have to obtain the certificate and then send it to us.

== File Storage Method ==

There are ''two'' options for how the website's files will be stored on our systems. Both require CS Linux accounts.

=== Personal Account ===

:The simplest approach is to simply store the website's files under your ''personal'' CS account. In this case, you create a directory to hold the files (e.g. <code>~/<var>my-lab-website</var></code>) and just [mailto:support@cs.jhu.edu email support] to tell us what directory you want to use.

:This approach works best '''if you are the ''only'' person''' who will be managing the files for the website.

=== Dedicated Website Account ===

:Alternately, we can create a special account dedicated to your website. It will have its own home directory for the website's files. You and anyone else who manages the files will be given access to the account's home directory. A CS Grad Net account is required for access; if you or the other people need an account, please see our [[Obtaining CS Computer Accounts]] page.

:For this option, you will need to fill out and sign a [https://support.cs.jhu.edu/forms/vhost-form.pdf website account form].

:This approach is best when '''more than one person needs to be able to manage the website's files''', or when the person managing those files will change over time.

[[Category:Webpages and Webservices]]

JHU IT Security

2024-06-07T14:25:38Z

Phil:

JHU has an IT group that oversees computer security for the university. This page provides links to important resources relevant for maintaining a safe computing environment at JHU, including official policies and available online IT security courses.

==JHU IT's Website==

: You can reach JHU IT by visiting: [https://it.johnshopkins.edu https://it.johnshopkins.edu]

==JHU IT Security Policies==

:JHU has established various policies to ensure acceptable use and security of computing resources within the University. Please visit [https://it.johnshopkins.edu/policies https://it.johnshopkins.edu/policies] for a complete list of these policies. However, we will highlight a few that you should be familiar with.

===General JHU IT Use and Security Policies===

: [https://policies.jhu.edu/?event=render&mid=796&pid=32378&fid=policy_32378.pdf&_=0.785408630212 Acceptable Use and Security of Johns Hopkins Information Technology Resources]

===Protecting Sensitive Information===

:'''Personally Identifiable Information (PII)''' includes birthdates, social security numbers, financial information, plus more.

:JHU has its own policies regarding protecting, storing, and transferring PII. Please visit: [https://policies.jhu.edu/?event=render&mid=769&pid=32368&fid=PII_Policy.pdf&_=0.928234992742 JHU's P''ersonally Identifiable Information (PII)'' Policy]

==WSE IT's Security Update, 2021==

:WSE IT's Director has put together a slideshow presentation discussing various aspects of IT Security at JHU. Among the various topics, it references Personally Identifiable Information, varying IT-related threats to watch out for, IT security breaches, and more. Please take a moment and check out the [[Media:WSE-IT-Security-2021.pdf|slideshow in PDF format.]]

==JHU-Provided IT Security Online Courses==

:{{red|NOTE: The following courses are part of the JHU Learnshare system, and therefore...}}

:{{red|You '''must''' be on the [[VPN_-_JHU | JHU VPN]] or directly on a JHU network in order to access these courses.}}

:[https://lms14.learnshare.com/dashboard/dash.home.aspx?Z=Cvz7rlERBiINCk3kFkMDWtWkTAGCTs%2fZPxff8PHH9jpE3NtAwUrdMyfZVOCTBf2m Course: JHU Electronic Information Security and Data Management]
::'''Highly Recommended!''' A short online course discussing JHU's policies regarding the protection/storage/transfer of '''''Personally Identifiable Information (PII)''''', reporting related IT security issues, protecting yourself from email Phishing, and other JHU IT Security policies. Well worth the 30 minutes allotted. (During the course, it is advantageous to click on the various subsections to learn more, e.g., the sections including: ''Click this book for JH IT rules''. Very quick reads, and very informative.)

:[https://lms14.learnshare.com/dashboard/dash.home.aspx?Z=e1woSTzpuvT32v70VxOHbMM1EDfTfRjm9962YX%2bhg0o659ZEEY3yZoMjvB7%2bZRJO6qT4EPhRSmUyWu%2f8rO3s1KR8Id%2fnuKobtJkEkpYlCV4%3d Course: IT Security for End Users: IT Security Fundamentals]
:: Learn fundamental security concepts as an end user, including general security policies. Course should take less than an hour to complete. Although this course is a bit dated, the general guidelines might be useful. '''NOTE:''' There is a section in this course regarding good password-creation practice. Guidelines for passwords have improved since the time of this course. So, for more current info on creating good passwords, we recommend reviewing our CS IT Support Wiki page on [https://support.cs.jhu.edu/wiki/Password_Requirements Password Requirements]

[[Category:Security]]

Installing WordPress on the main CS Webserver (www.cs.jhu.edu)

2024-06-07T14:24:18Z

Phil:

[https://wordpress.org/ WordPress] is a popular blogging and content management system. This page describes how to set up WordPress in your CS website. (It's really easy!)

This procedure has been tested with WordPress version 3.8. Other versions should work in the same way, but if you run into problems, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.

== Prerequisites ==

* First, you need a MySQL account. Please see the [[Obtaining CS MySQL Accounts]] page for instructions on how to get one.

* You will also need to have a database on the department MySQL server that you can create tables in. If you requested a database when your account was created, that database should be sufficient. If you need a database created or if you're unsure whether you have a database to use, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.

* And finally, make a note of your MySQL account name, password, and the name of the database you will use.

{{red|'''NOTE:''' CS IT does '''not''' create or edit webpage content for users. You are responsible for your own website design and troubleshooting.}}

== Installing WordPress ==

=== Download WordPress ===

Go to https://wordpress.org/download/. Use the button on the right to download the .zip version of WordPress.

If you didn't download the file while using one of our [[:Category:Linux Clients|Linux Clients]], you'll need to transfer the file to one of them with <code>scp</code> or some similar program.

=== Unpack the Download ===

Extract the .zip file into your <tt>~/public_html</tt> directory. If you're at a lab machine, that's as easy as double-clicking on the downloaded file and telling it to extract into your public_html directory. From the command line, you can run the following command:

unzip -d ~/public_html latest.zip

The default location for the WordPress site will be <nowiki>http://</nowiki>www.cs.jhu.edu/~''your-account''/wordpress. If you want it somewhere else, simply put the files somewhere else within your <tt>~/public_html</tt> directory. If you want your home page to be WordPress, move the contents of the <tt>~/public_html/wordpress/</tt> directly into the <tt>~/public_html/</tt> directory. From the command line, this will do it:

mv ~/public_html/wordpress/* ~/public_html/
rmdir ~/public_html/wordpress

=== Configure Database Access ===

In your wordpress directory, rename the <tt>wp-config-sample.php</tt> file to <tt>wp-config.php</tt> .

Edit that file, either by double-clicking on it or by running <code>pico wp-config.php</code> from the command line.

Find the MySQL settings in the file. Enter your MySQL account name, password, and database into the appropriate fields. For <code>DB_HOST</code>, use <code>'mysql.cs.jhu.edu'</code>. That part of the file should look something like this:

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'example');

/** MySQL database username */
define('DB_USER', 'example');

/** MySQL database password */
define('DB_PASSWORD', 's3kr1t');

/** MySQL hostname */
define('DB_HOST', 'mysql.cs.jhu.edu');

Find the section labeled "Authentication Unique Keys and Salts". In your web browser, go to https://api.wordpress.org/secret-key/1.1/salt/, which will generate unique values for each setting for you. Copy the text of that page and paste it into the <code>wp-config.php</code> file, replacing all of the lines that contain "put your unique phrase here".

Save the config file.

=== Secure Your Configuration ===

This part needs to be done from a command line. Open a terminal window and type the following commands:

cd ~/public_html/wordpress
chmod 0600 wp-config.php

(Obviously, if you put your WordPress files somewhere else, change to that directory instead of <tt>~/public_html/wordpress</tt>.)

These commands will make sure that no one but you can read the file with your MySQL password in it.

=== Finish Setting up WordPress ===

Now go to <nowiki>http://</nowiki>www.cs.jhu.edu/~''your-account''/wordpress (or wherever you installed WordPress) in your browser. The page will present you with a form that you must fill out to create a WordPress account for yourself. This account does not have to be the same as your CS account, nor does it have to use the same password. After you submit the data in that form, your site will be set up and ready to go.

[[Category:Webpages and Webservices]]

Hard Drive Recovery

2024-06-07T14:23:46Z

Phil:

If you've experienced a hard drive failure, you might still need to recover your data. Data recovery can be expensive, especially if its due to failed hard drive hardware. If the hardware is still functioning, but the partition is lost/corrupted, that might be a less costly recovery.

We have compiled the following options for drive recovery from WSE's IT Director, as he was compiling info based upon recommendations he received.

If you have questions about any of these, {{red|''please contact the specific companies/groups mentioned below.''}} Please understand that CS IT does not endorse these companies, but are just providing you the information we have received.


:'''NOTE:''' CS IT does '''not''' recover hard drive data for systems not managed by CS IT.

 

==First, A Reminder==

''Backup, backup, backup''. We can't express this enough as a suggestion/reminder. Backup your data regularly.

 

==Drive Failure Recovery (Especially If Drive ''Hardware'' Has Failed)==

:1) One person we had spoken to was very impressed with Drive Savers ([http://www.drivesaversdatarecovery.com http://www.drivesaversdatarecovery.com]) who did a great job on a VIP hard drive.

:2) Here is a fix we had read about for a specific problem with the Seagate 7200.11 drive ([https://sites.google.com/site/seagatefix https://sites.google.com/site/seagatefix])

:3) A recommendation we were provided for Catzen Computer Consulting Corp (PO Box 16228, Baltimore MD, 21210). ''They're already in SAP!''

:4) Another recommendation is for [https://www.ontrack.com/en-us/data-recovery Ontrack] (formerly, Kroll Ontrack.) In one example, another manufacturer couldn't recover, but Ontrack (when it was Kroll Ontrack) was able to.

:5) Another successful experience was with [http://werecoverdata.com http://werecoverdata.com]

:6) DIY recommendations, for example, swapping the circuit boards from a like-working drive to the like-non-working drive.

'''NOTE:'''
:If your failed drive is an external USB hard drive, consider that it might not be the drive itself, but rather, the casing/power supply. Remove the drive from the casing and connect to a dock or directly to a SATA connection.

 

==When Drive Hardware ''Works'', But Partition ''Has Disappeared'' Or ''Become Corrupt''==

:1) Use powered docking stations during diagnostics/troubleshooting with downloadable recovery utilities.

::A suggested dock was [https://www.amazon.com/Sabrent-External-Docking-Station-DS-UB31/dp/B019C5NE8I/ref=sr_1_7?ie=UTF8&qid=1474308663&sr=8-7&keywords=sabrent+usb+3.0+dock https://www.amazon.com/Sabrent-External-Docking-Station-DS-UB31/dp/B019C5NE8I/ref=sr_1_7?ie=UTF8&qid=1474308663&sr=8-7&keywords=sabrent+usb+3.0+dock]

::This is a good option when your ''external'' hard drive's casing/power has failed. Remove the drive from the casing (youtube may have tutorials) and place the drive in the dock. The dock connects to the PC by USB. You should be able to access the drive that way. If the drive data is corrupt, you'll need a drive recovery utility.

:2) An example drive recovery utility: '''TestDisk'''. An IT admin in CS has had experience and success with a drive recovery utility called '''''TestDisk'''''. [http://www.cgsecurity.org/wiki/TestDisk http://www.cgsecurity.org/wiki/TestDisk]

::It is multiplatform and... free!

::And, ''if your drive is encrypted'', and you want to use '''TestDisk''' for the data recovery, visit this page for suggestions: [https://forum.cgsecurity.org/phpBB3/viewtopic.php?t=1431 https://forum.cgsecurity.org/phpBB3/viewtopic.php?t=1431]

[[Category:Troubleshooting]]

Disk Quotas

2024-06-07T14:23:11Z

Phil:

==INTRO==
 

'''CS ''GRAD'' Net Users:''' The '''''CS Grad/Research Net''''' does not currently have disk quotas enabled. But, we ask that users on the CS Grad/Research Net be mindful that you are ''sharing disk space with much of CS''. If you need to store large amounts of data on the CS Grad Net, please see: [[Storing Large Amounts Of Data On Our Systems]]

'''CS ''UGRAD'' Net Users:''' On the '''''CS Ugrad Net''''', the Ugrad accounts ''are subject to '''disk quotas''''', which are limits on the total amount of data you are permitted to store in your home directory (or, in some cases, other directories). If you exceed a quota, you will be unable to create new files or add to existing files until you reduce the total amount of disk space you're using to go below your quota.

== How Quotas Work on the ''CS Ugrad Net'' ==

Every account that is subject to a quota has limit on the total amount of disk space used by that account's files. For most of our CS Ugrad accounts, that limit is '''10 GiB'''. Once you hit that limit, all attempts to allocate more space (creating new files, making existing files larger, etc.) will fail.

''If you cannot allocate more space (because you've hit your quota limit), '''you might not be able to log in via the GUI on our Ugrad computer lab Linux systems'''. If that happens, you will have to SSH in remotely and reduce your disk usage below your quota.''

==='''''{{red|IMPORTANT NOTE:}} If You Are Using A ''Cloud Drive'' ('''Dropbox''', '''Google Drive''', etc.)===

:If you have your CS Ugrad Linux account linked to a cloud drive such as '''Dropbox''' or '''Google Drive''', please note that those services may download local copies of your cloud files into your Ugrad account. This is an extremely quick way to go over your CS Ugrad disk quota. We recommend you not link cloud drives with your CS Linux account (unless your cloud drive is very small and well within your CS Ugrad disk quota.) We cannot accomodate users' cloud data within our provided home directory disk resources.

== How to Check Your Quota on the ''CS Ugrad Net'' ==

Log in to one of the [[Linux Clients on the CS Undergrad Net]] and run the following command from the command line:

quota

If it doesn't print anything, you are not subject to any quotas. If it does print something, the output will look like this:

''account'': 1.6GiB used out of 10.0GiB quota

This should be fairly self-explanatory. The person (with account name "''account''") has files totaling 1.6 gigabytes of data. The account's usage limit is 10 gigabytes.

== How to Get Yourself Under Quota on the ''CS Ugrad Net''==

If you're over quota, the only way to get back under is to delete or shrink files until your total disk usage is reduced below your limit.

You can use the <code>du</code> command line program to see how much space individual files or directories are using. One of the simplest ways to invoke it is to run the following command from your home directory:

du -h | sort -h

The above command will show you every directory in your home directory (and every subdirectory of them and every subdirectory of those and so on) and how much space it and all of its contents occupies, with the largest directories shown last. The directories containing the most data are probably the best candidates to start cleaning out.

Another useful command is the following:

du -sh * .??* | sort -h

This version of running the du command lists all directories ''and all files'' in the current directory and their sizes. (The ''previous'' version of running the du command shows all directories, not just the ones directly in the current directory, ''and'' it doesn't list files directly; they simply get added to the size tally for the directory they're in.)

:'''NOTE:''' With either of the two above commands, it might be helpful to pipe them to ''less'' or ''more'', or something similar, should your output be long enough to scroll by. For example...

:<pre>du -h | sort -h | less</pre>

=== If You Have .nfs Files ===

If, from the above list of commands, you run:

du -sh * .??* | sort -h

and you notice a file with a name starting with "<code>.nfs</code>" followed by a long string of numbers, you will want to remove it, as it can be a very large (and unwanted) file. And it's not a file you can use the <code>rm</code> command with (unlike other with other files.)

The .nfs file is created when some other file ''is deleted'' while a running program ''is still using'' that file. Our systems simply renames that other file (that you deleted) to <code>.nfs</code> (followed by a long string of numbers) while the program is still running. As soon as the program exits, the <code>.nfs</code> file will be removed. But, if the .nfs file remains in your directory, as mentioned, you cannot simply remove it with a <code>rm</code> command, as you would do with regular files. The .nfs file remains because there is some process/program open that is keeping the .nfs file in place. If you tried to directly remove the .nfs file that some process has open, there would be a replacement .nfs file created. So, you need to stop the program that is running that is keeping the .nfs file open.

If you need to figure out what program is using the file, you can use the <code>lsof</code> program, like this:

lsof .nfs''000000003114807500000002''

(Obviously, use the actual name of the file in your directory.) Its output will look something like this:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pv 9671 example 1w REG 0,45 167772160 823427189 .nfs000000003114807500000002

The most useful information is at the beginning, giving the name and process ID of the running program.

''This will only work on the system running the program.'' If, for example, you started a program on our <code>ugradx</code> system, you would only see useful information from <code>lsof</code> if you also ran it on <code>ugradx</code>. If you ran it on, say, <code>ugradz</code>, it would still see the <code>.nfs</code> file (because all the ugrad systems see the same home directory folders), but it wouldn't be able to find what program was using it.

=== If You Can't Find any Large Files ===

Sometimes the <code>quota</code> program will say that you're using a lot of disk space, but the <code>du</code> command doesn't show anything large.

One common cause for this is because of a quirk in Unix filesystem behavior. If a you delete a file while it's in use by a running program, the file will disappear from the directory, ''but it will still exist, invisibly using disk space'' until the running program exits. Even worse, if the program writes data to this deleted file, the extra data gets counted against your quota, even though you can't see the file. (Usually when you delete a file that's in use you'll get a .nfs file, [[#If You Have .nfs Files|as described above]], but sometimes the file will just disappear entirely.)

You can use the <code>lsof</code> program to find files that have deen deleted but are still in use, like this:

lsof +aL1 /home

If you have any files in this state, it'll print something like this:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME
pv 16081 example 1w REG 0,45 159907840 0 823427190 /home/example/inuse (barley.cs.jhu.edu:/home)

That will show the name of the program and the location where the file used to be before it was deleted. If you don't have any other way to stop the program, you can usually terminate it with the <code>kill</code> command, like this:

kill ''16081''

For the number, use the process ID (PID) from <code>lsof</code>'s output.

''This will only work if you run <code>lsof</code> on the same system where the other program is running.'' You might need to log into several systems to check things if you've used more than one for your recent work.

=== If You Still Can't Reduce Your Disk Usage ===

If the system insists that you're over quota but you can't figure out why, you can always email us at [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.

== If You Need a Larger Quota on the ''CS Ugrad Net''==

If your class projects or research require more disk space than your quota will allow, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] and detail the reasons your current quota is insufficient. (Note: Please ''do not'' request a larger disk quota to accommodate ''cloud drives'' such as '''Dropbox''' and '''Google Drive'''.) Please include the following information when requesting more disk space:

* Your CS username
* CS student status (ugrad? grad? concurrent?)
* Your JHED ID
* How much additional space you require.
* Name ''and'' section of class you're taking that's requiring the extra space.
* Name of the professor teaching the class.
* How long you need the increased quota. After that, your quota will be reduced to its normal level, and you will need to be below that level to write files to your directory.

''Quota increases are not guaranteed. Allow '''at least''' one full business day for your quota increase request to be processed.''

[[Category:Accounts]]
[[Category:Linux Clients]]

Creating a Personal Webpage

2024-06-07T14:22:44Z

Phil:

==INTRO==

CS users may create webpages on our www.cs.jhu.edu or www.ugrad.cs.jhu.edu web servers.

===NOTES:===
:* To make a webpage on our web servers, ''you must have a [[Obtaining_CS_Computer_Accounts|CS Linux account]]''.
:**CS Grad Net account required for the main CS webserver.
:**CS Ugrad Net account required for the Ugrad webserver.

:* {{red| CS IT does '''not''' create or edit webpage content for users. You are responsible for your own website design and troubleshooting.}}

== Accessing Your Webpage ==

NOTE: Where you see "''account''", replace that with your CS account name.

* On the CS '''''Grad/Research''''' net, use <tt><nowiki>http://</nowiki>www.cs.jhu.edu/~''account''</tt> or <tt><nowiki>http://</nowiki>cs.jhu.edu/~''account''</tt>

* On the CS '''''Ugrad''''' net, use <tt><nowiki>http://</nowiki>www.ugrad.cs.jhu.edu/~''account''</tt> or <tt><nowiki>http://</nowiki>ugrad.cs.jhu.edu/~''account''</tt>

== Making a Basic Homepage ==

<code>ssh</code> into one of our [[:Category:Linux Clients | Linux clients]].

chmod 0701 ~ # That's a tilde at the end of the command.
mkdir ~/public_html # This directory might already exist. If so, do not delete its contents.
chmod 0701 ~/public_html
cd ~/public_html

Edit <tt>index.html</tt> with your favorite editor.
Follow the template below for your <tt>index.html</tt> file:

<pre>
<html>
<head>
<title> Title of my webpage </title>
</head>
<body>
<h1> Title of my webpage </h1>
 This is a test! 
</body>
</html>
</pre>

Save and exit from your editor.

chmod 0604 index.html

Now check your work. Visit your webpage as described in [[#Accessing your webpage|Accessing your webpage]], above.

If you add more pages, please make sure they all have the appropriate permissions, as described in [[File Permissions for Webpages]]. That link is a useful resource any time you get a "permission denied" error when trying to access your webpage.

== Other Issues ==

If you need additional help, please e-mail [mailto:support@cs.jhu.edu CS IT Support] with a complete description of your problem.

[[Category:Webpages and Webservices]]

Contacting JHU IT Support

2024-06-07T14:22:21Z

Phil:

While CS ''IT Support'' offers support for the [[Services_Provided_By_CS_IT|''the Computer Science Dept's IT-specific'' services]], JHU IT offers ''their own'' IT support for services JHU IT provides to the University including:

* Issues with your JHED ID account, including your JHED password.
* JHU's ''@jhu.edu'' email (Microsoft Echange)
* JHU OneDrive
* JHU VPN
* Certain Microsoft software products
* ...and various other Enterprise services

JHU IT's main help website can be found at: [https://it.johnshopkins.edu/help/ https://it.johnshopkins.edu/help]

==Open A Trouble Ticket With JHU IT==

:To open a trouble ticket to obtain support of IT-related services directly offered by JHU IT, you can reach them...

* by calling them ''by phone'' at '''410-516-HELP'''
** It's the fastest way to reach JHU IT Support.
** You will be provided a ticket number for your issue.

*by visiting their ''Service website'': '''[https://johnshopkins.service-now.com/serviceportal https://johnshopkins.service-now.com/serviceportal]'''
**You will need your JHED credentials to access that page.
**Once you arrive at that page, choose the red {{red|Get Help}} link on the left.

*by emailing JHU IT at [mailto:help@jhu.edu help@jhu.edu]
** We are not entirely sure who at JHU/JHU IT will see email sent here, but JHU IT provided this email as an alternative way to reach JHU IT if needed. We suggest, however, to try one of the other above options first.

==Reporting spam received at your {{red|''@jhu.edu'' or ''@jhmi.edu''}} email address to JHU IT==

:If you receive spam (including phishing, etc.) email at your ''@jhu.edu'' or ''@jhmi.edu'' email address ''directly'' ('''''and''''' it did '''not''' originate from an ''@cs.jhu.edu'' email address or if you don't forward your CS email to your @jhu email), you can visit  [https://johnshopkins.service-now.com/serviceportal?id=kb_article&sys_id=59e4b648db2d7b84e6cfdb85ca96199d JHU's How-to page for reporting spam]. As part of the process, you'll want to forward that email (including any mail headers, if possible, by '''forwarding''' it ''as an attachment''), to [mailto:spam@jhu.edu spam@jhu.edu] (and perhaps include the word '''SPAM''' somewhere in the Subject line), so that JHU can examine it and take proper action. If you're not sure if the email is legitimate, mention that in your correspondence with JHU IT as well. If you haven't heard back from JHU in a reasonable amount of time, please [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support open a trouble ticket with JHU IT.]

:'''NOTE''': Spam mail received at your ''non-CS'' email address and that ''did not'' originate from an ''@cs.jhu.edu'' address does '''not''' need to be reported to CS IT's email address (support@cs.jhu.edu)

[[Category:Misc]]
[[Category:Support Options]]

CS Account Removal

2024-06-07T14:21:35Z

Phil:

={{red|THESE ACCOUNT REMOVAL POLICIES ARE SUBJECT TO CHANGE IN THE FUTURE.}}=

==INTRO==

:Due to the number of CS Grad/Research Net and Ugrad Net Linux accounts we must maintain on our systems, when a person leaves CS, depending upon the circumstances, that person's CS account(s) may be removed.

:This information is related to your '''''CS account''''' only. We are not referring to your '''''JHED''''' account which is maintained by [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support JHU's IT group.]

:You can click your current status below to jump to the appropriate section of this doc.

::[[#CS PhD STUDENTS| CS PhD Students]]

::[[#CS MASTERS STUDENTS| CS Masters Students]]

::[[#CS UGRAD STUDENTS|CS Undergraduate Students]]

::[[#CS CLASS/COURSE ACCOUNTS|CS Class/Course Accounts]]

::[[#CS COMBINED/CONCURRENT STUDENTS|CS Combined/Concurrent Students]]

::[[#CS_FACULTY.2C_INSTRUCTORS.2C_POSTDOCS.2C_RESEARCHERS_.28INCLUDING_RESEARCH_PROFESSORS.2C_SCIENTISTS.2C_RESEARCH_ENGINEERS.29_ETC.|CS Faculty, Instructors, Researchers, Postdocs, etc.]]

::[[#CS Staff| CS Staff]]

::'''IMPORTANT:''' [[#Email Forwarding Is Removed When Your CS Account Is Removed| Email Forwarding Will Be Removed When Your CS Account Is Removed]]

==CS PhD STUDENTS==

: Your CS ''PhD'' (Grad) account will be up for removal no sooner than '''3 years''' ''after'' graduation. ''(removal time subject to change.)''

: We will email your '''''CS email account''''' after those 3 years to let you know that your account will be removed ''and'' to remind you to download any files or email of yours still residing on our servers. You will have '''2 months''' after that notification before your account is removed.

:This means, if you want to receive notice of when your CS account is going to be removed, '''''you must monitor your CS email account.''''' You might consider [https://support.cs.jhu.edu/wiki/Forwarding_Mail forwarding your CS email] to some place you will regularly see it, in case we send you an email about closing your account. '''(We generally ''do not'' send to your JHU email account or elsewhere for account removal notifications.)'''

===Requesting An Account Extension===

:'''''After''''' you receive notice that your CS PhD account is being removed, you might still be able to request us to extend the time-frame for your account. You must notify us during the 2 months '''''after''''' we notify you that your account will be removed. And we will only extend accounts on a case-by-case basis, depending upon need. '''You'll need to have a [https://www.cs.jhu.edu/faculty CS Faculty] sponsor to continue your account ''and you must have a specific JHU-related reason to do so'' (e.g., officially collaborating with that faculty member on a project, etc.)'''

:* '''If you're graduating now, please ''do not'' write us to request an account extension. We will contact you sometime after 3 years of you graduating from CS, when we are evaluating accounts to remove, in order to discuss any account extension opportunities.''' Please make sure you monitor your CS email address, as that is where we will be sending emails regarding PhD account closures. '''''However,''''' if you are ready for your account to be closed ''now'', please let us know, and we can arrange that.

=== When we remove your CS PhD account, the following will also be removed ===

:* '''Home Directories:''' We will remove your CS home directories and all files within them.

:* '''Web Pages:''' We will remove any ''web pages'' you created in your account.

:* '''MySQL Accounts/Databases''' We will remove any ''MySQL accounts or databases'' owned by you.

:* '''Email:''' We will remove any email/email folders that belong to your CS CS account

:* '''Additional Email Presence:''' Your CS email presence will be removed. Therefore, if you were '''''forwarding your CS email''''' elsewhere, '''that forwarding will go away when your CS account is removed.''' If you had us set up a '''''forwarding mail alias''''' for you, that '''alias will go away as well.'''

===IMPORTANT PHD ACCOUNT REMOVAL NOTES:===

:* Some CS PhD students ''also'' have a CS ''Ugrad'' account. That CS Ugrad account''' will be going away no sooner than ''2 months'' after graduation,''' with no notice. So, make sure you remove what you need from your CS Ugrad account '''before''' you graduate.

:* If, at any time after you graduate, we find a security issue with your CS PhD account, we have the right to close your account. We typically try to contact you somehow to let you know what's going on, but, sometimes, that might not be possible.





===Rules to follow to retain your CS PhD account after graduation, and if, in the future, we extend your PhD account.===

:To preserve resources for current CS students, once you graduate,  there are a few rules in place you ''must'' follow, otherwise, your account may be removed with or without notice.

::* You must keep your use of CS disk space (your CS home directory) to a minimum, that is, the least amount of disk space absolutely needed. 

::* '''You must check your ''CS email'' regularly''' for important messages from CS support regarding your account, your use of resources, other CS IT-related announcements, ''or for an eventual account removal email.''

::* If you keep your CS email inbox local to our servers (i.e., you do not forward your CS email elsewhere), '''please keep your inbox ''below 100mb.''''' That means, you'll need to clean it out regularly. But, you'll be checking your CS email regularly anyway, so this should not be a problem for you to maintain. 




==CS MASTERS STUDENTS==

:Your CS '''Masters''' account (and any associated CS Ugrad account you might also have-- some Masters students have both) will be '''up for removal no sooner than 2 months after graduation'''. ''(removal time subject to change.)''

:We will email your '''''CS email account''''' approximately '''one month''' or more ''before'' your CS Masters account removal to let you know and to remind you to pull any files or email of yours still residing on our servers. This means, if you want notice of when your CS account is going to be removed, '''''you must monitor your CS email account.''''' You might consider [https://support.cs.jhu.edu/wiki/Forwarding_Mail forwarding your CS email] to some place you will regularly see it, in case we send you an email about closing your account. '''(We generally ''do not'' send to your JHU email account or elsewhere for account removal notifications.)'''

:'''Account extension:''' If you will be continuing in another educational program in the CS Dept (e.g., you are going for your CS PhD at JHU, please let us know as soon as possible so that we can continue to provide your CS account.)

=== When we remove your CS Masters account, the following will also be removed ===

:* '''Home Directories:''' We will remove your CS home directories and all files within them.

:* '''Web Pages:'''We will remove any ''web pages'' you created in your account.

:* '''MySQL Accounts/Databases''' We will remove any ''MySQL accounts or databases'' owned by you.

:* '''Email:'''We will remove any email/email folders that belong to your CS CS account

:* '''Email Presence''' Your CS email presence will be removed. Therefore, if you were forwarding your CS email elsewhere, '''that forwarding will go away when your CS account is removed.''' If you had us set up a forwarding mail alias for you, that alias will go away as well.

====NOTES:====

::* Please download any of your CS Masters (and CS Ugrad, if you have one) home directory files you need from the system before your CS Masters (and CS Ugrad) account is scheduled to be removed.
::* Please download any of your CS account email (your CS inbox) you need that resides on our mail server before your CS Masters account is scheduled to be removed. (This includes your CS Ugrad account's email, if you also have a CS Ugrad account.)
 

==CS UGRAD STUDENTS==

:Your CS '''Ugrad''' account will be up for removal no sooner than 2 months after graduation. ''(removal time subject to change.)''

:If you switch out of a CS Major or Minor, your CS Ugrad account will be up for removal no sooner than 2 months after you've left CS. ''(removal time subject to change.)''

:We will email your '''''CS email account''''' approximately '''one month''' or more before your CS Ugrad account removal to let you know and to remind you to pull any files or email of yours still residing on our Ugrad servers. This means, if you want notice of when your CS Ugrad account is going to be removed, '''''you must monitor your CS email account.''''' You might consider [https://support.cs.jhu.edu/wiki/Forwarding_Mail forwarding your CS email] to some place you will regularly see it, in case we send you an email about closing your account. '''(We generally ''do not'' send to your JHU email account or elsewhere for account removal notifications.)'''

:'''Account extension:''' If you will be continuing in another educational program in the CS Dept (e.g., you are going for your CS Masters or PhD at JHU, please let us know as soon as possible so that we can continue to provide your CS account.)

=== When we remove your CS Ugrad account, the following will also be removed ===

:* '''Home Directories:''' We will remove your CS home directories and all files within them.

:* '''Web Pages:''' We will remove any ''web pages'' you created in your account.

:* '''MySQL Accounts/Databases''' We will remove any ''MySQL accounts or databases'' owned by you.

:* '''Email:''' We will remove any email/email folders that belong to your CS CS account

:* '''Email Presence:''' Your CS email presence will be removed. Therefore, if you were forwarding your CS email elsewhere, '''that forwarding will go away when your CS account is removed.''' If you had us set up a forwarding mail alias for you, that alias will go away as well.

====NOTES:====

::* Please download any of your CS Ugrad home directory files you need from the system before your CS Ugrad account is scheduled to be removed.
::* Please download any of your CS Ugrad email (your CS inbox) you need that resides on our mail server before your CS Ugrad account is scheduled to be removed.
 

==CS CLASS/COURSE ACCOUNTS==

:If you're taking a CS class and have a CS '''class/course''' account, not a personal CS user account, your account will be up for removal no sooner than ''two months'' after the semester ends.

:We '''do not''' offer retention opportunites for CS Class/Course accounts after the class has ended.

:If you need a regular CS user account '''''and''''' you are a CS student '''''or''''' a CS faculty member has requested you to have a CS user account (not a class/course account), then, please see [https://support.cs.jhu.edu/wiki/Obtaining_CS_Computer_Accounts our page on obtaining CS accounts].

'''NOTES:'''

:* Please remove any files/email you need from the system before your CS class/course account is removed.

:* '''You will ''not'' receive a notification that your CS class/course account is being removed.'''
 

==CS COMBINED/CONCURRENT STUDENTS==

:If you're in both the CS Ugrad and Masters programs at the same time, both your Masters and Ugrad accounts will be removed no sooner than 2 months after you've graduated from the Masters program.

:When you're ready to graduate, please review the following two sections to see the process for account removal:

::[[#CS MASTERS STUDENTS| CS Masters Students]]
::[[#CS UGRAD STUDENTS|CS Undergraduate Students]]

 

==CS FACULTY, INSTRUCTORS, POSTDOCS, RESEARCHERS (INCLUDING RESEARCH PROFESSORS, SCIENTISTS, RESEARCH ENGINEERS) ETC.==

: CS has a new policy for account removal for CS faculty, instructors, postdocs and researchers (that can include research professors, research scientists, and research engineers.) Your CS account will be up for removal no sooner than '''3 years''' ''after'' you have left the department. ''(removal time subject to change.)''

: We will email your '''''CS email account''''' after those 3 years to let you know that your account will be removed ''and'' to remind you to download any files or email of yours still residing on our servers. You will have '''2 months''' after that notification before your account is removed.

: Remember, we will be sending notifications for CS account removal '''''to your CS email only!''''' This means, if you want to receive notice of when your CS account is going to be removed, '''''you must monitor your CS email account.''''' If you do not normally monitor your CS email, it is highly recommended that you consider [https://support.cs.jhu.edu/wiki/Forwarding_Mail forwarding your CS email] to some place you will regularly see it, in case we send you an email about closing your account. '''(We ''do not'' send CS account removal notices to your JHU email account or elsewhere.)'''

===Requesting An Account Extension===

:'''''After''''' you receive notice that your CS account is being removed, you might still be able to ''request us to extend the time-frame for your account''. You must notify us during the 2 months '''''after''''' we notify you that your account will be removed. And we will only extend accounts on a case-by-case basis, depending upon need. '''You'll need to have a CS faculty or CS administrative sponsor to continue your account.'''

:* '''If you're planning to leave JHU, please ''do not'' write us to request an account extension at this time. We will contact you sometime after 3 years of your leaving CS, when we are evaluating what accounts to remove in order to discuss any account extension opportunities.'''

=== When we remove your CS account, the following will also be removed ===

:* '''Home Directories:''' We will remove your CS home directories and all files within them.

:* '''Web Pages:''' We will remove any ''web pages'' you created in your account.

:* '''MySQL Accounts/Databases''' We will remove any ''MySQL accounts or databases'' owned by you.

:* '''Email:''' We will remove any email/email folders that belong to your CS CS account

:* '''Email Presence:''' Your CS email presence will be removed. Therefore, if you were forwarding your CS email elsewhere, '''that forwarding will go away when your CS account is removed.''' If you had us set up a forwarding mail alias for you, that alias will go away as well.

===IMPORTANT CS FACULTY, ETC. ACCOUNT REMOVAL NOTES:===

:* Some CS Faculty, Etc. accounts on the CS Grad Net ''also'' have a CS ''Ugrad'' account. That CS Ugrad account''' will be going away no sooner than ''2 months'' after you leave JHU, ''' with no notice. So, make sure you remove what you need from your CS Ugrad account '''before''' you leave the CS Department.
:**If you're leaving CS and it is decided that your CS Grad/Research acct can remain, your CS Ugrad account will still go away.

:* If, at any time after you leave JHU, we find a security issue with your CS account, we have the right to close your account. We typically try to contact you somehow to let you know what's going on, but, sometimes, that might not be possible.

===Rules to follow to retain your CS Faculty, etc. account after you have left the dept., and if, in the future, we extend your account.===

:To preserve resources for current CS-affiliated persons, once you leave the CS department,  there are a few rules in place you ''must'' follow, otherwise, your account may be removed with or without notice.

::* You must keep your use of CS disk space (your CS home directory) to a minimum, that is, the least amount of disk space absolutely needed. 

::* '''You must check your ''CS email'' regularly''' for important messages from CS support regarding your account, your use of resources, other CS IT-related announcements, ''or for an eventual account removal email.''

::* If you keep your CS email inbox local to our servers (i.e., you do not forward your CS email elsewhere), '''please keep your inbox ''below 100mb.''''' That means, you'll need to clean it out regularly. But, you'll be checking your CS email regularly anyway, so this should not be a problem for you to maintain.

 

==CS Staff==

:CS Staff accounts will be removed at the direction/discretion of the CS administrative office. ''If'' it is decided to send a notice to you regarding your CS account removal, it would be sent either to your CS account by our CS IT staff or by a CS administrator to the address they choose.

==Email Forwarding Is Removed When Your CS Account Is Removed==

:'''''CS will no longer be [https://support.cs.jhu.edu/wiki/Forwarding_Mail fowarding emails]''''' for those no longer currently affiliated with the CS department. This includes both the use of the '''.forward''' file, mail aliases, and several dept-wide mailing lists you might be on.

:Therefore, when your affiliation with the CS department is complete and your CS account is removed, '''''any email forwarding that you (or the CS IT staff) have configured with your CS account will be removed.'''''

[[Category:Accounts]]

Available Printers

2024-06-07T14:21:12Z

Phil:

We have various printers available for general use throughout the CS Dept.

{{red|'''Because of the great diversity in functionality amongst printers and people's personal systems, we can only offer support/assistance in configuring printing for only those computer systems and printers that CS IT Support maintains.''' '''''We do not configure users' own systems to print to our printers.'''''}}

Please see our [[:Category:Printing|Printing category]] for an '''overview and notes''' regarding printing at CS.

Also, please see the [[#Printer Problems|Printer Problems]] section at the bottom of this page.

NOTE: In the chart below, QUEUE NAME is the print queue name of the printer on our Ugrad and Masters'/Grad Lab Linux computers.



{| class="wikitable"

|-
! LOCATION !! MODEL !! HOSTNAME !! CS GRAD/UGRAD LABS LINUX QUEUE NAME !! AVAILABLE TO !! NOTES
|-
|Malone 122 (CS Undergraduate Lab)  ||HP LaserJet 4350 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers)||Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-4350-printer-series/412160 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-4350-printer-series/412160] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Unfortunately, for Macs, HP provides a driver there for older versions of the Mac OS (10.5), however you could see iF that driver will load and run properly in your later MacOS. Generally, If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone G61 (Masters'/Ugrad Lab) ||HP LaserJet 4350||mhg61prt.cs.jhu.edu||mhg61prt||All CS Grad and UGrad Students and faculty/staff/researchers/postdocs||Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-4350-printer-series/412160 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-4350-printer-series/412160] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Unfortunately, for Macs, HP provides a driver there for older versions of the Mac OS (10.5), however you could see iF that driver will load and run properly in your later MacOS. Generally, If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone 154 (CS Office Mailroom)||Canon ImageRunner Advance C7270 color copier||copier.cs.jhu.edu||copier|| All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers) '''''However, for CS students''', we ask that they only print to the color copier if color is absolutely necessary, and only during the CS Office's office hours.''|| COLOR, Duplexing copier '''and''' printer. {{red|1='''NOTE:''' Please default your print configuration to ''Black and White or Grayscale''. Only choose ''Color'' if you need to print out specifically in color.}}

'''DRIVERS:''' Drivers for several computing platforms can be found here: https://www.usa.canon.com/internet/portal/us/home/support/details/copiers-mfps-fax-machines/multifunction-copiers/imagerunner-advance-c7270?tab=drivers#Z7_MQH8HIC0L88RB0AMD0F1Q42K25

There are several drivers available for this copier. Windows users can choose PCL 5/6, PS, or UFRII. Choose the one that best fits your needs. ''However, we've noticed that, at least for Windows, the UFRII driver works best.''''' When configuring the copier as a printer, we suggest choosing the TCP/IP port option (at least in Windows) using ''copier.cs.jhu.edu'' as the hostname to connect to.

'''NOTE:''' CS IT does not maintain/configure the Canon copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.
|-
|Malone 257A (North-end section of MH 2nd floor) ||HP LaserJet p4515x||mh2ndprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Versions of the driver for up through MacOS 10.12 are available there as well. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-

|Malone 340 (''3rd floor Kitchen Area'') ||HP LaserJet P2055dn||mh3rdprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer ; not for high-volume printing. This printer was previously located in MH 322, but is now located in MH 340.

Printer supports LPD and HP JetDirect printing. It does not support IPP.

If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p2055-printer-series/3662052/model/3662058 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p2055-printer-series/3662052/model/3662058] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. For Mac users, HP offers their HP LaserJet P2050 Series Mac OS X Full Software Solution at that site. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-

|}

==Note to Mac Users==

:Macs can be somewhat tricky when configuring printers. One thing you should keep in mind when configuring one of our networked printers on your Mac is to choose to install an '''IP''' printer, put in the IP address or full hostname (with .cs.jhu.edu part) for the '''Address''' field. For the '''Protocol''' field, choose ''Line Printer Daemon -LPD''. (That '''Protocol''' field is usually the part that most Mac users do not set, and that needs to be set to print properly to our printers, in our experience.) You can keep the '''Queue''' field blank. That should be all you need.

==Printer Problems==

* If one of the printers that CS IT Support manages (other than the dept copier) is low on toner or experiencing print-quality issues, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] {{red|During Summer, the CS IT Staff all work remotely on Mondays and Fridays, so if you experience toner out or a paper jam, and we are not available, please let us know about the situation, but also, please try to use one of the other printers listed above.}}

* If you run out of paper at the printer, ''please visit Malone Hall 160 (the CS main office),'' and request more.

* If a CS-managed printer jams, and you are able to remove the jammed sheet, but the printer seems to hang on printing:
** Turn off the printer
** Unplug the power from the printer
** Wait at least 30 seconds.
** Plug the printer back in.
** Turn printer back on.
That usually clears out a printer's internal print queue.

* If a CS-managed printer jams, and you are unable to remove/find the paper jamming in the printer, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

[[Category:Printing]]

[[Category:Labs]]

Audio-Visual Support Options

2024-06-07T14:17:52Z

Phil:

==INTRO==

As of April, 2023, Audio Visual support options for Malone Hall has changed. We are generally '''''no longer using'''
[https://classrooms.johnshopkins.edu/ Kit-Cats] for '''A/V support''' as we had for many years (except, perhaps, in certain circumstances). '''''Instead''''', WSE now has their own A/V support team,
the [https://support.cldt.jhu.edu/hc/en-us Center for Learning Design & Technology group], and that's who we will utilize for A/V support.

CS also maintains projectors in the '''CS Ugrad Lab (MH 122)''' and the '''MSSI Lab (MH 316.)''' See below for A/V support contact info for those two rooms as well. In addition, '''Hackerman B-17''' has been used by CS in the past for seminars and classes. Should CS continue to use that room, and you need A/V support, that info is below too.

:{{red|'''NOTE:''' CS IT '''''does not''''' administer or repair general A/V equipment or services within Malone Hall '''''or''''' for Hackerman B-17's lecture hall, other than the CS Undergrad Computing Lab, Malone Hall 122. Please see below for A/V support options.}}

==General Malone Hall A/V Support ==

This includes most Malone offices and seminar/conference rooms.

::'''[https://support.cldt.jhu.edu/hc/en-us Center for Learning Design & Technology (CLDT)]'''
:::Available Monday through Friday, 8am to 8pm
:::'''(410) 514-3124''' (Call for faster service.)
:::[mailto:cldtsupport@jhu.edu '''cldtsupport@jhu.edu''']
:::[https://support.cldt.jhu.edu/hc/en-us/requests/new Submit a Helpdesk Ticket]

::: Provide them as much info as possible including:
::* the room number where the A/V issue is happening
::* any details you may have about the A/V equipment (brand, model, etc.)
::* a detailed explanation of the issue the A/V equipment is experiencing
::* your contact info

==CS Undergrad Lab MH 122 And Its Breakout Rooms Projectors==

MH-122 hosts an overhead projector. That projector has a control box on the rear left table in the main room, and the projector can be selected to connect to one of our Linux systems at that table ''(ugrad1)'' or ''to your own laptop''. MH-122 also has 3 short-throw projectors located in MH-122's breakout rooms.

===Issues with projector connections to our lab Linux system ''(ugrad1)'' in MH-122===
If you're having issues with the overhead projector's connection to our Linux computer, ''ugrad1'', then please email [mailto:support@cs.jhu.edu support@cs.jhu.edu], and we will look into the issue. Please include as many details as you can regarding the problem you're experiencing with the projectors.

===Issues with connecting your own equipment to the MH-122 projectors===
If the issue is ''your own connection'' to any of the projectors in MH-122 (the overhead or short-throw projectors), then please contact CLDT using the information below...

::'''[https://support.cldt.jhu.edu/hc/en-us Center for Learning Design & Technology (CLDT)]'''
:::Available Monday through Friday, 8am to 8pm
:::'''(410) 514-3124''' (Call for faster service.)
:::[mailto:cldtsupport@jhu.edu '''cldtsupport@jhu.edu''']
:::[https://support.cldt.jhu.edu/hc/en-us/requests/new Submit a Helpdesk Ticket]

==MSSI Lab Projector In MH 316/MH 322 Lab==

:For any issues with the '''''Epson BrightLink 485Wi''''' projector in the MSSI Lab, MH-316/MH-322...

:During regular hours, please contact [mailto:support@cs.jhu.edu support@isi.jhu.edu], and ISI's IT support will look into the issue. Please include as many details as you can regarding the problem you're experiencing with the projector.

===If it's after hours or on a weekend...===

:If it's after hours or on a weekend, please ''first try'' to contact CLDT at the address below, '''and email [mailto:support@isi.jhu.edu support@isi.jhu.edu] to let them know you contacted CLDT.

::'''[https://support.cldt.jhu.edu/hc/en-us Center for Learning Design & Technology (CLDT)]'''
:::Available Monday through Friday, 8am to 8pm
:::'''(410) 514-3124''' (Call for faster service.)
:::[mailto:cldtsupport@jhu.edu '''cldtsupport@jhu.edu''']
:::[https://support.cldt.jhu.edu/hc/en-us/requests/new Submit a Helpdesk Ticket]

:Provide them as much info as you can about the issue you are experiencing, including your name, a way to reach you, the location of the projector (there are actually ''two'' projectors in that room. One closest to the MH-316 door and one near the MH-322 door), and the model of the projector: '''''Epson BrightLink 485Wi'''''.

==Hackerman Hall B-17's A/V Equipment==

CS utilizes this lecture hall for seminars and classes. If there are problems with the A/V equipment, please contact:

::'''[https://support.cldt.jhu.edu/hc/en-us Center for Learning Design & Technology (CLDT)]'''
:::Available Monday through Friday, 8am to 8pm
:::'''(410) 514-3124''' (Call for faster service.)
:::[mailto:cldtsupport@jhu.edu '''cldtsupport@jhu.edu''']
:::[https://support.cldt.jhu.edu/hc/en-us/requests/new Submit a Helpdesk Ticket]

==And if CLDT cannot assist with the A/V==

If, for some reason, CLDT cannot assist with the A/V, we are providing contact info for our old A/V support team from JHU, Kit-cats, just in case. Kit-cats mostly provides A/V support for the Krieger School of Arts & Sciences (KSAS), and they might require a charge/cost number.

::'''KIT-CATS''' ('''K'''rieger '''I'''nformation '''T'''echnology - '''C'''lassroom '''A'''udiovisual '''T'''echnology '''S'''upport):
::: [https://classrooms.johnshopkins.edu '''https://classrooms.johnshopkins.edu''']
::: '''410-516-6699''' (calling will provide you faster service.)
::: [mailto:kitcats@jhu.edu '''kitcats@jhu.edu''']

[[Category:Audio-Visual]]
[[Category:Support Options]]

Phishing and Spoofing-Masquerading Spam

2024-06-07T14:15:23Z

Phil:

{{messagebox|
type=stop|
STOP! READ HERE FIRST: This page contains instructions for '''''Computer Science Department'' affiliates''' only|
2= 
If you are '''''not affiliated''''' with the ''Johns Hopkins University '''Computer Science Department''''', this is '''''not''''' the right resource for you. Instead, please see [https://johnshopkins.service-now.com/serviceportal?id=kb_article&sys_id=59e4b648db2d7b84e6cfdb85ca96199d JHU IT's page on how to report spam] for further instructions. 
 
If you are a Computer Science affiliate, please read on...
}}

==Phishing==

:Phishing can generally be defined as non-legitimate email you receive that tries to get you to provide the sender some type of personal information. The sender is "fishing" for info from you.

:What are some elements of phishing email?

* It could be in the form of an html-based email with a login page embedded.

* It could be something as simple as someone emailing you requesting you to send them info directly.
**And sometimes, the sender might have first created an email address, like a gmail address, that looks ''similar'' to one you might already know, but not exactly the same.
**Or it might be a masqueraded sender address. See the Spoofing (Masquerading)/Spear Phishing section below.

* A phishing email might have a link to a login or info request page.

: The above are just some examples of characteristics of phishing emails.

==Be Wary...==

:It is very important that you examine ''all'' incoming email to make sure it comes from a legitimate source.

:Your mail client should provide you a way to look at ''full mail or message headers'' so you can see if what you ''think'' is a legit address in the '''From:''' part of your message is actually the ''real'' address the sender is sending from.

:If you're unsure about an email, you should look up the person's email address off an official website (my.jh.edu, etc.) and use the looked-up address to contact the email originator to confirm the email request. Remember, these ''spammers might simply change even one character in their own email address'' from an email address you might already recognize.

:If your email has a ''link'' to a web page, the text for the link you see in your email may ''not'' be where the link actually takes you. '''Examine the link carefully.''' If you're at a computer, you might be able to hover your pointer over the link to see its true URL.

:Also, look for ''spelling'' or ''grammatical'' errors in an email. Sometimes, those could indicate that the email is not from a legitimate source.

==Spoofing (Masquerading)/Spear Phishing==

:'''Spoofing''' or '''Masquerading''' is when someone sends an email and it appears to come from someone else. You you could receive spoofed/masqueraded email in the form of a phishing email. Please see above for info on phishing email.

:'''Spear Phishing''' ''extends'' the masquerading, as spear phishing is a type of phishing spam where a spammer sends email that ''appears'' to be from someone you know/trust, but is actually from the spammer.

:: In the case of spear phishing, the spammer tries to get you to send them information (financial, etc.), as you might think you're actually sending it to the person you know/trust (and you're really not.)

::Spear Phishing is a ''very dangerous type of email,'' and it's easy to fall prey to it. It has become a common personal information-fishing tactic. And... it's also a very easy thing for a spammer to do.

::Spammers can make the From: address in your email look like any name or email address, like that of your trusted friend, family member, co-worker, etc. However, the actual e-mail was sent by the spammer. Examining the full mail headers for your email (different methods for each email client), can help you determine the actual sender's (spammer's) email address. (And it's also possible that the spammer's email address you see in the headers might not actually belong to the spammer, but rather and meial address the spammer has stolen.)

:: If you receive email that looks like it comes from someone you know, but the message content seems suspicious in some way, examine the mail carefully, including the mail headers for the actual sender's email address, to be sure it's legitimate. If you receive email asking for personally identifiable information, financial info, login credentials, etc., be wary, and make sure you are replying to the legitimate audience.

::''If you are not sure if the email is legit,'' contact the "sender" by an alternate means, e.g, by phone (a phone number you know is legit) or send a separate email to that individual (do not just click reply on the suspicious email) using an email address you know for that individual.

==If You Receive Phishing/Spoofing Email...==
:If you receive phishing/spoofing email , especially if it's requesting you to log in to the JHU login page (or to other pages that request you to login) or asks for a gift card or wants to know your availability, please be wary of it, ''and if you think it's not legit'', '''do ''not'' click on any included links located in that phishing mail!'''

:{{red|'''Instead...'''}} (and please read the below options carefully.)

===...if the mail you received is specifically a Phishing email that {{red|''looks like''}} it came from an {{red|@cs.jhu.edu email address}}===

:If you receive a Phishing email that '''looks like it ''came from'' an ''@cs.jhu.edu'' email address''', we want to know about that, ''regardless'' of whether you received the email at your ''own'' @cs.jhu.edu or @jhu.edu email address. So, in this instance, please forward the Phishing email (including any mail headers, if possible, by '''forwarding it''' ''as an attachment''), to [mailto:support@cs.jhu.edu support@cs.jhu.edu] so that our CS IT Support Team can examine it and take proper action.

:{{red|'''However...'''}}

:If the Phishing email you received does '''''not''''' look like it came ''from'' an ''@cs.jhu.edu'' email address, then please see the below two options to determine who to report the Phishing email to.

===...if you receive Phishing/Spoofing email at your {{red|''@jhu.edu''}}, {{red|''@jhmi.edu''}} or other {{red|''non''-@cs.jhu.edu}} (but still ''JHU''-related) email address===

:If you receive spam (including phishing, etc.) email at your ''@jhu.edu'' (or @jhmi.edu, @jh.edu, etc.) email address ''directly'' (and is not from an @cs.jhu.edu email address, or if you don't forward your CS email to your @jhu email), you can visit  [https://johnshopkins.service-now.com/serviceportal?id=kb_article&sys_id=59e4b648db2d7b84e6cfdb85ca96199d JHU's How-to page for reporting spam]. As part of the process, you'll want to forward that email (including any mail headers, if possible, by '''forwarding''' it ''as an attachment''), to [mailto:spam@jhu.edu spam@jhu.edu] (and perhaps make the Subject Line say '''SPAM'''), so that JHU can examine it and take proper action. If you're not sure if the email is legitimate, mention that in your correspondence with JHU IT as well. If you haven't heard back from JHU in a reasonable amount of time, please [https://support.cs.jhu.edu/wiki/Contacting_JHU_IT_Support open a trouble ticket with JHU IT.]

:'''NOTE''': Phishing mail received at your ''non-CS'' email address and that did not originate from an ''@cs.jhu.edu'' address does '''not''' need to be reported to CS IT (i.e,. support@cs.jhu.edu)

===...if you receive Phishing/Spoofing email at your {{red|''@cs.jhu.edu''}} email address===

:If you receive the spam/phishing email ''directly'' (i.e., not forwarded from your @jhu.edu address) at your ''CS email address'', or... if you think the email originated from an @cs.jhu.edu email address, please forward it (including any mail headers, if possible, by '''forwarding it''' ''as an attachment''), to [mailto:support@cs.jhu.edu support@cs.jhu.edu] so that our CS IT Support Team can examine it and take proper action.

==Filtering Spam Received At Your CS Email email address==

:Please see: [[:Category:Spam Filtering At CS|Spam Filtering At CS]]

==A JHU IT-Prepared Doc To Help Its Users Identify Phishing Emails==

:JHU has put together a pdf that provides helpful information for identifying phishing emails. It's geared to those using JHU's email system, but many of its tips apply to all that receive email.

:Please read: [[Media:Phishing-Safe_Links_and_Detecting_Suspicious_URLs.pdf|Phishing-Safe_Links_and_Detecting_Suspicious_URLs.pdf]]

==Do's & Don'ts Of Protecting Yourself From Phishing, Malware, & Ransomware-based Emails Scams==

:In a recent email to the JHU public, Darren Lacey, JHU's Chief Information Security Officer, compiled an excellent collection of Do's and Don'ts to protect yourself from phishing, malware, and ransomware-based email scams. Click the link below to read Darren's email.

:[[Media:BeCautiousAndAvoidPhishingAttacks.pdf|Be Cautious and Avoid Phishing Attacks - Do's & Don'ts]]

==Training Course Opportunity To Help You Identify Phishing Emails==

:JHU offers an excellent online course for the end-user regarding electronic information security and data management that includes a section on ''identifying phishing emails''.

:To get info on the course, '''you need to be on the [[VPN_-_JHU | JHU VPN]]''' or directly on a JHU network, and then browse to:

:[https://lms14.learnshare.com/dashboard/dash.home.aspx?Z=Cvz7rlERBiINCk3kFkMDWtWkTAGCTs%2fZPxff8PHH9jpE3NtAwUrdMyfZVOCTBf2m Course: JHU Electronic Information Security and Data Management]

[[Category:Spam]]

If You Receive Spam

2024-06-07T14:13:07Z

Phil:

MediaWiki:Common.css

2024-06-07T14:11:03Z

Phil:

/* CSS placed here will be applied to all skins */

/* CATEGORY LINK START
* Created by http://mediawiki.org/User:Kyle_van_der_meer
* Used for Version 2 for non-table layout.
*/
.category_link{
v-align:top;
display:inline-block;
width:144px; /*Default width part 2*/
}

.category_link a{
border:1px solid #333; /*Default dark color*/
color:#fff; /*Default Light color*/
background-color:#333; /*Default dark color*/
padding:2px;
line-height:1;
display:block;
}

.category_link a:hover{
border:1px solid #333; /*Default dark color*/
color:#333; /*Default dark color*/
background-color:#eee; /*Default light color*/
}
/*CATEGORY LINK END*/

/* CATEGORY TREE START */

#main-page-categories {
margin: 0.75em;
}
#main-page-categories .CategoryTreeTag {
-webkit-column-width: 15em;
-moz-column-width: 15em;
-ms-column-width: 15em;
column-width: 15em;
-webkit-column-gap: 2em;
-moz-column-gap: 2em;
-ms-column-gap: 2em;
column-gap: 2em;
}
#main-page-categories .CategoryTreeBullet,
#main-page-categories .CategoryTreeEmptyBullet {
display: none;
}
#main-page-categories .CategoryTreeItem {
padding-left: 0.75em;
text-indent: -0.75em;
display: inline-block;
}

/* CATEGORY TREE END */

/* MESSAGE BOX START */

.message-box {
padding: 1.2rem 0.8rem !important;
margin: 10px 0;
background-color: rgba(0, 0, 0, 0.1);
text-align: left;
}

figure.message-box {
display: grid;
grid-template-columns: min-content 1fr;
}

figure.message-box figcaption {
grid-column: 2;
grid-row: 1;
text-align: left;
font-weight: bold;
font-size: 1.12em;
}
figure.message-box p {
grid-column: 2;
grid-row: 2;
text-align: left;
vertical-align: middle;
margin: auto 0 !important;
}
figure.message-box p.standalone {
grid-row: 1 / 3;
}

.message-box:before {
font-family: "Font Awesome 6 Free", "Font Awesome 5 Free", FontAwesome;
font-style: normal;
font-weight: 900;
font-size: 2em;
speak: none;
display: inline-block;
text-decoration: inherit;
width: 1em;
margin: auto 0.4em auto 0.2em;
text-align: center;
font-variant: normal;
text-transform: none;
line-height: 1em;
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale
grid-column: 1;
grid-row: 1 / 3;
}
.info-box:before {
color: #00529B;
content: "\f05a";
}
.warning-box:before {
color: #9A6324;
content: "\f071";
}
.todo-box:before {
color: #4363d8;
content: "\f46c";
}
.stop-box:before {
color: #E6194B;
content: "\f057";
font-size: 3em;
}
.info-box {
background-color: rgba(0, 173, 255, 0.1);
}
.warning-box {
background-color: rgba(254, 204, 0, 0.2);
}
.todo-box {
background-color: rgba(0, 130, 200, 0.2);
}
.stop-box {
background-color: rgba(230, 25, 75, 0.2);
}
figure.stop-box figcaption {
font-size: 1.25em;
}

/* MESSAGE BOX END */

MediaWiki:Common.css

2024-06-07T14:09:31Z

Phil:

/* CSS placed here will be applied to all skins */

/* CATEGORY LINK START
* Created by http://mediawiki.org/User:Kyle_van_der_meer
* Used for Version 2 for non-table layout.
*/
.category_link{
v-align:top;
display:inline-block;
width:144px; /*Default width part 2*/
}

.category_link a{
border:1px solid #333; /*Default dark color*/
color:#fff; /*Default Light color*/
background-color:#333; /*Default dark color*/
padding:2px;
line-height:1;
display:block;
}

.category_link a:hover{
border:1px solid #333; /*Default dark color*/
color:#333; /*Default dark color*/
background-color:#eee; /*Default light color*/
}
/*CATEGORY LINK END*/

/* CATEGORY TREE START */

#main-page-categories {
margin: 0.75em;
}
#main-page-categories .CategoryTreeTag {
-webkit-column-width: 15em;
-moz-column-width: 15em;
-ms-column-width: 15em;
column-width: 15em;
-webkit-column-gap: 2em;
-moz-column-gap: 2em;
-ms-column-gap: 2em;
column-gap: 2em;
}
#main-page-categories .CategoryTreeBullet,
#main-page-categories .CategoryTreeEmptyBullet {
display: none;
}
#main-page-categories .CategoryTreeItem {
padding-left: 0.75em;
text-indent: -0.75em;
display: inline-block;
}

/* CATEGORY TREE END */

/* MESSAGE BOX START */

.message-box {
padding: 1.2rem 0.8rem !important;
margin: 10px 0;
background-color: rgba(0, 0, 0, 0.1);
text-align: left;
}

figure.message-box {
display: grid;
grid-template-columns: min-content 1fr;
}

figure.message-box figcaption {
grid-column: 2;
grid-row: 1;
text-align: left;
font-weight: bold;
font-size: 1.12em;
}
figure.message-box p {
grid-column: 2;
grid-row: 2;
text-align: left;
vertical-align: middle;
margin: auto 0 !important;
}
figure.message-box p.standalone {
grid-row: 1 / 3;
}

.message-box:before {
font-family: "Font Awesome 6 Free", "Font Awesome 5 Free", FontAwesome;
font-style: normal;
font-weight: 900;
font-size: 2em;
speak: none;
display: inline-block;
text-decoration: inherit;
width: 1em;
margin: auto 0.4em auto 0.2em;
text-align: center;
font-variant: normal;
text-transform: none;
line-height: 1em;
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale
grid-column: 1;
grid-row: 1 / 3;
}
.info-box:before {
color: #00529B;
content: "\f05a";
}
.warning-box:before {
color: #9A6324;
content: "\f071";
}
.todo-box:before {
color: #4363d8;
content: "\f46c";
}
.stop-box:before {
color: #E6194B;
content: "\f057";
font-size: 3em;
}
.info-box {
background-color: rgba(0, 173, 255, 0.1);
}
.warning-box {
background-color: rgba(170, 110, 40, 0.2);
}
.todo-box {
background-color: rgba(0, 130, 200, 0.2);
}
.stop-box {
background-color: rgba(230, 25, 75, 0.2);
}
figure.stop-box figcaption {
font-size: 1.25em;
}

/* MESSAGE BOX END */

MediaWiki:Common.css

2024-06-07T14:07:51Z

Phil:

/* CSS placed here will be applied to all skins */

/* CATEGORY LINK START
* Created by http://mediawiki.org/User:Kyle_van_der_meer
* Used for Version 2 for non-table layout.
*/
.category_link{
v-align:top;
display:inline-block;
width:144px; /*Default width part 2*/
}

.category_link a{
border:1px solid #333; /*Default dark color*/
color:#fff; /*Default Light color*/
background-color:#333; /*Default dark color*/
padding:2px;
line-height:1;
display:block;
}

.category_link a:hover{
border:1px solid #333; /*Default dark color*/
color:#333; /*Default dark color*/
background-color:#eee; /*Default light color*/
}
/*CATEGORY LINK END*/

/* CATEGORY TREE START */

#main-page-categories {
margin: 0.75em;
}
#main-page-categories .CategoryTreeTag {
-webkit-column-width: 15em;
-moz-column-width: 15em;
-ms-column-width: 15em;
column-width: 15em;
-webkit-column-gap: 2em;
-moz-column-gap: 2em;
-ms-column-gap: 2em;
column-gap: 2em;
}
#main-page-categories .CategoryTreeBullet,
#main-page-categories .CategoryTreeEmptyBullet {
display: none;
}
#main-page-categories .CategoryTreeItem {
padding-left: 0.75em;
text-indent: -0.75em;
display: inline-block;
}

/* CATEGORY TREE END */

/* MESSAGE BOX START */

.message-box {
padding: 1.2rem 0.8rem !important;
margin: 10px 0;
background-color: rgba(0, 0, 0, 0.1);
text-align: left;
}

figure.message-box {
display: grid;
grid-template-columns: min-content 1fr;
}

figure.message-box figcaption {
grid-column: 2;
grid-row: 1;
text-align: left;
font-weight: bold;
font-size: 1.12em;
}
figure.message-box p {
grid-column: 2;
grid-row: 2;
text-align: left;
vertical-align: middle;
margin: auto 0 !important;
}
figure.message-box p.standalone {
grid-row: 1 / 3;
}

.message-box:before {
font-family: "Font Awesome 6 Free", "Font Awesome 5 Free", FontAwesome;
font-style: normal;
font-weight: 900;
font-size: 2em;
speak: none;
display: inline-block;
text-decoration: inherit;
width: 1em;
margin: auto 0.4em auto 0.2em;
text-align: center;
font-variant: normal;
text-transform: none;
line-height: 1em;
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale
grid-column: 1;
grid-row: 1 / 3;
}
.info-box:before {
color: #00529B;
content: "\f05a";
}
.warning-box:before {
color: #7c4400;
content: "\f071";
}
.todo-box:before {
color: #3cb44b;
content: "\f46c";
}
.stop-box:before {
color: #E6194B;
content: "\f057";
font-size: 3em;
}
.info-box {
background-color: rgba(0, 173, 255, 0.1);
}
.warning-box {
background-color: rgba(255, 255, 25, 0.2);
}
.todo-box {
background-color: rgba(60, 180, 75, 0.2);
}
.stop-box {
background-color: rgba(230, 25, 75, 0.2);
}
figure.stop-box figcaption {
font-size: 1.25em;
}

/* MESSAGE BOX END */

Template:Important

2024-06-07T14:04:30Z

Phil:

<noinclude>
Marks text as important to draw attention to it.

<code><nowiki>{{important|This is important!}}</nowiki></code> → {{important|This is important!}}
</noinclude><includeonly>{{red|{{{1}}}}}</includeonly>

Template:Outage

2024-06-07T14:02:13Z

Phil:

<noinclude>This is a template for formalizing the structure of outage notifications on the [[Notices]] page.

At a minimum, use of this template should look like this:

<nowiki>{{</nowiki>outage
|time=''date and time outage started''
|services=''affected services''
|summary=''summary of the problem''<nowiki>}}</nowiki>

That will look like this:

{{outage
|time=''date and time outage started''
|services=''affected services''
|summary=''summary of the problem''}}

There is a <code>type</code> parameter, which gives the type of outage. It defaults to "Issue".

<nowiki>{{</nowiki>outage
|type=Planned outage
|time=''date and time outage will starte''
|services=''affected services''
|summary=''summary of the outage''<nowiki>}}</nowiki>

{{outage
|type=Planned outage
|time=''date and time outage will starte''
|services=''affected services''
|summary=''summary of the outage''}}

You can include an <code>update</code> parameter, which will replace the last line of the output:

<code><nowiki>{{</nowiki>outage … |update=As of ''date/time'', the problem has been resolved.<nowiki>}}</nowiki></code> →

{{outage
|time=''date and time outage started''
|services=''affected services''
|summary=''summary of the problem''
|update=As of ''date/time'', the problem has been resolved.}}

You can also include a <code>details</code> parameter. The details may span multiple lines, but you'll need to put a <code><nowiki> </nowiki></code> at the end of each line:

<nowiki>{{</nowiki>outage
|time=''date and time outage started''
|services=''affected services''
|summary=''summary of the problem''
|details=''Extra Details 1''<nowiki> </nowiki>
''Extra Details 2''<nowiki>}}</nowiki>

{{outage
|time=''date and time outage started''
|services=''affected services''
|summary=''summary of the problem''
|details=''Extra Details 1'' 
''Extra Details 2''}}

</noinclude><includeonly>==== {{#if:{{{type|}}}|{{{type}}}|Issue}} with {{{services}}} ====
<ul style="list-style-type: none; margin-left: 0">
<li>'''WHEN''': {{{time}}}</li>
<li>'''WHAT''': {{{summary}}}</li>
{{#if:{{{update|}}}|<li>{{red|'''UPDATE''':}} {{{update}}}</li>}}
{{#if:{{{details|}}}|<li>'''DETAILS''': {{{details}}}</li>}}
</ul></includeonly>

Notices

2024-06-07T14:00:23Z

Phil:

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 








== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==






=== UNPLANNED CS IT SERVICE OUTAGES ===



:None at this time.




=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.













== {{red|CS COMPUTING LAB AVAILABILITY}} ==

 





CLSP SUMMER PROGRAM
:'''MH 122 ''UNAVAILABILITY'''''
::'''WHAT:''' MH 122 (and its breakout rooms) will be '''''closed''''' for the summer due to a CLSP workshop being held there.
::'''WHEN:''' Wednesday, June 5 through Tuesday, August 6.
::'''NOTES:'''

:* The MH 122 Linux systems, ugrad1 through ugrad12, will continue to be available, '''''but only remotely via ssh'''''. There will be some downtime for those systems on 6/5 and on 8/6 as the systems are transferred from, and then, back to MH 122. Please see our page on: [[Linux_Clients_on_the_CS_Undergrad_Net]] https://support.cs.jhu.edu/wiki/Linux_Clients_on_the_CS_Undergrad_Net for a list of our remotely-available Ugrad Linux systems.

:* The printer in MH 122 will be ''unavailable'' during this time.

:* The G61 Masters/Ugrad Lab will remain open and available during the summer, and its Linux systems will be available for in-person and remote work, as usual. The G61 printer will remain available as well.


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.




















== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Main Page

2024-06-07T13:56:23Z

Phil:

==Welcome to the JHU Computer Science Dept I.T. Group's User Support Wiki==

Here, we (the [https://www.cs.jhu.edu/it-support CS IT Support Group]) provide documentation on how to use many of our services. ''(Note: this wiki is only modifiable by the administrators.)''

If you need assistance with any of the documentation, or if you need computer assistance with [[Services Provided By CS IT|machines or services we support]], please e-mail {{mailto|support}}

'''{{red|We are available 8:30am to 5pm Monday - Friday, except university holidays.}}'''

 
{{messagebox| CS IT is back in Malone Hall. CS IT Staff members are working in a hybrid schedule, so some of the staff might be working remotely, while others might be on campus. We continue to be available ''M-F, 8:30 to 5pm'', but although we might be on campus, some of our services may only be provided via online means. Please see: [[Obtaining_CS_IT_Services_Remotely | Obtaining CS IT Services Remotely page]] for further information.|type=warning}}

==Our ''Scope Of Services''... What IT Services Do We Provide?==

'''''New to the CS Dept?''''' Please read about the many services provided by CS IT at our [[Services Provided By CS IT|Scope of Services]] page. You may also visit our [[Onboarding]] page.



== {{red|Operations Status}} of CS Servers/Services/Labs==

{{red|Visit our [[Notices]] page for a list of planned/unplanned ''service outages'', ''CS Computing Lab availability'', and ''other important notifications''.}}
 

 

''To start using this Wiki, you may do a '''search''' from the sidebar on the left or choose from one of our categories below.''

==Categories==
<div id=main-page-categories>
<categorytree mode=categories hideroot=on>All</categorytree>
</div>

Template:Red

2024-06-07T13:55:04Z

Phil: Created page with "<noinclude>This template just turns a span of text red. <code><nowiki>{{red|This text will be colored red}}</nowiki></code> → {{red|This text will be colored red}} </noincl..."

MediaWiki:Common.css

2024-06-07T13:50:02Z

Phil:

/* CSS placed here will be applied to all skins */

/* CATEGORY LINK START
* Created by http://mediawiki.org/User:Kyle_van_der_meer
* Used for Version 2 for non-table layout.
*/
.category_link{
v-align:top;
display:inline-block;
width:144px; /*Default width part 2*/
}

.category_link a{
border:1px solid #333; /*Default dark color*/
color:#fff; /*Default Light color*/
background-color:#333; /*Default dark color*/
padding:2px;
line-height:1;
display:block;
}

.category_link a:hover{
border:1px solid #333; /*Default dark color*/
color:#333; /*Default dark color*/
background-color:#eee; /*Default light color*/
}
/*CATEGORY LINK END*/

/* CATEGORY TREE START */

#main-page-categories {
margin: 0.75em;
}
#main-page-categories .CategoryTreeTag {
-webkit-column-width: 15em;
-moz-column-width: 15em;
-ms-column-width: 15em;
column-width: 15em;
-webkit-column-gap: 2em;
-moz-column-gap: 2em;
-ms-column-gap: 2em;
column-gap: 2em;
}
#main-page-categories .CategoryTreeBullet,
#main-page-categories .CategoryTreeEmptyBullet {
display: none;
}
#main-page-categories .CategoryTreeItem {
padding-left: 0.75em;
text-indent: -0.75em;
display: inline-block;
}

/* CATEGORY TREE END */

/* MESSAGE BOX START */

.message-box {
padding: 1.2rem 0.8rem !important;
margin: 10px 0;
background-color: rgba(0, 0, 0, 0.1);
text-align: left;
}

figure.message-box {
display: grid;
grid-template-columns: min-content 1fr;
}

figure.message-box figcaption {
grid-column: 2;
grid-row: 1;
text-align: left;
font-weight: bold;
font-size: 1.12em;
}
figure.message-box p {
grid-column: 2;
grid-row: 2;
text-align: left;
vertical-align: middle;
margin: auto 0 !important;
}
figure.message-box p.standalone {
grid-row: 1 / 3;
}

.message-box:before {
font-family: "Font Awesome 6 Free", "Font Awesome 5 Free", FontAwesome;
font-style: normal;
font-weight: 900;
font-size: 2em;
speak: none;
display: inline-block;
text-decoration: inherit;
width: 1em;
margin: auto 0.4em auto 0.2em;
text-align: center;
font-variant: normal;
text-transform: none;
line-height: 1em;
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale
grid-column: 1;
grid-row: 1 / 3;
}
.info-box:before {
color: #00529B;
content: "\f05a";
}
.warning-box:before {
color: #7c4400;
content: "\f071";
}
.todo-box:before {
color: #006900;
content: "\f46c";
}
.stop-box:before {
color: #660000;
content: "\f057";
font-size: 3em;
}
.info-box {
background-color: rgba(0, 173, 255, 0.1);
}
.warning-box {
background-color: rgba(254, 204, 0, 0.2);
}
.todo-box {
background-color: rgba(12, 255, 0, 0.2);
}
.stop-box {
background-color: rgba(255, 0, 0, 0.2);
}
figure.stop-box figcaption {
font-size: 1.25em;
}

/* MESSAGE BOX END */

Resource Limits on the Linux Clients

2024-05-15T18:26:31Z

Phil: /* Number of Processes */

Our [[Linux Clients on the CS Undergrad Net|undergraduate Linux clients]] have system-enforced limits on some programs' resource usage. These limits are designed to prevent runaway programs from impacting other people's use of the shared computers. The limits should not affect your routine use of the systems; if you believe they're causing problems, please {{mailto|support|contact us}} to discuss the issue.

For some guidance on not exceeding these limits, please see our page on [[Preventing Your Programs From Overrunning Our Computers]].

== Memory Usage ==

The maximum memory (RAM) usage for a program is '''16 GiB'''. This limit applies only to the non-lab systems like ugradx and ugradz. The lab systems (ugrad1 through ugrad24) have no imposed limit, so it's possible for a buggy program to use up all of a system's RAM. If one lab computer is unresponsive, you can simply use a different one until we're able to fix the problem.

Note that this limit applies collectively to every program started from the ''same'' login session. Running one program that uses 16 GiB of RAM will hit the limit, but so will running eight programs that each use 2 GiB of RAM.

The limit also applies to memory reservations, whether or not they're actively being used. This means if you <code>mmap</code> a file, the entire file size will count towards this limit, even though blocks from the file are only paged into RAM on demand.

When your program hits the memory limit, any further attempts to allocate memory will fail. How that failure is manifested will depend on your programming language. In C, <code>malloc()</code> (or another memory allocation function) will return <code>NULL</code> and <code>errno</code> will be set to <code>ENOMEM</code>. In Python, a <code>MemoryError</code> exception will be raised. In Java, an <code>OutOfMemoryError</code> will be raised. For other languages, please consult the relevant documentation.

== Number of Processes ==

We have a limit of '''8192 process threads''' per account on each of our Linux clients.

Note that this limit applies to ''threads'', not just processes. Every process has at least one thread, but many processes run using more than one thread. You can see a list of all of your processes from the command line by running <kbd>ps x</kbd> . You can see a list of all your process threads by running <kbd>ps x -L</kbd> .

If the total number of running processes started from the same account is at the limit, attempts to start any additional processes will fail. How that failure is manifested will depend on the program that tried to launch the additional process. In C, <code>fork()</code> will return -1 and <code>errno</code> will be set to <code>EAGAIN</code>. A shell will typically give a message along the lines of "fork failed: Resource temporarily unavailable". In Python, you will typically get a <code>BlockingIOError</code> with a message of "[Errno 11] Resource temporarily unavailable". The Java exception raised will vary depending on the function having been called; for instance, <code>java.util.concurrent.ForkJoinPool.execute()</code> will raise <code>java.util.concurrent.RejectedExecutionException</code>.

== Maximum Process Runtime ==

Any program that has consumed more than '''1 week''' of ''accumulated CPU time'' will be terminated.

"Accumulated CPU time" is the total amount of time spent actively using a single CPU core. For example, a ''single''-threaded process running continuously for ''one'' week will accumulate ''one'' week of CPU time. Along the same lines, a process with ''seven'' threads, all running continuously, will accumulate ''seven'' seconds of CPU time for every actual elapsed second and, therefore, will accumulate ''one'' week of CPU time after running ''for one day''.

When a program exceeds the CPU time limit, it will be sent the <code>SIGXCPU</code> signal. If the program has no registered handler for that signal, it will simply stop running and its parent process will be notified. If it has a registered signal handler, the handler will be given about 30 seconds of runtime to clean up any resources before the process is ended. The process will be sent a new <code>SIGXCPU</code> signal every second until it exits. If it's still running after 30 seconds, the process will be forcibly terminated.

== Disk Usage ==

Ugrad systems are also subject to disk usage limits, as described on the [[Disk Quotas]] page.

If your disk usage is at its limit, attempts to write additional data to files in the <code>/home</code> filesystem will fail. In C, the <code>write()</code> function will return -1 and <code>errno</code> will be set to <code>EDQUOT</code> (or, in some cases, <code>ENOSPC</code>). Python will raise an <code>OSError</code> exception with message "[Errno 122] Disk quota exceeded". Java ''might not raise an exception'' and instead might just silently fail to write the data.

[[Category:Linux Clients]]

Resource Limits on the Linux Clients

2024-05-15T18:17:41Z

Phil: /* Memory Usage */ memory limit now only applies to compute systems

Our [[Linux Clients on the CS Undergrad Net|undergraduate Linux clients]] have system-enforced limits on some programs' resource usage. These limits are designed to prevent runaway programs from impacting other people's use of the shared computers. The limits should not affect your routine use of the systems; if you believe they're causing problems, please {{mailto|support|contact us}} to discuss the issue.

For some guidance on not exceeding these limits, please see our page on [[Preventing Your Programs From Overrunning Our Computers]].

== Memory Usage ==

The maximum memory (RAM) usage for a program is '''16 GiB'''. This limit applies only to the non-lab systems like ugradx and ugradz. The lab systems (ugrad1 through ugrad24) have no imposed limit, so it's possible for a buggy program to use up all of a system's RAM. If one lab computer is unresponsive, you can simply use a different one until we're able to fix the problem.

Note that this limit applies collectively to every program started from the ''same'' login session. Running one program that uses 16 GiB of RAM will hit the limit, but so will running eight programs that each use 2 GiB of RAM.

The limit also applies to memory reservations, whether or not they're actively being used. This means if you <code>mmap</code> a file, the entire file size will count towards this limit, even though blocks from the file are only paged into RAM on demand.

When your program hits the memory limit, any further attempts to allocate memory will fail. How that failure is manifested will depend on your programming language. In C, <code>malloc()</code> (or another memory allocation function) will return <code>NULL</code> and <code>errno</code> will be set to <code>ENOMEM</code>. In Python, a <code>MemoryError</code> exception will be raised. In Java, an <code>OutOfMemoryError</code> will be raised. For other languages, please consult the relevant documentation.

== Number of Processes ==

We have a limit of '''8192 process threads''' per account on each of our Linux clients.

Note that this limit applies to ''threads'', not just processes. Every process has at least one thread, but many processes run using more than one thread. You can see a list of all of your processes from the command line by running <kbd>ps x</kbd> . You can see a list of all your process threads by running <kbd>ps x -L</kbd> .

If the total number of running processes started from the same login session is at the limit, attempts to start any additional processes will fail. How that failure is manifested will depend on the program that tried to launch the additional process. In C, <code>fork()</code> will return -1 and <code>errno</code> will be set to <code>EAGAIN</code>. A shell will typically give a message along the lines of "fork failed: Resource temporarily unavailable". In Python, you will typically get a <code>BlockingIOError</code> with a message of "[Errno 11] Resource temporarily unavailable". The Java exception raised will vary depending on the function having been called; for instance, <code>java.util.concurrent.ForkJoinPool.execute()</code> will raise <code>java.util.concurrent.RejectedExecutionException</code>.

== Maximum Process Runtime ==

Any program that has consumed more than '''1 week''' of ''accumulated CPU time'' will be terminated.

"Accumulated CPU time" is the total amount of time spent actively using a single CPU core. For example, a ''single''-threaded process running continuously for ''one'' week will accumulate ''one'' week of CPU time. Along the same lines, a process with ''seven'' threads, all running continuously, will accumulate ''seven'' seconds of CPU time for every actual elapsed second and, therefore, will accumulate ''one'' week of CPU time after running ''for one day''.

When a program exceeds the CPU time limit, it will be sent the <code>SIGXCPU</code> signal. If the program has no registered handler for that signal, it will simply stop running and its parent process will be notified. If it has a registered signal handler, the handler will be given about 30 seconds of runtime to clean up any resources before the process is ended. The process will be sent a new <code>SIGXCPU</code> signal every second until it exits. If it's still running after 30 seconds, the process will be forcibly terminated.

== Disk Usage ==

Ugrad systems are also subject to disk usage limits, as described on the [[Disk Quotas]] page.

If your disk usage is at its limit, attempts to write additional data to files in the <code>/home</code> filesystem will fail. In C, the <code>write()</code> function will return -1 and <code>errno</code> will be set to <code>EDQUOT</code> (or, in some cases, <code>ENOSPC</code>). Python will raise an <code>OSError</code> exception with message "[Errno 122] Disk quota exceeded". Java ''might not raise an exception'' and instead might just silently fail to write the data.

[[Category:Linux Clients]]

Notices

2024-04-08T13:26:27Z

Phil: /* UNPLANNED CS IT SERVICE OUTAGES */

== CS IT STAFF AVAILABILITY ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 








== CS IT SERVICE OUTAGES (Unplanned & Planned)==






=== UNPLANNED CS IT SERVICE OUTAGES ===



{{outage
|time=Started Monday, April 8 around 7:30 am
|services=all CS services – FIXED
|summary=There was a power outage affecting Malone Hall and all of CS's servers running there.
|update=As of about 9:30 am, all CS services have been restored. Please email {{mailto|support}} if you encounter any problems.
|details=As of about 8:30, the power is back and we're working on restoring all of our services.
}}






=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.













== CS COMPUTING LAB AVAILABILITY ==

 

:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access.











:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.




















== AUDIO/VISUAL (A/V) OUTAGES ==
:None at this time.

[[Category:All]]

Notices

2024-04-08T13:15:00Z

Phil: /* UNPLANNED CS IT SERVICE OUTAGES */

== CS IT STAFF AVAILABILITY ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 








== CS IT SERVICE OUTAGES (Unplanned & Planned)==






=== UNPLANNED CS IT SERVICE OUTAGES ===



{{outage
|time=Started Monday, April 8 around 7:30 am
|services=all CS services; power outage
|summary=There was a power outage affecting Malone Hall and all of CS's servers running there.
|details=As of about 8:30, the power is back and we're working on restoring all of our services.
}}






=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.













== CS COMPUTING LAB AVAILABILITY ==

 

:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access.











:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.




















== AUDIO/VISUAL (A/V) OUTAGES ==
:None at this time.

[[Category:All]]

Linux Clients on the CS Grad/Research Net

2024-03-15T13:47:55Z

Phil:

The following is a list of Linux machines available for ''grad'' students, faculty, researchers, or staff on the ''Grad/Research Net''. These Linux machines can be accessed remotely via <code>ssh</code>, <code>scp</code>, or [[VNC]].

If you're working remotely, although you are welcome to log into any of our Linux clients, it's recommended that you use ''gradx.cs.jhu.edu'', as it can handle more concurrent use than any of the lab machines. All of the systems are identically configured, however, so anything you can do on one of them can be done on all of the others, too.

===NOTES===

* All Grad/Research Net systems end with '''''.cs.jhu.edu''''' as in, '''''masters1.cs.jhu.edu'''''

* [[:Category:Accounts|Accounts]], [[:Category:Mail|mail]], [[:Category:Webpages_and_Webservices|web]], and home directories on the Grad Net machines ''are different than'' those on the [[Linux Clients on the CS Undergrad Net|Ugrad]] systems.

* If you are unable to reach one of the systems below, please first see if it is part of an outage by visiting our [[Notices|''Notices'' page]], otherwise, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

* You are ''sharing these systems (CPU, memory, etc.) with other users,'' so please make sure that you do not overload the processors on these systems. When your are completed running your processes, please make sure you stop those processes.

* '''These Linux clients are primarily used for ''educational (coursework)'' purposes and for ''light research'' that does not impair CPU/memory/disk resources for others.''' Therefore, since you are sharing these systems (CPU, memory, disk space etc.) with other users, please make sure that you do not overload the processors on these systems nor store large files or large amounts of files on these systems. When your are completed running your processes, please make sure you stop those processes.
 

==Available Grad/Research Systems==

* '''masters1''' through '''masters16'''
**''Fedora 38'' Linux clients
** Malone Hall G-61.
** Each client has 8 cores (one quad-core Xeon E3-1240 CPU with hyperthreading) and 16 GiB RAM.
** Each system includes an NVIDIA-based GPU that may be used with CUDA and OpenCL (both already installed) for coursework.
** ''These systems are also available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

* '''gradx'''
**''Fedora 38'' Linux-based compute server.
** 24 cores (two 64-bit 6-core CPUs with hyperthreading), 288 GiB RAM
**''only available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

* '''gradz'''
**''Fedora 38'' Linux-based compute server.
** 32 CPU cores, 48 GiB RAM
**''only available remotely via [[Connecting to CS Systems with SSH|'''ssh''']] for logins or [https://en.wikipedia.org/wiki/Secure_copy '''scp'''] for secure file transfers.''

'''ssh key fingerprints''' for these machines can be found on the [[SSH Key Fingerprints for Grad and Ugrad Net Linux Computers]] page

[[Category:Linux Clients]]

SSH Keys for Grad and Ugrad net Linux Computers

2024-03-15T13:42:05Z

Phil: Changed redirect target from SSH Keys for Grad and Ugrad Net Linux Computers to SSH Key Fingerprints for Grad and Ugrad Net Linux Computers

#REDIRECT [[SSH Key Fingerprints for Grad and Ugrad Net Linux Computers]]

SSH Keys

2024-03-15T13:40:37Z

Phil: Changed redirect target from SSH Keys for Grad and Ugrad net Linux Computers to SSH Key Fingerprints for Grad and Ugrad Net Linux Computers

#REDIRECT [[SSH Key Fingerprints for Grad and Ugrad Net Linux Computers]]

Trouble Logging In Using VS Code With Remote SSH Plugin

2024-03-15T13:39:00Z

Phil:

==First Things First...==

If you are trying to log in to our CS Linux systems and are having issues doing so '''''and''''' are using '''Visual Studio Code''' with the '''Remote SSH Plugin''', then, before any further troubleshooting is done, please make sure you can first log in into one of our available [[:Category:Linux_Clients | Linux systems]] only with [[Connecting to CS Systems with SSH|SSH]] (i.e., without the use of VS Code.) If you are unable to log in with just ssh, and you are sure you are using the correct password, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] with as much detail as you can, including a screenshot of your login attempt, if you are able to.

==If ssh'ing Into your Linux Account Works, But, Logging In with VS Code Does Not...==

You ''might'' need to change the '''<code>remote.SSH.useFlock</code>''' setting. We've seen problems in the past that ''may'' have been related to VS Code's file locking mechanisms.

To enable '''flock''', you will need to do the following:

<ol>
<li> Exit all of your VS Code sessions (close all your VS Code windows) </li>
<li> Delete the .vscode-server directory in your grad or ugrad home directory. You can do that by SSHing to the Linux client you used with VS Code and running:
: <kbd>rm -fr ~/.vscode-server</kbd>
: If the directory doesn't exist, that's okay.</li>
<li> In VS Code, go to your settings, find the Remote SSH section, and uncheck '''Use Flock'''.</li>
<li> Try connecting to the CS Grad or Ugrad system again.</li>
</ol>

== If you receive the error: ''device or resource is busy''==

If you try to use <kbd>rm -fr ~/.vscode-server</kbd> (see above) and receive an error that it cannot be removed because the device or resource is busy, what should you do?

That ''device or resource is busy'' error message is usually because VS Code is still running ''somewhere''. Make sure you have exited VS Code ''completely'' before running the command.

If you're absolutely sure VS Code is not running, it's possible it left behind some processes on whichever one of our client systems you were connecting to. In that case, you can try running the following command on our Linux client to stop any running processes:

:<kbd>pkill -u $(id -u) -f vscode</kbd>

Note that this only helps if you run it on the same computer where the processes are running. If, for example, you connected to ugrad4 with VS Code but then ran the command on ugrad7, the processes would still be running on ugrad4.

==Still having issues? ==

If you're still having issues, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] with as much detail as you can. Please include the system you're connecting from, the system you're trying to connect to, and please make sure you can ssh into that system normally first before trying it with VS Code.

[[Category:Troubleshooting]]
[[Category:SSH]]
[[Category:Software]]

Linux Clients on the CS Undergrad Net

2024-03-15T13:33:14Z

Phil:

The following is a list of Linux machines available for students, faculty, researchers, or staff. These Linux machines can be accessed remotely via [[Connecting to CS Systems with SSH|<code>ssh</code>]], <code>scp</code> or [[VNC]].

If you're working remotely, although you are welcome to log into '''''any''''' of our Linux clients, it's recommended that you try ''ugradx.cs.jhu.edu'' first, as it can handle more concurrent use than any of the lab machines. All of the systems are identically configured, however, so ''anything you can do on one of them can be done on all of the others'', too.

===NOTES===

:* All Ugrad Net systems end with '''''.cs.jhu.edu''''' as in, '''''ugrad1.cs.jhu.edu'''''

:* [[:Category:Accounts|Accounts]], [[:Category:Mail|mail]], [[:Category:Webpages_and_Webservices|web]], and home directories on the Ugrad Net machines ''are different than'' those on the [[Linux Clients on the CS Grad/Research Net|Grad]] systems.

:* Ugrad Net linux clients have [[Disk Quotas|disk quotas]] on the Ugrad home directories.

:* If you are unable to reach one of the systems below, please first see if it is part of an outage by visiting our [[Notices|''Notices'' page]], otherwise, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

:* '''These Linux clients are primarily used for ''educational (coursework)'' purposes.''' Therefore, since you are sharing these systems (CPU, memory, etc.) with other users, please make sure that you do not overload the processors on these systems. When your are completed running your processes, please make sure you stop those processes.

 

==Available Ugrad Linux Systems==

* '''ugrad1''' through '''ugrad24'''
**standard ''Fedora 38'' Linux clients
** split between both [[:Category:Labs|CS Undergraduate Labs (Malone 122 and G61.)]]
** Each client has 8 cores (one 4-core i7 CPU with hyperthreading) and 16 GiB RAM.
** Each system includes an NVIDIA-based GPU that may be used with CUDA and OpenCL (already installed) for coursework.
** ''These systems are also available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers.''

* '''ugradx'''
**''Fedora 38'' Linux-based compute server.
** 24 cores (two 64-bit 6-core CPUs with hyperthreading), 288 GiB RAM
**''only available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers.''

* '''ugradz'''
** ''Fedora 38'' Linux-based compute server.
** 32 CPU cores, 48 GiB RAM.
** ''Only available remotely via [[Connecting to CS Systems with SSH|SSH]] for logins or [https://en.wikipedia.org/wiki/Secure_copy scp] for secure file transfers.''
** Only accessible from the Hopkins network or VPN; not accessible directly from the Internet.

'''ssh key fingerprints''' for these machines can be found on the [[SSH Key Fingerprints for Grad and Ugrad Net Linux Computers]] page

[[Category:Linux Clients]]

Resource Limits on the Linux Clients

2024-03-14T13:09:29Z

Phil: /* Memory Usage */

Our [[Linux Clients on the CS Undergrad Net|undergraduate Linux clients]] have system-enforced limits on some programs' resource usage. These limits are designed to prevent runaway programs from impacting other people's use of the shared computers. The limits should not affect your routine use of the systems; if you believe they're causing problems, please {{mailto|support|contact us}} to discuss the issue.

For some guidance on not exceeding these limits, please see our page on [[Preventing Your Programs From Overrunning Our Computers]].

== Memory Usage ==

The maximum memory (RAM) usage for a program is '''4 GiB'''.

Note that this limit applies collectively to every program started from the ''same'' login session. Running one program that uses 4 GiB of RAM will hit the limit, but so will running eight programs that each use 512 MiB of RAM.

The limit also applies to memory reservations, whether or not they're actively being used. This means if you <code>mmap</code> a file, the entire file size will count towards this limit, even though blocks from the file are only paged into RAM on demand.

When your program hits the memory limit, any further attempts to allocate memory will fail. How that failure is manifested will depend on your programming language. In C, <code>malloc()</code> (or another memory allocation function) will return <code>NULL</code> and <code>errno</code> will be set to <code>ENOMEM</code>. In Python, a <code>MemoryError</code> exception will be raised. In Java, an <code>OutOfMemoryError</code> will be raised. For other languages, please consult the relevant documentation.

== Number of Processes ==

We have a limit of '''8192 process threads''' per account on each of our Linux clients.

Note that this limit applies to ''threads'', not just processes. Every process has at least one thread, but many processes run using more than one thread. You can see a list of all of your processes from the command line by running <kbd>ps x</kbd> . You can see a list of all your process threads by running <kbd>ps x -L</kbd> .

If the total number of running processes started from the same login session is at the limit, attempts to start any additional processes will fail. How that failure is manifested will depend on the program that tried to launch the additional process. In C, <code>fork()</code> will return -1 and <code>errno</code> will be set to <code>EAGAIN</code>. A shell will typically give a message along the lines of "fork failed: Resource temporarily unavailable". In Python, you will typically get a <code>BlockingIOError</code> with a message of "[Errno 11] Resource temporarily unavailable". The Java exception raised will vary depending on the function having been called; for instance, <code>java.util.concurrent.ForkJoinPool.execute()</code> will raise <code>java.util.concurrent.RejectedExecutionException</code>.

== Maximum Process Runtime ==

Any program that has consumed more than '''1 week''' of ''accumulated CPU time'' will be terminated.

"Accumulated CPU time" is the total amount of time spent actively using a single CPU core. For example, a ''single''-threaded process running continuously for ''one'' week will accumulate ''one'' week of CPU time. Along the same lines, a process with ''seven'' threads, all running continuously, will accumulate ''seven'' seconds of CPU time for every actual elapsed second and, therefore, will accumulate ''one'' week of CPU time after running ''for one day''.

When a program exceeds the CPU time limit, it will be sent the <code>SIGXCPU</code> signal. If the program has no registered handler for that signal, it will simply stop running and its parent process will be notified. If it has a registered signal handler, the handler will be given about 30 seconds of runtime to clean up any resources before the process is ended. The process will be sent a new <code>SIGXCPU</code> signal every second until it exits. If it's still running after 30 seconds, the process will be forcibly terminated.

== Disk Usage ==

Ugrad systems are also subject to disk usage limits, as described on the [[Disk Quotas]] page.

If your disk usage is at its limit, attempts to write additional data to files in the <code>/home</code> filesystem will fail. In C, the <code>write()</code> function will return -1 and <code>errno</code> will be set to <code>EDQUOT</code> (or, in some cases, <code>ENOSPC</code>). Python will raise an <code>OSError</code> exception with message "[Errno 122] Disk quota exceeded". Java ''might not raise an exception'' and instead might just silently fail to write the data.

[[Category:Linux Clients]]

Resource Limits on the Linux Clients

2024-03-14T13:05:46Z

Phil: /* Number of Processes */

Our [[Linux Clients on the CS Undergrad Net|undergraduate Linux clients]] have system-enforced limits on some programs' resource usage. These limits are designed to prevent runaway programs from impacting other people's use of the shared computers. The limits should not affect your routine use of the systems; if you believe they're causing problems, please {{mailto|support|contact us}} to discuss the issue.

For some guidance on not exceeding these limits, please see our page on [[Preventing Your Programs From Overrunning Our Computers]].

== Memory Usage ==

The maximum memory (RAM) usage for a program is '''4 GiB'''.

Note that this limit applies collectively to every program started from the ''same'' login session. Running one program that uses 4 GiB of RAM will hit the limit, but so will running eight programs that each use 512 MiB of RAM.

When your program hits the memory limit, any further attempts to allocate memory will fail. How that failure is manifested will depend on your programming language. In C, <code>malloc()</code> (or another memory allocation function) will return <code>NULL</code> and <code>errno</code> will be set to <code>ENOMEM</code>. In Python, a <code>MemoryError</code> exception will be raised. In Java, an <code>OutOfMemoryError</code> will be raised. For other languages, please consult the relevant documentation.

== Number of Processes ==

We have a limit of '''8192 process threads''' per account on each of our Linux clients.

Note that this limit applies to ''threads'', not just processes. Every process has at least one thread, but many processes run using more than one thread. You can see a list of all of your processes from the command line by running <kbd>ps x</kbd> . You can see a list of all your process threads by running <kbd>ps x -L</kbd> .

If the total number of running processes started from the same login session is at the limit, attempts to start any additional processes will fail. How that failure is manifested will depend on the program that tried to launch the additional process. In C, <code>fork()</code> will return -1 and <code>errno</code> will be set to <code>EAGAIN</code>. A shell will typically give a message along the lines of "fork failed: Resource temporarily unavailable". In Python, you will typically get a <code>BlockingIOError</code> with a message of "[Errno 11] Resource temporarily unavailable". The Java exception raised will vary depending on the function having been called; for instance, <code>java.util.concurrent.ForkJoinPool.execute()</code> will raise <code>java.util.concurrent.RejectedExecutionException</code>.

== Maximum Process Runtime ==

Any program that has consumed more than '''1 week''' of ''accumulated CPU time'' will be terminated.

"Accumulated CPU time" is the total amount of time spent actively using a single CPU core. For example, a ''single''-threaded process running continuously for ''one'' week will accumulate ''one'' week of CPU time. Along the same lines, a process with ''seven'' threads, all running continuously, will accumulate ''seven'' seconds of CPU time for every actual elapsed second and, therefore, will accumulate ''one'' week of CPU time after running ''for one day''.

When a program exceeds the CPU time limit, it will be sent the <code>SIGXCPU</code> signal. If the program has no registered handler for that signal, it will simply stop running and its parent process will be notified. If it has a registered signal handler, the handler will be given about 30 seconds of runtime to clean up any resources before the process is ended. The process will be sent a new <code>SIGXCPU</code> signal every second until it exits. If it's still running after 30 seconds, the process will be forcibly terminated.

== Disk Usage ==

Ugrad systems are also subject to disk usage limits, as described on the [[Disk Quotas]] page.

If your disk usage is at its limit, attempts to write additional data to files in the <code>/home</code> filesystem will fail. In C, the <code>write()</code> function will return -1 and <code>errno</code> will be set to <code>EDQUOT</code> (or, in some cases, <code>ENOSPC</code>). Python will raise an <code>OSError</code> exception with message "[Errno 122] Disk quota exceeded". Java ''might not raise an exception'' and instead might just silently fail to write the data.

[[Category:Linux Clients]]