@@ -75,26 +75,21 @@ Upon success, the jobid is returned to the user. The *job manager* then
7575takes the active role in moving a job through its life cycle:
7676
77771) If a job has dependencies, interacting with a job dependency
78- subsystem to ensure they are met before proceeding.
79-
78+ subsystem to ensure they are met before proceeding.
80792) Submitting an allocation request to the *scheduler * to obtain resources.
81-
82803) Once resources are allocated, submitting a start request to the
83- *exec service *.
84-
81+ *exec service *.
85824) The *exec service * starts *job shells * directly in a single-user instance.
86- In a multi-user instance, it directs the IMP to start them with guest
87- credentials, with appropriate containment.
88-
83+ In a multi-user instance, it directs the IMP to start them with guest
84+ credentials, with appropriate containment.
89855) The *job shell * examines jobspec and allocated resource set, then
90- launches tasks on local resources. It provides standard I/O, parallel
91- bootstrap, signal propagation, and exit code collection services.
92- It is a user-replaceable component.
93-
86+ launches tasks on local resources. It provides standard I/O, parallel
87+ bootstrap, signal propagation, and exit code collection services.
88+ It is a user-replaceable component.
94896) Once tasks exit, or an exceptional condition such as cancellation or
95- expiration of wall clock allocation occurs, the *exec service * cleans up
96- any lingering tasks and *job shells *, and notifies the *job manager * which
97- frees resources back to the *scheduler *.
90+ expiration of wall clock allocation occurs, the *exec service * cleans up
91+ any lingering tasks and *job shells *, and notifies the *job manager * which
92+ frees resources back to the *scheduler *.
9893
9994The job is now complete.
10095
0 commit comments