SSH - Revision history

Chris: /* NOHUP */

2021-07-08T02:50:45Z

NOHUP

← Older revision		Revision as of 22:50, 7 July 2021
Line 113:		Line 113:

	This can be avoided by prefixing your commands with the <code>nohup</code> and running it in the background with the ampersand, like the following example:		This can be avoided by prefixing your commands with the <code>nohup</code> and running it in the background with the ampersand, like the following example:
	<span style="color:red;font-weight:bold;">nohup</span> autorecon1.sh 501 T1_ <span style="color:red;font-weight:bold;">&</span>		<span style="color:red;font-weight:bold;">nohup</span> autorecon1.sh 501 T1_ <span style="color:red;font-weight:bold;">&</span>
	<span style="font-weight:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>		<span style="font-weight:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>

	All the program output gets sent to a file called ''nohup.out'' in your current working directory, but otherwise the program runs as normal, even if you log out of your SSH session. Note that, because the program output is not echoed to the terminal window, you will not immediately be alerted to any errors that may occur. It is recommended that you echo the contents of the nohup.out file after a moment or two, to make sure that things are running as expected:		All the program output gets sent to a file called ''nohup.out'' in your current working directory, but otherwise the program runs as normal, even if you log out of your SSH session. Note that, because the program output is not echoed to the terminal window, you will not immediately be alerted to any errors that may occur. It is recommended that you echo the contents of the nohup.out file after a moment or two, to make sure that things are running as expected:
	cat nohup.out		cat nohup.out
	If you want to run multiple processes simultaneously within the same directory, you'll run into a problem using <code>nohup</code> as it dumps all the output into a single ''nohup.out'' file, which becomes very difficult to sift through and interpret. To have more orderly output files, you can redirect <code>nohup</code> to an ''.out'' file of your choosing using an additional in-line command <code> > filename.out</code>. Here's an example:		If you want to run multiple processes simultaneously within the same directory, you'll run into a problem using <code>nohup</code> as it dumps all the output into a single ''nohup.out'' file, which becomes very difficult to sift through and interpret. To have more orderly output files, you can redirect <code>nohup</code> to an ''.out'' file of your choosing using an additional in-line command <code> &> filename.out</code>. Here's an example:
	nohup autorecon1.sh 501 T1_ > 501_T1.out &		nohup autorecon1.sh 501 T1_ &> 501_T1.out &

Chris: /* Connecting via VPN from outside campus */

2021-03-30T23:04:01Z

Connecting via VPN from outside campus

← Older revision		Revision as of 19:04, 30 March 2021
Line 6:		Line 6:

	== Connecting via VPN from outside campus ==		== Connecting via VPN from outside campus ==
	Note that if you are outside of the UB network (e.g., working at home) you will have to first be connected via UB's VPN using the [http://www.buffalo.edu/ubit/service-guides/connecting/vpn/computer.html ~~FortiClient VPN~~ Client] because these computers will ignore any connection request coming from outside Park Hall. If you have never done this before, follow the link to download, install and configure the client to connect to UB's VPN server.		Note that if you are outside of the UB network (e.g., working at home) you will have to first be connected via UB's VPN using the [http://www.buffalo.edu/ubit/service-guides/connecting/vpn/computer.html Cisco AnyConnect Client] because these computers will ignore any connection request coming from outside Park Hall. If you have never done this before, follow the link to download, install and configure the client to connect to UB's VPN server.

	== Windows ==		== Windows ==

Chris: /* NOHUP */

2020-05-20T03:14:13Z

NOHUP

← Older revision		Revision as of 23:14, 19 May 2020
Line 113:		Line 113:

	This can be avoided by prefixing your commands with the <code>nohup</code> and running it in the background with the ampersand, like the following example:		This can be avoided by prefixing your commands with the <code>nohup</code> and running it in the background with the ampersand, like the following example:
	nohup autorecon1.sh 501 T1_ &		<span style="color:red;font-weight:bold;">nohup</span> autorecon1.sh 501 T1_ <span style="color:red;font-weight:bold;">&</span>
	<span style="font-~~size~~:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>		<span style="font-weight:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>

	All the program output gets sent to a file called ''nohup.out'' in your current working directory, but otherwise the program runs as normal, even if you log out of your SSH session. Note that, because the program output is not echoed to the terminal window, you will not immediately be alerted to any errors that may occur. It is recommended that you echo the contents of the nohup.out file after a moment or two, to make sure that things are running as expected:		All the program output gets sent to a file called ''nohup.out'' in your current working directory, but otherwise the program runs as normal, even if you log out of your SSH session. Note that, because the program output is not echoed to the terminal window, you will not immediately be alerted to any errors that may occur. It is recommended that you echo the contents of the nohup.out file after a moment or two, to make sure that things are running as expected:

Chris: /* NOHUP */

2020-05-20T03:12:07Z

NOHUP

← Older revision		Revision as of 23:12, 19 May 2020
Line 114:		Line 114:
	This can be avoided by prefixing your commands with the <code>nohup</code> and running it in the background with the ampersand, like the following example:		This can be avoided by prefixing your commands with the <code>nohup</code> and running it in the background with the ampersand, like the following example:
	nohup autorecon1.sh 501 T1_ &		nohup autorecon1.sh 501 T1_ &
			<span style="font-size:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>

	All the program output gets sent to a file called ''nohup.out'' in your current working directory, but otherwise the program runs as normal, even if you log out of your SSH session. Note that, because the program output is not echoed to the terminal window, you will not immediately be alerted to any errors that may occur. It is recommended that you echo the contents of the nohup.out file after a moment or two, to make sure that things are running as expected:		All the program output gets sent to a file called ''nohup.out'' in your current working directory, but otherwise the program runs as normal, even if you log out of your SSH session. Note that, because the program output is not echoed to the terminal window, you will not immediately be alerted to any errors that may occur. It is recommended that you echo the contents of the nohup.out file after a moment or two, to make sure that things are running as expected:
	cat nohup.out		cat nohup.out
	~~<span style="font-size:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>~~

	If you want to run multiple processes simultaneously within the same directory, you'll run into a problem using <code>nohup</code> as it dumps all the output into a single ''nohup.out'' file, which becomes very difficult to sift through and interpret. To have more orderly output files, you can redirect <code>nohup</code> to an ''.out'' file of your choosing using an additional in-line command <code> > filename.out</code>. Here's an example:		If you want to run multiple processes simultaneously within the same directory, you'll run into a problem using <code>nohup</code> as it dumps all the output into a single ''nohup.out'' file, which becomes very difficult to sift through and interpret. To have more orderly output files, you can redirect <code>nohup</code> to an ''.out'' file of your choosing using an additional in-line command <code> > filename.out</code>. Here's an example:
	nohup autorecon1.sh 501 T1_ > 501_T1.out &		nohup autorecon1.sh 501 T1_ > 501_T1.out &

Chris: /* NOHUP */

2020-05-20T03:11:43Z

NOHUP

← Older revision		Revision as of 23:11, 19 May 2020
Line 117:		Line 117:
	cat nohup.out		cat nohup.out
	<span style="font-size:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>		<span style="font-size:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>

	If you want to run multiple processes simultaneously within the same directory, you'll run into a problem using <code>nohup</code> as it dumps all the output into a single ''nohup.out'' file, which becomes very difficult to sift through and interpret. To have more orderly output files, you can redirect <code>nohup</code> to an ''.out'' file of your choosing using an additional in-line command <code> > filename.out</code>. Here's an example:		If you want to run multiple processes simultaneously within the same directory, you'll run into a problem using <code>nohup</code> as it dumps all the output into a single ''nohup.out'' file, which becomes very difficult to sift through and interpret. To have more orderly output files, you can redirect <code>nohup</code> to an ''.out'' file of your choosing using an additional in-line command <code> > filename.out</code>. Here's an example:
	nohup autorecon1.sh 501 T1_ > 501_T1.out &		nohup autorecon1.sh 501 T1_ > 501_T1.out &

Chris: /* NOHUP */

2020-05-20T03:11:31Z

NOHUP

← Older revision		Revision as of 23:11, 19 May 2020
Line 116:		Line 116:
	All the program output gets sent to a file called ''nohup.out'' in your current working directory, but otherwise the program runs as normal, even if you log out of your SSH session. Note that, because the program output is not echoed to the terminal window, you will not immediately be alerted to any errors that may occur. It is recommended that you echo the contents of the nohup.out file after a moment or two, to make sure that things are running as expected:		All the program output gets sent to a file called ''nohup.out'' in your current working directory, but otherwise the program runs as normal, even if you log out of your SSH session. Note that, because the program output is not echoed to the terminal window, you will not immediately be alerted to any errors that may occur. It is recommended that you echo the contents of the nohup.out file after a moment or two, to make sure that things are running as expected:
	cat nohup.out		cat nohup.out
			<span style="font-size:bold;font-size:large">Remember: Don't forget to end your command with the ampersand!</span>
	If you want to run multiple processes simultaneously within the same directory, you'll run into a problem using <code>nohup</code> as it dumps all the output into a single ''nohup.out'' file, which becomes very difficult to sift through and interpret. To have more orderly output files, you can redirect <code>nohup</code> to an ''.out'' file of your choosing using an additional in-line command <code> > filename.out</code>. Here's an example:		If you want to run multiple processes simultaneously within the same directory, you'll run into a problem using <code>nohup</code> as it dumps all the output into a single ''nohup.out'' file, which becomes very difficult to sift through and interpret. To have more orderly output files, you can redirect <code>nohup</code> to an ''.out'' file of your choosing using an additional in-line command <code> > filename.out</code>. Here's an example:
	nohup autorecon1.sh 501 T1_ > 501_T1.out &		nohup autorecon1.sh 501 T1_ > 501_T1.out &

Chris: /* Linux */

2020-03-20T19:34:57Z

Linux

← Older revision		Revision as of 15:34, 20 March 2020
Line 55:		Line 55:

	==Linux==		==Linux==
	See the instructions for OSX~~. Also~~, ~~don't be daft. If~~ you've committed to Linux, you probably already know how to do this.		See the instructions for OSX, but if you've committed to Linux, you probably already know how to do this.

	== File Transfer ==		== File Transfer ==

Chris: /* Connecting with the ssh command using Xwindows */

2020-03-20T19:33:55Z

Connecting with the ssh command using Xwindows

← Older revision		Revision as of 15:33, 20 March 2020
Line 45:		Line 45:

	===Connecting with the ssh command using Xwindows===		===Connecting with the ssh command using Xwindows===
	The Xorg window server is the system that Unix computers use to draw windows and other graphic elements on the screen. If you have an Xorg client installed on your Mac OSX computer, you can have your local screen accept these graphical instructions from the remote computer. This would let you run remote applications that have a graphical user interface. To use X, simply use the -X command line switch when connecting (that's an upper-case X):		The Xorg window server is the system that Unix computers use to draw windows and other graphic elements on the screen. If you have an Xorg client installed on your Mac OSX computer, you can have your local screen accept these graphical instructions from the remote computer. This would let you run remote applications that have a graphical user interface. To use X, simply use the -X command line switch when connecting (that's an upper-case X), e.g.,:
	<code>ssh -X username@cast-psy341ws03</code>		<code>ssh -X username@cast-psy341ws03.caset.buffalo.edu</code>
	====Where can I get an Xorg client?====		====Where can I get an Xorg client?====
	The OSX Xorg client is called XQuartz (homepage: [http://www.xquartz.org/ www.xquartz.org]). If you go to that website, you can download the .dmg installer.		The OSX Xorg client is called XQuartz (homepage: [http://www.xquartz.org/ www.xquartz.org]). If you go to that website, you can download the .dmg installer.

Chris: /* Connecting with the ssh command */

2020-03-20T19:32:59Z

Connecting with the ssh command

← Older revision		Revision as of 15:32, 20 March 2020
Line 40:		Line 40:
	#Open up a terminal window		#Open up a terminal window
	#*If you have never done this, you will find it under '''Applications/Utilities/Terminal'''		#*If you have never done this, you will find it under '''Applications/Utilities/Terminal'''
	#In your terminal window, type <code> ssh username@~~cast-psy341ws~~[~~2 or 3~~]</code>		#In your terminal window, type <code> ssh username@[hostname]</code>

	After a successful login, you will find yourself with a terminal connection and in your home directory, just as though you had logged in and launched a terminal window on one of the computers in the lab.		After a successful login, you will find yourself with a terminal connection and in your home directory, just as though you had logged in and launched a terminal window on one of the computers in the lab.

Chris: /* Windows */

2020-03-20T19:31:43Z

Windows

← Older revision		Revision as of 15:31, 20 March 2020
Line 4:		Line 4:

	'''IMPORTANT: See NOHUP section below before running commands over a remote connection'''		'''IMPORTANT: See NOHUP section below before running commands over a remote connection'''

			== Connecting via VPN from outside campus ==
			Note that if you are outside of the UB network (e.g., working at home) you will have to first be connected via UB's VPN using the [http://www.buffalo.edu/ubit/service-guides/connecting/vpn/computer.html FortiClient VPN Client] because these computers will ignore any connection request coming from outside Park Hall. If you have never done this before, follow the link to download, install and configure the client to connect to UB's VPN server.

	== Windows ==		== Windows ==
Line 9:		Line 12:

	Note that the fact that this simple program doesn't do a big installation song and dance is a blessing and a curse: It's really compact and doesn't muck up your computer with stuff you don't want. On the other hand, you won't have the benefit of having a handy Start Menu shortcut being created for you. You will either have to find the putty.exe file on your computer each time you want to connect, or else create a menu or desktop shortcut manually.		Note that the fact that this simple program doesn't do a big installation song and dance is a blessing and a curse: It's really compact and doesn't muck up your computer with stuff you don't want. On the other hand, you won't have the benefit of having a handy Start Menu shortcut being created for you. You will either have to find the putty.exe file on your computer each time you want to connect, or else create a menu or desktop shortcut manually.

	~~===Connecting via VPN from outside campus===~~
	Note that if you are outside of the UB network (e.g., working at home) you will have to first be connected via UB's VPN using the [http://www.buffalo.edu/ubit/service-guides/connecting/vpn/computer.html FortiClient VPN Client] because these computers will ignore any connection request coming from outside Park Hall. If you have never done this before, follow the link to download, install and configure the client to connect to UB's VPN server.

	=== Connecting in PuTTY ===		=== Connecting in PuTTY ===