CS IT Support Wiki - User contributions [en]

Lab And Other Website Hosting

2026-06-03T14:04:17Z

Pip: /* File Storage Method */

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

:Note that with this approach, if your account is removed (see [[CS Account Removal]] for the policies related to that process), the website will be removed at the same time.

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

:The website will remain for as long there is someone affiliated with the department who is responsible for the website's maintenance.

[[Category:Webpages and Webservices]]

Available Printers

2026-06-02T16:08:07Z

Pip:

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 M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone 316 (Masters/MSSI Lab) ||HP LaserJet M610||mh316prt.cs.jhu.edu||mh316prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) '''''{{red|NEW!}}'''''||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| 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.''|| {{red|('''''NEW'' ''HP'' copier, replaced the old ''Canon'' Copier''')}}
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.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|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 352 (''{{red|'''NEW'''}} printer in the 3rd floor Kitchen Area, as of 5/28/25'') ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==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. (Sometimes, only the full hostname will work if the IP address doesn't.) 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. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==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] 

* 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]]

Obtaining CS Computer Accounts

2026-06-02T16:07:30Z

Pip:

:{{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. ''

* All CS accounts '''must''' be pre-approved by a CS faculty member from this [https://www.cs.jhu.edu/faculty CS Faculty member list] '''''unless'''''...
** a student is a direct CS student (i.e., a CS PhD, CS Masters, or CS Undergrad student)
** a student is taking a CS course taught by a [https://www.cs.jhu.edu/faculty CS Faculty member] and is on a course list provided to CS IT Support directly by the faculty member or by CS Academic Advising.
** the account applicant has some other CS affiliation and will therefore need approval by CS Dept administration.

 
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 Henneman''' 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 Henneman''') 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 NOTE 1:''''' When you email the account form to us, please have the '''''Subject Line''''' include '''''your name''''' and the words '''''"CS Account Form"''''}}
:::{{red|'''''IMPORTANT Note 2:''''' When you send your filled-out and signed account form to support@cs.jhu.edu, if possible, '''''please send it from a JHU-based email address''''', to make sure it will get to our team. Obviously, if you don't have a JHU-based email address, that's ok too... just send from an email address you have. But, again, we prefer it coming from a JHU-based email address to ensure its delivery to us.}}

::'''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]]

Screenlocking Policy in the CS Ugrad Labs and Masters Lab

2026-06-02T16:06:00Z

Pip:

To all CS Grad or Ugrad students who use either the MH-122 CS Ugrad Lab/Collaboration Room or the 316 CS Masters Lab Lab Linux or Windows computers:

* If you need to leave one of the Linux or Windows computers in those labs ''for more than one hour'', you need to '''log out''' of it '''''instead of screenlocking''''' it, to allow others to use the machine.

* An hour should give you plenty of time to use the restroom or pick up lunch, etc. Do not screenlock the computer if you have to go to a class that is more than an hour long. Please logout instead.

* If we see that your machine is screenlocked (or if it is brought to our attention), and it has been more than an hour, ''we will have the option to unlock it and log you out'' (without notice), so that others can gain access to the computer.

* If there is a specific program that you '''must''' run directly at the desktop (instead of ssh'ing in, etc.), and you need to absolutely lock the screen for more than an hour for this purpose, you should contact us ([mailto:support@cs.jhu.edu support@cs.jhu.edu]) ahead of time to make arrangements.

We are hoping not to have to impose an automatic unlock-and-logout software system on these machines, so, please help out your fellow students by only screenlocking your machine if you'll be away for less than an hour.

[[Category:Labs]]

Resetting a CS Lab Printer That Hangs

2026-06-02T16:05:41Z

Pip:

CS Labs MH 122 and MH 316 each house an HP LaserJet 4350 printer.

Per the [https://support.cs.jhu.edu/wiki/Available_Printers available printers list]...

:MH-122's printer is called '''mh122prt'''

::and

:MH 316's printer is called '''mh316prt'''

If you notice either of these printers are hung up ''(not related to a printer jam)'', it could be an incompatible document or a document that triggers an '''error 49.4C02''' or something similar might have occurred.

Generally, to unhang these printers, try the following steps:

* Power off the printer with the power switch on the right side of the printer.

* Wait 1 minute. (Helps the internal memory clear out.)

* Power the printer back on and wait until the screen shows ''Ready''

:'''IMPORTANT NOTE:''' Try not to turn off a printer while it is in the middle of printing. Perhaps hit the menu button and find a "Cancel Print"-type of option. Otherwise, the printer might jam.

If the printer still doesn't work, please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] with a full description of the problem (including which CS Lab room # the printer resides in.)

[[Category:Printing]]

Computing Rules and Policies for CS IT Services and Computing Labs

2026-06-02T16:04:46Z

Pip:

==CS I.T.’s Computing Services and Computing Labs: Computing Rules and Policies==

The following applies to the [[:Category:Labs | CS Grad & Undergrad Computing Labs]] (MH 122 and MH 316) and their computers. However, where appropriate, these rules and policies also apply to the general computing services provided by CS I.T. The computing labs are here to meet computing needs of students taking Computer Science courses that have specific resource needs not offered by the rest of the university computers and labs. We accomplish this goal by providing the tools needed to meet their academic goals in a positive educational environment.

'''NOTE: THE CS UGRAD & GRAD LABS (Malone 122 & MH 316) ARE UNDER SURVEILLANCE FOR YOUR SAFETY, AS WELL AS FOR THE PROTECTION OF THE LAB EQUIPMENT.'''

==RULES OF USE FOR THE CS GRAD/UGRAD LABS, THEIR RELATED COMPUTERS, & GENERAL CS IT Services==

# Masks are now '''''optional''''' for all those using our labs. (updated Aug, 2022)
#''Eating'' is '''no longer allowed''' in the lab.
# Absolutely no commercial software is to be installed on any of the CS Grad/Ugrad Lab-related computers, except by the CS IT Support Staff.
# Any user-installed free/shareware must be installed within user’s own home directory and removed when done.
# Tampering with current setups/configurations of the CS Grad or Ugrad Lab-related computers and furniture is prohibited and will not be tolerated.
# People doing work for Computer Science courses will have priority over anyone else using the CS Grad or Ugrad Lab machines.
# No foreign hardware (with the exception of USB thumb drives) is to be used with the CS Grad or Ugrad Lab machines or wall ports without the permission of the CS IT Support Staff.
# No networked games (except for those required for class assignments on game software-writing) are to be played on any of the CS Grad or Ugrad lab computers. We define networked games as any real-time, graphics-based game played between two or more computers.
# Admission to the CS Grad and Undergrad Labs is granted only to those persons who have legitimate Computer Science Department needs. These persons will have J-Card access.
# Students will not allow any non-authorized persons into the CS Grad/Undergrad Labs. Only those who have Computer Science-authorized J-Card access will be allowed into these labs. All CS users should swipe their J-Card for entry to the CS Labs.
# No bicycles allowed in the Computer Science Masters Lab or Undergrad Labs for any reason. Use the bicycle racks outside the building.
# Users will clean up after themselves in the CS Computing Labs.
# No propping the CS Undergrad Lab doors open unless authorized to do so by the CS office or CS IT staff.
# The CS Ugrad Lab (Malone 122) is primarily for Undergrad students and for Grad/Masters course work as required. However, Grad/Masters students should utilize the Masters Lab (Malone 316) instead, whenever possible, and only use the Ugrad Lab computers as required. (Ugrad computers have home directory [[Disk Quotas | disk quotas]]. Grad/Masters computers do not.)
# Users will not give out their passwords, nor will they allow others to use their personal accounts.
# Course-specific Linux accounts issued to students will be deleted upon the completion of the course. This rule applies to Teaching Assistant accounts as well. If you need a personal Linux account, please apply for one. Details on the CS IT Support Wiki in the [https://support.cs.jhu.edu/wiki/Category:Accounts Accounts] category.
# Users will adhere at all times to any and all policies with regard to [[Disk Quotas | disk quotas]]. Users of the ''Ugrad Net'' Linux computers are limited to '''10 gb''' of home directory disk space. Exceptions will be made on a case-by-case basis by e-mailing [mailto:support.cs.jhu.edu support@cs.jhu.edu]
# Any action which violates local, state, and/or federal laws and/or which violates JHU's Computing Ethics Policy is strictly prohibited.
# Lock or logoff all machines before leaving the CS Grad or Ugrad Labs or any CS IT-managed system.
# Locking any computing lab system for more than one hour (without prior authorization from CS IT Support) or leaving any machine that you are logged into unattended (and unlocked) by you is not permitted! You may be logged off regardless of what you are working on, and your account may be disabled. This is for both security purposes and to allow others to use the lab machines. See [[Screenlocking_Policy_in_the_CS_Ugrad_Lab_and_Masters'_Office|Screenlocking Policy in the CS Ugrad Labs and Masters Lab]] for more details

'''FAILURE TO COMPLY WITH THE ABOVE RULES MAY RESULT IN DENIAL OF ACCESS TO THE DEPARTMENTAL COMPUTING RESOURCES.'''

'''CASES INVOLVING VIOLATION OF APPLICABLE LAWS OR UNIVERSITY POLICIES MAY BE PROSECUTED TO THE FULLEST EXTENT OF THE LAW. 

[[Category:Labs]]

Networking at CS - Overview

2026-06-02T16:04:00Z

Pip:

:There are three main networks in CS at Malone Hall. They are:

::'''Public CS Grad/Research Net''' (128.220.35.x) - Uses IP addresses that are ''accessible from the Internet''.

::'''Private CS Grad/Research Net''' (10.161.159.x) - Uses IP addresses that are ''only accessible from within the Hopkins network (and Hopkins VPN)''.

::'''CS Undergrad Net''' (128.220.224.x) - Uses IP addresses that are ''accessible from the Internet''

:The Public and Private Grad/Research Nets are only ''physically'' accessible via network jacks in Malone Hall in CS work areas, except for the CS Undergrad Labs (Malone Hall room 122). The CS Undergrad Net is only ''physically'' accessible via network jacks in the CS Undergrad Lab. (Of course, you can access the Grad/Research Nets and the Ugrad Net systems remotely from other systems.)

:Not all network jacks are active. If you need to use a network jack but are not getting any network connection at all from it, please {{mailto|support|email us}} to ask for it to be activated.

 

==Network Jacks (Wallports) In Malone Hall==

:Network jacks may be located be under floor panels via access doors on the floor or they might be located on the wall, depending upon where you're located. Each network jack is identified with a floor number and jack number. (It is very important that any correspondence with CS IT Support or JHU Networking about a network jack include the full jack number.)

:(For those grad students working on the third floor of Malone, you might see that your floor panel access door is located under a slightly raised cabinet where the floor access door might be difficult to reach. For your convenience, there are network cables already coming out of those specific floor panels, and each of those cables is labeled with the port number.)

:Each active network jack in your Malone ''office'' will go to exactly one of those two Grad/Research networks (Public ''or'' Private Grad Net), so care will be needed to connect your computers into appropriate jacks. Again, if a jack is not currently active, you can {{mailto|support|email us}} to have it activated.

:Any given network jack can be changed from one network to the other (i.e., ''public to private'' or ''private to public'') with relatively little difficulty with an emailed request to [mailto:support@cs.jhu.edu CS Support]. We will pass on your request to JHU Networking. JHU Networking will be administering the network configurations; here is their current plan:

:* '''Even-numbered jacks''', by default, are connected to the '''''Public''''' CS Grad network, 128.220.35.x
:* '''Odd-numbered jacks''', by default, are be connected to the '''''Private''''' CS Grad network, 10.161.159.x

:'''Note 1:''' All network jacks in the CS Undergrad Lab are part of the CS Undergrad Net (128.220.224.x)

:'''Note 2:''' If you have a system that will reside in the G29 Malone ''server room'' instead, please contact CS Support, and we will help arrange your system's connections to the appropriate network, as there are no wallports in G-29.

 

== ''Public'' CS Grad/Research Network Details ==

:The '''"Public" CS Grad/Research Net''' uses IP addresses that are directly accessible from the Internet. It is useful for servers that need to be widely accessible or for systems that people need to connect to without going through the Hopkins VPN. (For example, if you need to ssh into your work machine from out on the Internet, your work machine needs a public IP address.)

:Systems on the Public Grad Net can freely communicate with systems elsewhere on the Hopkins network, including systems on the Private CS Grad Net.

:In order to set up a system on the Public Grad Net, you will need to follow the instructions at [[Requesting a Static IP Address on the CS Network]] and indicate in your request that the IP address will be public. There is '''no''' ''dynamic IP address service'' available on the Public network.

===Public IP Security Considerations===

:Please keep in mind that a system with a Public IP is exposed to the Internet. That means that '''''your system is open and vulnerable to access attempts from the outside.''''' If you're the only one who will access your system from the outside, please consider a Private IP instead, and use the VPN to put you into the JHU network so that you can access your system. If you have several outside people needing access to your system, then, yes, a Public IP is probably needed.

:And, because systems on the Public Grad Net are exposed to the Internet, they are expected to be managed in a way that preserves their security and the security of the Hopkins network. The JHU Network Security Team (part of the [http://www.it.jhu.edu/ IT@JH] group, ''not'' CS) may periodically perform security scans of systems on the Public Grad Net. If they determine that there are security problems with a system, they may disable all Internet access for that system until the problems are resolved.

===Opening Ports on the JHU Firewall===

:Some systems with a CS '''public''' IP might might want to be accessible through JHU's perimeter firewall. (CS does not maintain a departmental firewall) To have a port opened on the JHU firewall, please see: [https://support.cs.jhu.edu/wiki/Requesting_Open_Ports_on_the_JHU_Firewall Requesting Open Ports on the JHU Firewall]

 

== ''Private'' CS Grad/Research Network Details==

:The '''"Private" CS Grad/Research Net''' uses IP addresses that can only be directly accessed from either the Hopkins network or the Hopkins VPN. It is useful for systems that do not need to be accessed from the Internet, like desktop computers or printers. The private addressing used on this network helps keep the systems a little more secure, since no one on the Internet can contact them directly.

:You can connect your system to the Private Grad Net by following the instructions at [[Connecting to the CS Grad Nets]]. By default, you will receive a ''dynamic IP address''. If you need a ''static IP address'', follow the instructions at [[Requesting a Static IP Address on the CS Network]], making sure to specify that you want a ''private static IP address''.

 

==''CS Undergrad Network'' Details==

:The '''CS Undergrad Network''' is only available via wall and tabletop network jacks in Malone Hall Room 122 (the CS Collaboration Room). To connect to the CS Undergrad Net, follow the instructions at [[Connecting to the CS Ugrad Net]]. Your computer will receive a dynamic IP address. There are no static IP addresses granted for the CS Ugrad Net.

 

== Requesting a Static IP Address ==

:If you need to request a ''static IP address'', please follow the instructions at [[Requesting a Static IP Address on the CS Network]].

 

== DNS Servers to use when on the CS Network ==

:Primary DNS: '''10.200.1.1'''

:Secondary DNS: '''10.200.2.2'''

:DHCP-provided CS IPs will automatically receive the above DNS servers.

 

== General Configuration Notes ==

===Public Network (128.220.35.x, even-numbered ports)===

:Subnet Mask: '''255.255.255.0'''

:Gateway: '''128.220.35.1'''

===Private Network (10.161.159.x, odd-numbered ports)===

:Subnet Mask: '''255.255.255.0'''

:Gateway: '''10.161.159.1'''

 

== Security Note ==

:All computers that connect to the CS Grad/Research or Undergrad net should be at their latest security levels and should be configured to prevent viruses, etc. For antivirus software, please see the [http://it.jhu.edu/antivirus JHU Antivirus webpage].

[[Category:Networking]]

Connecting to the CS Ugrad Net

2026-06-02T16:02:53Z

Pip:

Since CS does not maintain [https://support.cs.jhu.edu/wiki/Wireless_Networking wireless connections], if you will not be connecting to JHU's '''''hopkins''''' or '''''eduroam''''' wireless system, then, you will need to use a Cat 5 or Cat 6 cable for your network connection to connect to the ''CS Undergrad Net''.

'''DHCP''' service with dynamic IP addresses on the CS Ugrad Net is available from:

:* the table-mounted and wall-based network jacks within the Malone 122 Undergraduate computer lab

'''NOTE:''' ''Static IP'' addresses are '''not''' available on the CS Ugrad Net.

 

==Obtaining a ''DHCP'' IP Address on the CS Undergrad Net==

#Set your computer to use '''DHCP'''
#Plug your computer into a tabletop or wall-based network jack in ''MH 122''
#Depending on your operating system, you may have to reboot your computer at this point
#You should now have a dynamically-assigned IP address on the CS Undergrad Net

:'''NOTE:''' Sometime in the future, we will be using a different method for providing a dynamically-assigned IP, but for now, the procedure above works.



[[Category:Networking]]

Available Printers

2026-06-02T15:41:50Z

Pip:

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 M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone 316 (Masters/MSSI Lab) ||HP LaserJet M610||mh316prt.cs.jhu.edu||mh316prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) '''''{{red|NEW!}}'''''||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| 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.''|| {{red|('''''NEW'' ''HP'' copier, replaced the old ''Canon'' Copier''')}}
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.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|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 352 (''{{red|'''NEW'''}} printer in the 3rd floor Kitchen Area, as of 5/28/25'') ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==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. (Sometimes, only the full hostname will work if the IP address doesn't.) 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. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==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] 

* 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]]

Notices

2026-05-29T19:26:07Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

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

* The CS IT Support staff operates out of 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 are 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.
* 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 ===



{{outage
|services=masters10
|time=Friday, May 29
|summary=masters10 is only available remotely for the moment. Please use a different lab computer if you need to use one in person.
}}
 

=== PLANNED CS IT SERVICE OUTAGES ===


:'''WHAT''': JHU's Chilled water outage could potentially affect our CS IT Services.

:'''WHEN:''' Friday, 5/29, 10pm thru Saturday, 5/30, 2am.

:'''DETAILS:'''

::JHU Facilities just announced to us that they will be performing another chilled water outage Friday, (5/29, from 10pm until Saturday, 5/30, at 2 am. (4 hours.)

::When this happens, our CS server room loses cooling ability, and that can adversely affect our server hardware. Without cooling, we may need to resort to shutting down a variety of our servers (and their services) to protect them from overheating.

::If you notice any of our CS IT services (login, mail, web, MySQL, etc..) become unavailable Friday evening into Saturday, it might be due to the cooling outage.



______,


 

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




:'''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 10 through Wednesday, August 12. And the computers in that room will be moved from there to remote-only on June 10. On Thursday, August 13, the room becomes available to CS again, with ugrad1 through ugrad12 and the lab's printer returning to the room on sometime during August 12 and August 13.

::'''NOTES:'''

:* The MH 122 Linux systems, ugrad1 through ugrad12, will continue to be available, '''''but only remotely via ssh''''' ''until'' they are moved back into MH-122 in August.

:::On 6/10, we will be transferring the computers from MH-122.

:::On 8/12 and/or 8/13, we will be transferring the computers back to MH-122.

:::During the transfer times, ugrad1 through ugrad12 may not be available.

:*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, but it too should be back in MH-122 on 8/12 or 8/13.

:* The G61 Masters/Ugrad Lab will be closed permanently. Please see the G61 Lab section notices below...


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access '''but''' '''''closing permanently''''' '''on June 1, 2026'''.

::After many years of operating a CS Masters Lab and a 2nd Ugrad Lab in Malone G61, we will be closing G61 (as it's being repurposed.) G61 will be no longer be a CS IT-administered computer lab starting '''Monday, June 1, 2026.'''

::For the CS Masters students, our new plan is to make access to the masters/grad Linux systems fully remote. We will still have masters lab space (a collaborative space), but that is being relocated to Malone Hall 316 (sharing with the MSSI lab), and without the masters Linux computers available as desktops, as they had been in G61. (Well, for a short period of time, we will plan to have four of the masters systems --masters1 thru masters4-- configured as desktops and remotely-accessible in MH 316. Eventually, though, those desktops will go away.)

::For our CS Undergraduate students, MH-122 will become our only CS Ugrad computing lab, with the twelve active Ugrad systems, Ugrad1 through Ugrad12 remaining as desktops in that lab. So, that room/lab will remain configured as it currently is. The other Ugrad systems, ugrad13 through ugrad24 are being retired.

::Most CS students have already been accessing the masters and ugrad Linux computers remotely. To compensate for the loss of those computers and their computing power, we plan to bring two new, powerful remotely-accessible compute servers online, one for the CS grad/masters students and one for the CS undergrad students, similar to gradx and ugradx. And, we're hoping to have them in place by the beginning of the Fall semester.

::In this new paradigm for CS academic computing, you'll be using your own computer to access our systems remotely, via ssh and vnc (vnc will allow access to a Linux desktop), without console access as had been the case in G61 (except, as stated, MH-122 will continue to operate its Linux desktops that are also remotely accessible.()

::'''NOTES:'''

:* All of the G61 Linux computers (masters and ugrad) will be shut down the morning of June 1.

:* Four of the masters Linux computers (masters1 thru masters4) will be moved into MH 316, and we hope to have them running that day, but they could be delayed.

:* The current G61 printer will also be moved into MH 316 on June 1 or shortly thereafter.

:* The dept will be working on a plan to transfer J-Card access from MH G61 to MH 316. If there are issues, we will let you know.

:* MH 316 also houses the MSSI lab, and those MSSI computers will '''not''' be accessible to CS students (unless you are part of the MSSI program.)

 

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

[[Category:All]]

Notices

2026-05-22T16:55:12Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

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

* The CS IT Support staff operates out of 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 are 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.
* 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 ===



{{outage
|services=several lab machines
|time=Friday, May 22
|summary=Several lab machines did not return to operation after a power outage. Those systems include ugrad3, ugrad7, and masters10. Please use other Linux clients until those have their issues addressed.
}}
 

=== PLANNED CS IT SERVICE OUTAGES ===

:None at this time.





 

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




:'''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 10 through Wednesday, August 12. And the computers in that room will be moved from there to remote-only on June 10. On Thursday, August 13, the room becomes available to CS again, with ugrad1 through ugrad12 and the lab's printer returning to the room on sometime during August 12 and August 13.

::'''NOTES:'''

:* The MH 122 Linux systems, ugrad1 through ugrad12, will continue to be available, '''''but only remotely via ssh''''' ''until'' they are moved back into MH-122 in August.

:::On 6/10, we will be transferring the computers from MH-122.

:::On 8/12 and/or 8/13, we will be transferring the computers back to MH-122.

:::During the transfer times, ugrad1 through ugrad12 may not be available.

:*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, but it too should be back in MH-122 on 8/12 or 8/13.

:* The G61 Masters/Ugrad Lab will be closed permanently. Please see the G61 Lab section notices below...


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access '''but''' '''''closing permanently''''' '''on June 1, 2026'''.

::After many years of operating a CS Masters Lab and a 2nd Ugrad Lab in Malone G61, we will be closing G61 (as it's being repurposed.) G61 will be no longer be a CS IT-administered computer lab starting '''Monday, June 1, 2026.'''

::For the CS Masters students, our new plan is to make access to the masters/grad Linux systems fully remote. We will still have masters lab space (a collaborative space), but that is being relocated to Malone Hall 316 (sharing with the MSSI lab), and without the masters Linux computers available as desktops, as they had been in G61. (Well, for a short period of time, we will plan to have four of the masters systems --masters1 thru masters4-- configured as desktops and remotely-accessible in MH 316. Eventually, though, those desktops will go away.)

::For our CS Undergraduate students, MH-122 will become our only CS Ugrad computing lab, with the twelve active Ugrad systems, Ugrad1 through Ugrad12 remaining as desktops in that lab. So, that room/lab will remain configured as it currently is. The other Ugrad systems, ugrad13 through ugrad24 are being retired.

::Most CS students have already been accessing the masters and ugrad Linux computers remotely. To compensate for the loss of those computers and their computing power, we plan to bring two new, powerful remotely-accessible compute servers online, one for the CS grad/masters students and one for the CS undergrad students, similar to gradx and ugradx. And, we're hoping to have them in place by the beginning of the Fall semester.

::In this new paradigm for CS academic computing, you'll be using your own computer to access our systems remotely, via ssh and vnc (vnc will allow access to a Linux desktop), without console access as had been the case in G61 (except, as stated, MH-122 will continue to operate its Linux desktops that are also remotely accessible.()

::'''NOTES:'''

:* All of the G61 Linux computers (masters and ugrad) will be shut down the morning of June 1.

:* Four of the masters Linux computers (masters1 thru masters4) will be moved into MH 316, and we hope to have them running that day, but they could be delayed.

:* The current G61 printer will also be moved into MH 316 on June 1 or shortly thereafter.

:* The dept will be working on a plan to transfer J-Card access from MH G61 to MH 316. If there are issues, we will let you know.

:* MH 316 also houses the MSSI lab, and those MSSI computers will '''not''' be accessible to CS students (unless you are part of the MSSI program.)

 

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

[[Category:All]]

Networking at CS - Overview

2026-05-01T19:22:04Z

Pip:

:There are three main networks in CS at Malone Hall. They are:

::'''Public CS Grad/Research Net''' (128.220.35.x) - Uses IP addresses that are ''accessible from the Internet''.

::'''Private CS Grad/Research Net''' (10.161.159.x) - Uses IP addresses that are ''only accessible from within the Hopkins network (and Hopkins VPN)''.

::'''CS Undergrad Net''' (128.220.224.x) - Uses IP addresses that are ''accessible from the Internet''

:The Public and Private Grad/Research Nets are only ''physically'' accessible via network jacks in Malone Hall in CS work areas, except for the CS Undergrad Labs (Malone Hall 122 and the Ugrad Lab side of MH G61). The CS Undergrad Net is only ''physically'' accessible via network jacks in the CS Undergrad Lab. (Of course, you can access the Grad/Research Nets and the Ugrad Net systems remotely from other systems.)

:Not all network jacks are active. If you need to use a network jack but are not getting any network connection at all from it, please {{mailto|support|email us}} to ask for it to be activated.

 

==Network Jacks (Wallports) In Malone Hall==

:Network jacks may be located be under floor panels via access doors on the floor or they might be located on the wall, depending upon where you're located. Each network jack is identified with a floor number and jack number. (It is very important that any correspondence with CS IT Support or JHU Networking about a network jack include the full jack number.)

:(For those grad students working on the third floor of Malone, you might see that your floor panel access door is located under a slightly raised cabinet where the floor access door might be difficult to reach. For your convenience, there are network cables already coming out of those specific floor panels, and each of those cables is labeled with the port number.)

:Each active network jack in your Malone ''office'' will go to exactly one of those two Grad/Research networks (Public ''or'' Private Grad Net), so care will be needed to connect your computers into appropriate jacks. Again, if a jack is not currently active, you can {{mailto|support|email us}} to have it activated.

:Any given network jack can be changed from one network to the other (i.e., ''public to private'' or ''private to public'') with relatively little difficulty with an emailed request to [mailto:support@cs.jhu.edu CS Support]. We will pass on your request to JHU Networking. JHU Networking will be administering the network configurations; here is their current plan:

:* '''Even-numbered jacks''', by default, are connected to the '''''Public''''' CS Grad network, 128.220.35.x
:* '''Odd-numbered jacks''', by default, are be connected to the '''''Private''''' CS Grad network, 10.161.159.x

:'''Note 1:''' All network jacks in the CS Undergrad Lab are part of the CS Undergrad Net (128.220.224.x)

:'''Note 2:''' If you have a system that will reside in the G29 Malone ''server room'' instead, please contact CS Support, and we will help arrange your system's connections to the appropriate network, as there are no wallports in G-29.

 

== ''Public'' CS Grad/Research Network Details ==

:The '''"Public" CS Grad/Research Net''' uses IP addresses that are directly accessible from the Internet. It is useful for servers that need to be widely accessible or for systems that people need to connect to without going through the Hopkins VPN. (For example, if you need to ssh into your work machine from out on the Internet, your work machine needs a public IP address.)

:Systems on the Public Grad Net can freely communicate with systems elsewhere on the Hopkins network, including systems on the Private CS Grad Net.

:In order to set up a system on the Public Grad Net, you will need to follow the instructions at [[Requesting a Static IP Address on the CS Network]] and indicate in your request that the IP address will be public. There is '''no''' ''dynamic IP address service'' available on the Public network.

===Public IP Security Considerations===

:Please keep in mind that a system with a Public IP is exposed to the Internet. That means that '''''your system is open and vulnerable to access attempts from the outside.''''' If you're the only one who will access your system from the outside, please consider a Private IP instead, and use the VPN to put you into the JHU network so that you can access your system. If you have several outside people needing access to your system, then, yes, a Public IP is probably needed.

:And, because systems on the Public Grad Net are exposed to the Internet, they are expected to be managed in a way that preserves their security and the security of the Hopkins network. The JHU Network Security Team (part of the [http://www.it.jhu.edu/ IT@JH] group, ''not'' CS) may periodically perform security scans of systems on the Public Grad Net. If they determine that there are security problems with a system, they may disable all Internet access for that system until the problems are resolved.

===Opening Ports on the JHU Firewall===

:Some systems with a CS '''public''' IP might might want to be accessible through JHU's perimeter firewall. (CS does not maintain a departmental firewall) To have a port opened on the JHU firewall, please see: [https://support.cs.jhu.edu/wiki/Requesting_Open_Ports_on_the_JHU_Firewall Requesting Open Ports on the JHU Firewall]

 

== ''Private'' CS Grad/Research Network Details==

:The '''"Private" CS Grad/Research Net''' uses IP addresses that can only be directly accessed from either the Hopkins network or the Hopkins VPN. It is useful for systems that do not need to be accessed from the Internet, like desktop computers or printers. The private addressing used on this network helps keep the systems a little more secure, since no one on the Internet can contact them directly.

:You can connect your system to the Private Grad Net by following the instructions at [[Connecting to the CS Grad Nets]]. By default, you will receive a ''dynamic IP address''. If you need a ''static IP address'', follow the instructions at [[Requesting a Static IP Address on the CS Network]], making sure to specify that you want a ''private static IP address''.

 

==''CS Undergrad Network'' Details==

:The '''CS Undergrad Network''' is only available via wall and tabletop network jacks in Malone Hall Room 122 (the CS Collaboration Room). (Note that our other Ugrad Lab room, the Ugrad Lab side of Malone Hall G61, houses additional Ugrad Lab systems, but we are not currently supporting users plugging into the network in that room). To connect to the CS Undergrad Net, follow the instructions at [[Connecting to the CS Ugrad Net]]. Your computer will receive a dynamic IP address. There are no static IP addresses granted for the CS Ugrad Net.

 

== Requesting a Static IP Address ==

:If you need to request a ''static IP address'', please follow the instructions at [[Requesting a Static IP Address on the CS Network]].

 

== DNS Servers to use when on the CS Network ==

:Primary DNS: '''10.200.1.1'''

:Secondary DNS: '''10.200.2.2'''

:DHCP-provided CS IPs will automatically receive the above DNS servers.

 

== General Configuration Notes ==

===Public Network (128.220.35.x, even-numbered ports)===

:Subnet Mask: '''255.255.255.0'''

:Gateway: '''128.220.35.1'''

===Private Network (10.161.159.x, odd-numbered ports)===

:Subnet Mask: '''255.255.255.0'''

:Gateway: '''10.161.159.1'''

 

== Security Note ==

:All computers that connect to the CS Grad/Research or Undergrad net should be at their latest security levels and should be configured to prevent viruses, etc. For antivirus software, please see the [http://it.jhu.edu/antivirus JHU Antivirus webpage].

[[Category:Networking]]

Notices

2026-04-16T23:11:52Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2026-02-18T16:42:38Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2026-02-18T16:30:10Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2026-01-08T20:32:15Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2025-10-31T13:20:02Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2025-10-30T13:45:50Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-10-30T11:48:37Z

Pip: /* Outage #1: CS Webserver Will Be Unavailable */

Available Printers

2025-10-14T19:08:16Z

Pip:

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 M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone G61 (Masters'/Ugrad Lab) ||HP LaserJet M610||mhg61prt.cs.jhu.edu||mhg61prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) '''''{{red|NEW!}}'''''||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| 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.''|| {{red|('''''NEW'' ''HP'' copier, replaced the old ''Canon'' Copier''')}}
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.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|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 352 (''{{red|'''NEW'''}} printer in the 3rd floor Kitchen Area, as of 5/28/25'') ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==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. (Sometimes, only the full hostname will work if the IP address doesn't.) 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. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==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] 

* 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]]

Available Printers

2025-10-10T14:35:25Z

Pip:

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 M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone G61 (Masters'/Ugrad Lab) {{red|'''Temporarily unavailable'''; use mh122prt instead.}} ||HP LaserJet M610||mhg61prt.cs.jhu.edu||mhg61prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) '''''{{red|NEW!}}'''''||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| 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.''|| {{red|('''''NEW'' ''HP'' copier, replaced the old ''Canon'' Copier''')}}
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.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|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 352 (''{{red|'''NEW'''}} printer in the 3rd floor Kitchen Area, as of 5/28/25'') ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==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. (Sometimes, only the full hostname will work if the IP address doesn't.) 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. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==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] 

* 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]]

Notices

2025-10-10T14:33:45Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Python on the CS Webservers

2025-10-01T19:33:51Z

Pip: /* Python Packages */

Python is supported as a CGI program on the [[:Category:Webpages and Webservices|CS Department webservers]], but there are a few things you should know about it.

You may also want to read about [[Python on the CS Linux Clients]].

== Python Versions ==

The web servers have both Python 3 and Python 2 available. As of February 2021, the web servers are using '''''Python 3.6''''' by default. This is ''different'' from the [[:Category:Linux Clients|Linux clients]], which use a ''newer'' version. (As of fall 2025, the Linux clients use Python 3.13 by default.) If you're writing programs to run on one of the department web servers, '''we recommend you restrict those programs to use only features available in the web servers' version of Python 3.'''

The web servers have several other versions of Python ''available''. The Python versions available on both the web servers and the Linux clients are:

* Python 3.6 (default on the web servers)
* Python 3.9
* Python 3.11
* Python 3.12
* Python 3.13 (default on the Linux clients)

The version of Python used for your programs will depend on what interpreter you call at the top of your program. If you use {{code|#!/usr/bin/env python}} or {{code|#!/usr/bin/env python3}}, you will get the default Python for the system (which, again, will be different between the web server and the Linux client you can log in to). If you use {{code|#!/usr/bin/env python2}}, you will get Python 2.7 on the web server and the program will not work on our Linux clients. You can also give the precise version of Python you want; for example, {{code|#!/usr/bin/env python3.11}} will use Python 3.11 on both the web server and the Linux clients.

(It's good practice to explicitly use {{code|python3}} when you intend to use Python 3. Using {{code|python}} by itself is only recommended [https://www.python.org/dev/peps/pep-0394/ in a handful of situations] that mostly don't apply to our web servers.)

== Python Packages ==

The set of Python packages installed on the webservers is fairly minimal. If you need a package that's not installed, you should first try installing it yourself into your home directory, using our [[Python on the CS Linux Clients#Installing_Python_Packages|self-installation instructions]]. If that does not work, you can contact us at {{mailto|support}} for assistance, but be aware that we are not be able to install every requested package.

If you need a package that is not supported on our web servers' default Python version, you can use the versioned Python executable to set up the virtual environment. For example, if you had a package that needed Python 3.11 or later, you could run <kbd>python3.11 -m venv <var>/path/to/venv/directory</var></kbd>. If you run a Python program in such a venv, it will use the version of Python you used to set up the venv, even if the program starts with {{code|#!/usr/bin/env python3}} or {{code|#!/usr/bin/env python}}.

See the previous section for which versions of Python are available on both our web servers and our Linux clients.

== Deployment Options ==

For technical reasons, we do not support WSGI. You will have to run your Python programs as either CGI or FastCGI programs. (Most major Python web frameworks support FastCGI deployment; see their documentation for details.)

[[Category:Webpages and Webservices]]

Python on the CS Webservers

2025-10-01T18:46:57Z

Pip: /* Python Packages */

Python is supported as a CGI program on the [[:Category:Webpages and Webservices|CS Department webservers]], but there are a few things you should know about it.

You may also want to read about [[Python on the CS Linux Clients]].

== Python Versions ==

The web servers have both Python 3 and Python 2 available. As of February 2021, the web servers are using '''''Python 3.6''''' by default. This is ''different'' from the [[:Category:Linux Clients|Linux clients]], which use a ''newer'' version. (As of fall 2025, the Linux clients use Python 3.13 by default.) If you're writing programs to run on one of the department web servers, '''we recommend you restrict those programs to use only features available in the web servers' version of Python 3.'''

The web servers have several other versions of Python ''available''. The Python versions available on both the web servers and the Linux clients are:

* Python 3.6 (default on the web servers)
* Python 3.9
* Python 3.11
* Python 3.12
* Python 3.13 (default on the Linux clients)

The version of Python used for your programs will depend on what interpreter you call at the top of your program. If you use {{code|#!/usr/bin/env python}} or {{code|#!/usr/bin/env python3}}, you will get the default Python for the system (which, again, will be different between the web server and the Linux client you can log in to). If you use {{code|#!/usr/bin/env python2}}, you will get Python 2.7 on the web server and the program will not work on our Linux clients. You can also give the precise version of Python you want; for example, {{code|#!/usr/bin/env python3.11}} will use Python 3.11 on both the web server and the Linux clients.

(It's good practice to explicitly use {{code|python3}} when you intend to use Python 3. Using {{code|python}} by itself is only recommended [https://www.python.org/dev/peps/pep-0394/ in a handful of situations] that mostly don't apply to our web servers.)

== Python Packages ==

The set of Python packages installed on the webservers is fairly minimal. If you need a package that's not installed, you should first try installing it yourself into your home directory, using our [[Python on the CS Linux Clients#Installing_Python_Packages|self-installation instructions]]. If that does not work, you can contact us at {{mailto|support}} for assistance, but be aware that we are not be able to install every requested package.

If you need a package that is not supported on our web servers' default Python version, you can use the versioned Python executable to set up the virtual environment. For example, if you had a package that needed Python 3.11 or later, you could run <kbd>python3.11 -m venv <var>/path/to/venv/directory</var></kbd>. See the previous section for which versions of Python are available on both our web servers and our Linux clients.

== Deployment Options ==

For technical reasons, we do not support WSGI. You will have to run your Python programs as either CGI or FastCGI programs. (Most major Python web frameworks support FastCGI deployment; see their documentation for details.)

[[Category:Webpages and Webservices]]

Python on the CS Webservers

2025-10-01T18:43:20Z

Pip: /* Python Versions */

Python is supported as a CGI program on the [[:Category:Webpages and Webservices|CS Department webservers]], but there are a few things you should know about it.

You may also want to read about [[Python on the CS Linux Clients]].

== Python Versions ==

The web servers have both Python 3 and Python 2 available. As of February 2021, the web servers are using '''''Python 3.6''''' by default. This is ''different'' from the [[:Category:Linux Clients|Linux clients]], which use a ''newer'' version. (As of fall 2025, the Linux clients use Python 3.13 by default.) If you're writing programs to run on one of the department web servers, '''we recommend you restrict those programs to use only features available in the web servers' version of Python 3.'''

The web servers have several other versions of Python ''available''. The Python versions available on both the web servers and the Linux clients are:

* Python 3.6 (default on the web servers)
* Python 3.9
* Python 3.11
* Python 3.12
* Python 3.13 (default on the Linux clients)

The version of Python used for your programs will depend on what interpreter you call at the top of your program. If you use {{code|#!/usr/bin/env python}} or {{code|#!/usr/bin/env python3}}, you will get the default Python for the system (which, again, will be different between the web server and the Linux client you can log in to). If you use {{code|#!/usr/bin/env python2}}, you will get Python 2.7 on the web server and the program will not work on our Linux clients. You can also give the precise version of Python you want; for example, {{code|#!/usr/bin/env python3.11}} will use Python 3.11 on both the web server and the Linux clients.

(It's good practice to explicitly use {{code|python3}} when you intend to use Python 3. Using {{code|python}} by itself is only recommended [https://www.python.org/dev/peps/pep-0394/ in a handful of situations] that mostly don't apply to our web servers.)

== Python Packages ==

The set of Python packages installed on the webservers is fairly minimal. If you need a package that's not installed, you should first try installing it yourself into your home directory, using our [[Python on the CS Linux Clients#Installing_Python_Packages|self-installation instructions]]. If that does not work, you can contact us at {{mailto|support}} for assistance, but be aware that we are not be able to install every requested package.

== Deployment Options ==

For technical reasons, we do not support WSGI. You will have to run your Python programs as either CGI or FastCGI programs. (Most major Python web frameworks support FastCGI deployment; see their documentation for details.)

[[Category:Webpages and Webservices]]

Template:Code

2025-09-29T19:49:50Z

Pip: Created page with "<code {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} {{#if:{{{style|}}}|style="{{{style}}}"}}>{{{1}}}</code><noinclude> See https://www.mediawiki.org..."

<code {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} {{#if:{{{style|}}}|style="{{{style}}}"}}>{{{1}}}</code><noinclude>
See https://www.mediawiki.org/wiki/Template:Code .
</noinclude>

Notices

2025-09-19T13:02:05Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-18T20:18:09Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-18T20:18:02Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-18T20:13:15Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-18T16:54:01Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-18T16:53:53Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-18T16:53:33Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-18T16:53:13Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-10T18:01:08Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-10T17:07:46Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-10T17:01:54Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-10T16:57:35Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Disk Quotas

2025-08-29T12:41:56Z

Pip: Quota increase

'''CS ''UGRAD'' Net Users:''' Due to the number of students using the Ugrad Linux systems, 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.

'''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]]

== 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 '''15 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 15.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 15 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 (short for "d"isk "u"sage) 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>

Another use of du can provide some additional detail of what files are taking up the most space:

du -ha |sort -h |tail

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

== A Note on File Size and Disk Usage ==

On our systems, files are compressed before they're stored on disk. Consequently, the disk space used by a file (what you see if you run <kbd>du -sh <var>file</var></kbd>) is likely to be smaller than the amount of data stored in the file (which is what you see if you run <kbd>ls -lh <var>file</var></kbd>). Since our quotas are based on the actual amount of disk space used, the sizes shown by <code>du</code> are most relevant here. If you rely on just the sizes shown by <code>ls</code>, you might be misled about how much your quota is being affected by particular files.

== 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]]

Notices

2025-08-22T16:09:41Z

Pip: /* OUTAGE 1: Linux Lab Systems Not Accessible During Upgrades */

== {{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 ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 12:15 on Friday, all of our Linux clients have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage will start at 8:00 pm and is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

 

== {{red|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.

 

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

[[Category:All]]

Notices

2025-08-21T18:24:09Z

Pip: /* OUTAGE 1: Linux Lab Systems Not Accessible During Upgrades */

== {{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 ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 2:30 pm on Thursday, ugradx, gradx, and all the lab computers (ugrad1 through ugrad24 and masters1 through masters16) have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage will start at 8:00 pm and is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

 

== {{red|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.

 

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

[[Category:All]]

Notices

2025-08-20T16:24:19Z

Pip: /* OUTAGE 1: Linux Lab Systems Not Accessible During Upgrades */

== {{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 ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 12:30 on Wednesday, all lab computers (ugrad1 through ugrad24 and masters1 through masters16) have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage will start at 8:00 pm and is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

 

== {{red|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.

 

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

[[Category:All]]

Notices

2025-08-19T20:46:05Z

Pip: /* Outage 2: Networking Outage on the Malone Ground Floor */

== {{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 ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 12:30 on Tuesday, all ugrad systems from ugrad1 through ugrad12 have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage will start at 8:00 pm and is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

 

== {{red|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.

 

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

[[Category:All]]

Notices

2025-08-19T20:28:16Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

== {{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 ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 12:30 on Tuesday, all ugrad systems from ugrad1 through ugrad12 have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

== {{red|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.

 

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

[[Category:All]]

Notices

2025-08-19T16:25:23Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

== {{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 ===


'''WHEN:''' Tuesday, August 19 through Friday, August 22

'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

'''UPDATE:''' As of about 12:30 on Tuesday, all ugrad systems from ugrad1 through ugrad12 have been upgraded.

'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

== {{red|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.

 

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

[[Category:All]]

Third-Party Website Hosting with a CS Domain Name

2025-08-15T16:23:46Z

Pip: /* Process */

There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page hosting, like GitHub Pages or Google Sites, to more full-featured cloud platforms like Netlify, Heroku, Amazon Web Services, and Google Cloud Platform.

It is generally possible to use such third-party services in conjunction with a cs.jhu.edu hostname. For example, you could use <var>mycoursename</var>.cs.jhu.edu for course info served from a GitHub Pages site under your personal GitHub account. Any service that allows a DNS CNAME to point to their web server should let you use a cs.jhu.edu hostname in this way.

At this time, we only offer this service for CS Department faculty members.

== Process ==

# You must to set up the site yourself; CS IT Support staff are unable to provide assistance with this step
# Follow the service's custom domain instructions to see what DNS CNAME record you need to have added
#* CS IT Support staff may be able to assist you by pointing you to the right page in the service's documentation, but we can't promise we can help in every instance
# Fill out our [https://support.cs.jhu.edu/forms/ip-address-application IP address application]
#* Put the cs.jhu.edu hostname you want in the “Requested Machine Name” field
#* Put information about the CNAME record you need in the comment field
#* Add other information as appropriate (e.g. put in your contact information)
#* If a field is required but not applicable to this (e.g. the “Will you use DHCP” field), just put anything in that field

We'll let you know when things are set up on our end.

[[Category:Webpages and Webservices]]

Third-Party Website Hosting with a CS Domain Name

2025-08-15T13:45:15Z

Pip:

There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page hosting, like GitHub Pages or Google Sites, to more full-featured cloud platforms like Netlify, Heroku, Amazon Web Services, and Google Cloud Platform.

It is generally possible to use such third-party services in conjunction with a cs.jhu.edu hostname. For example, you could use <var>mycoursename</var>.cs.jhu.edu for course info served from a GitHub Pages site under your personal GitHub account. Any service that allows a DNS CNAME to point to their web server should let you use a cs.jhu.edu hostname in this way.

At this time, we only offer this service for CS Department faculty members.

== Process ==

# You must to set up the site yourself; CS IT Support staff are unable to provide assistance with this step
# Follow the service's custom domain instructions to see what DNS CNAME record you need to have added
# Fill out our [https://support.cs.jhu.edu/forms/ip-address-application IP address application]
#* Put the cs.jhu.edu hostname you want in the “Requested Machine Name” field
#* Put information about the CNAME record you need in the comment field
#* Add other information as appropriate (e.g. put in your contact information)
#* If a field is required but not applicable to this (e.g. the “Will you use DHCP” field), just put anything in that field

We'll let you know when things are set up on our end.

[[Category:Webpages and Webservices]]

Third-Party Website Hosting with a CS Domain Name

2025-08-15T13:39:52Z

Pip:

There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page hosting, like GitHub Pages or Google Sites, to more full-featured cloud platforms like Netlify or Heroku.

It is generally possible to use such third-party services in conjunction with a cs.jhu.edu hostname. For example, you could use <var>mycoursename</var>.cs.jhu.edu for course info served from a GitHub Pages site under your personal GitHub account. Any service that allows a DNS CNAME to point to their web server should let you use a cs.jhu.edu hostname in this way.

At this time, we only offer this service for CS Department faculty members.

== Process ==

# You must to set up the site yourself; CS IT Support staff are unable to provide assistance with this step
# Follow the service's custom domain instructions to see what DNS CNAME record you need to have added
# Fill out our [https://support.cs.jhu.edu/forms/ip-address-application IP address application]
#* Put the cs.jhu.edu hostname you want in the “Requested Machine Name” field
#* Put information about the CNAME record you need in the comment field
#* Add other information as appropriate (e.g. put in your contact information)
#* If a field is required but not applicable to this (e.g. the “Will you use DHCP” field), just put anything in that field

We'll let you know when things are set up on our end.

[[Category:Webpages and Webservices]]

Redirecting A CS URL To A Github Site

2025-08-15T13:38:25Z

Pip:

If you're a [https://www.cs.jhu.edu/faculty/ CS faculty member] with a [https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site GitHub Pages] site for CS Department–related work (research or teaching), but would rather have a CS URL instead that points to the GitHub Pages site, we can help with that.

Please follow our instructions for [[Third-Party Website Hosting with a CS Domain Name]]. The GitHub documentation for your site should be the “[https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain Configuring a Subdomain]” section of their custom domain documentation.

[[Category:Webpages and Webservices]]

Third-Party Website Hosting with a CS Domain Name

2025-08-15T13:33:57Z

Pip: Created page with "There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page h..."

There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page hosting, like GitHub Pages or Google Sites, to more full-featured cloud platforms like Heroku.

It is generally possible to use such third-party services in conjunction with a cs.jhu.edu hostname. For example, you could use <var>mycoursename</var>.cs.jhu.edu for course info served from a GitHub Pages site under your personal GitHub account. Any service that allows a DNS CNAME to point to their web server should let you use a cs.jhu.edu hostname in this way.

At this time, we only offer this service for CS Department faculty members.

== Process ==

# You must to set up the site yourself; CS IT Support staff are unable to provide assistance with this step
# Follow the service's custom domain instructions to see what DNS CNAME record you need to have added
# Fill out our [https://support.cs.jhu.edu/forms/ip-address-application IP address application]
#* Put the cs.jhu.edu hostname you want in the “Requested Machine Name” field
#* Put information about the CNAME record you need in the comment field
#* Add other information as appropriate (e.g. put in your contact information)
#* If a field is required but not applicable to this (e.g. the “Will you use DHCP” field), just put anything in that field

We'll let you know when things are set up on our end.

[[Category:Webpages and Webservices]]