Timeline for Linux Shell Scripting for reading multiple files and running them
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 25, 2021 at 8:00 | comment | added | Yash54 | Thankyou @cas slution provided works fine. | |
| Dec 25, 2021 at 7:49 | vote | accept | Yash54 | ||
| Dec 25, 2021 at 7:07 | comment | added | Yash54 | I will try this solution and see. Thanks | |
| Dec 24, 2021 at 9:46 | comment | added | cas |
@terdon it's been ages since i worked with PBS or Torque too (I always preferred SLURM, anyway). But qsub submits the job to the queue, then it exits - that's it's purpose. It doesn't wait for the job to finish - it doesn't even know when it will start, let alone finish. The scheduler runs the job according to its rules (timing, permissions, priorities, etc), and when it has the resources (cpu cores/threads, gpus, memory, etc) available for the job. Anyway, that's why I think running qsub with & isn't needed and would probably be a bad idea.
|
|
| Dec 24, 2021 at 7:38 | comment | added | terdon♦ |
I haven't used this sort of setup in years, does qsub return immediately or will it wait until the job has finished running?
|
|
| Dec 24, 2021 at 6:46 | comment | added | Stéphane Chazelas |
Or (cd "$d" && exec qsub runme.pbs) to avoid having to restore the cwd and not run qsub if cd failed.
|
|
| Dec 24, 2021 at 6:28 | history | answered | cas | CC BY-SA 4.0 |