Running scripts in the background - Revision history

Daniel Castaño at 09:45, 19 November 2020

2020-11-19T09:45:09Z

Daniel Castaño: /* Killing a background process */

2020-11-18T18:53:57Z

Killing a background process

Daniel Castaño at 18:53, 18 November 2020

2020-11-18T18:53:18Z

Daniel Castaño at 18:51, 18 November 2020

2020-11-18T18:51:52Z

Daniel Castaño at 18:50, 18 November 2020

2020-11-18T18:50:04Z

Daniel Castaño: Created page with "This information refers to Linux and Mac operative systems = The nohup command = The nohup command allows to run a command in the background, in a fashion that interru..."

2020-11-18T18:43:00Z

Created page with "This information refers to Linux and Mac operative systems = The nohup command = The <t>nohup</tt> command allows to run a command in the background, in a fashion that interru..."

New page

This information refers to Linux and Mac operative systems
= The nohup command =
The <t>nohup</tt> command allows to run a command in the background, in a fashion that interruptions of the connection will not terminate the job. The terminal containing the job might get closed and the job will still carry on.
In order to keep track of the PID (process identifier) assigned by the process to the command launched, remember to use the <tt>&</tt> at the end of the line that invokes nohup. This PID might be needed to interrupt the execution of the background job.

== Retrieving the PID of your process==
Use the <tt>pgrep</tt> command, followed by the command that you nohup-ed. For instance:

<tt>pgrep MATLAB</tt>

to locate PIDs that carry a MATLAB process. Note that in your system, capital letters might not apply

=Running Matlab scripts=

==With a license==
If you want to run the script <tt>myTest.m</tt> through <tt>nohup</tt>, the advised syntax is:
<tt>nohup -nosplash matlab < myTest.m > output.txt & </tt>

where
* no splash inhibited the popup of the Matlab welcome window
* output.txt is a text file that will catch the text that would be shown in the screen if the script would be ran directly (instead of through nohup).

==With the standalone==

== Matlab scripts including Dynamo commands ==
Remember that you need to include a line that activates 'Dynamo' inside the script that you submit into nohup.

= Running projects in the background=
'Dynamo' projects can be run directly by nohup. A project script <tt>myProject.exe</tt> can be ran by
<tt>nohup myProject.exe</tt>

← Older revision		Revision as of 09:45, 19 November 2020
Line 45:		Line 45:
	'Dynamo' projects can be run directly by <tt>nohup</tt>. A project script <tt>myProject.exe</tt> can be ran by		'Dynamo' projects can be run directly by <tt>nohup</tt>. A project script <tt>myProject.exe</tt> can be ran by
	<tt>nohup myProject.exe</tt>		<tt>nohup myProject.exe</tt>
		+
		+	=Use Dynamo to run nohup=
		+
		+	There is a convenience object to initiate nohup processes from Dynamo itself. The syntax is
		+
		+	<tt>mbsys.nohup.launch('myScript')</tt>
		+
		+	The output can be directed to an object:
		+
		+	<tt>nh = mbsys.nohup.launch('myScript')</tt>
		+
		+	where <tt>nh</tt> gathers the info of the process (PID number, output file, etc), at includes some utilities for typical functionalities (killing the process, checking its status, etc).

@@ Line 6: / Line 6: @@
 == Killing a background process ==
-Use the command <tt>kill -9</tt> followed by the PID of the process that you want to kill.
+Use the command <tt>kill -9</tt> followed by the PID of the process that you want to kill. For instance, for a job with PID <tt>12657</tt>, write:
   <tt>kill -9 12657 </tt>

@@ Line 1: / Line 1: @@
-This information refers to Linux and Mac operative systems
+This information refers to Linux and Mac operative systems.
 = The nohup command =
-The <t>nohup</tt> command allows to run a command in the background, in a fashion that interruptions of the connection will not terminate the job. The terminal containing the job might get closed and the job will still carry on.
+The <tt>nohup</tt> command allows to run a job in the background, in a fashion that interruptions of the connection will not terminate the job. The terminal containing the job might get closed and the job will still carry on.
 In order to keep track of the PID (process identifier) assigned by the process to the command launched, remember to use the <tt>&</tt> at the end of the line that invokes nohup, this will force the system to show the PID after launching the job. This PID might be needed to interrupt the execution of the background job.
@@ Line 16: / Line 17: @@
 =Running Matlab scripts=
 ==With a license==
@@ Line 36: / Line 38: @@
 <tt>nohup dynamo < myTest.m > output.txt & </tt>
-= Running projects in the background=
+=Running projects in the background=
-'Dynamo' projects can be run directly by nohup. A project script <tt>myProject.exe</tt> can be ran by
+'Dynamo' projects can be run directly by <tt>nohup</tt>. A project script <tt>myProject.exe</tt> can be ran by
   <tt>nohup myProject.exe</tt>

@@ Line 10: / Line 10: @@
 == Retrieving the PID of your process==
-Use the <tt>pgrep</tt> command, followed by the command that you nohup-ed. For instance:
+You can use the <tt>pgrep</tt> command, followed by the command that you nohup-ed. For instance:
   <tt>pgrep MATLAB</tt>
-to locate PIDs that carry a MATLAB process. Note that in your system, capital letters might not apply
+to locate PIDs that carry a MATLAB process and that are ran by nohup. Note that in your system, capital letters might not apply.
 =Running Matlab scripts=