| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Process IDs of Tasks
- If you call a shell job
...
- in the JobScheduler Agent then you can write the PID in the shell script to stdout
...
- in order to see the PID in the task log.
- On a linux shell you can use "echo $$".
- For Windows look for example here.
- Another way
...
- how to achieve this is to check the task log.
- There you see the temporary file which is called on the JobScheduler Agent (e.g. for Linux Agent: SCHEDULER-987 Starting process: '/bin/sh' '-c' '"/tmp/sos.C5NpSU"').
Example
In the ./logs/scheduler.log file of the JobScheduler Agent you will findon Linux Agent
- for a Unix JobScheduler Agent:
| Code Block |
|---|
\{scheduler\} fork(), execvp("/tmp/sos.C5NpSU") \{scheduler\} pid=4711 |
...
- for a Windows JobScheduler Agent:
| Code Block |
|---|
..CreateProcess("",""C:\TEMP\sos41CE7.cmd"")
..pid=4711
|