Timeline for Submitting non-interactive jobs over ssh
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 20, 2017 at 21:40 | comment | added | DopeGhoti |
That's what the start of the script is for - it drops a looks for a .lock file when it starts. If it's there, it aborts and barks; otherwise it writes the file and sets a trap to remove is when the script exits. You will very briefly have two screen sessions with the name LongJob1 in that instance.
|
|
| Jan 20, 2017 at 21:38 | comment | added | marmistrz |
Edited the OP. Two problems with this solution are mentioned there - I can't safely run schedule multiple commands at once. What if LongJob1 already exists?
|
|
| Jan 20, 2017 at 18:59 | comment | added | Luciano Andress Martini | Sorry. is because the question is not nice, the guy just dont like to use google or something like this. But the answer is nice. I removed the -1 as you ask. | |
| Jan 20, 2017 at 18:17 | comment | added | DopeGhoti | I am curious as to why this was downvoted, as it provides a solution to the question posed. A comment explaining why this was perceived to be a bad answer (particularly in the absence of any others) would be gratefully received. | |
| Jan 20, 2017 at 17:40 | history | answered | DopeGhoti | CC BY-SA 3.0 |