ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've got a shell script that submits a subjob to atd. This subjob could potentially take a long time. If it is taking more than 15 minutes, the script moves on and performs the action in another (less desirable) way and the at job should be cancelled or killed. Is there a way to capture the at job number that is submitted? If for some reason the atd daemon is down or hung, I want to be able to remove the at job I submitted.
If I can capture this job number, I can be assured I atrm the right job number. There are obviously other work arounds, but it is much clearer if I could just capture this job number during submission.
Is there a way to capture the at job number that is submitted?
jobnr=($(at -f commandfile timespec 2>/dev/null)); [ "${#jobnr[@]}" = "5" ] && jobnr=${jobnr[1]}
Could do with some more tests but should work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.