Score:0

at-command: Scheduling and process priority

cn flag
SEU

I have about 10 "at" jobs. There are cases where there is a conflict of resources and I am trying to find a neat way to schedule this. Say, job#5 may want to start before the job#4 ends. Each job has a priority/weight. If job#5 has higher priority, it can kill job#1 and start. How do I incorporate such a method of scheduling?

Thanks.

Patrick Mevzek avatar
cn flag
You are clearly pushing the `at` subsystem too far from what it was designed for. You probably need to redesign things and understand why you have 10 jobs that seem separate, because written as 10 jobs, but at the same time having dependencies between them. You could have a look at newer solutions like `systemd.timer` but even that may not have the features you need.
cn flag
SEU
Thanks. Right now I solved it by creating and deleting a file FLAG.txt with certain parameters. Each job checks for the existence of that file and the parameters. The subsequent at job will proceed or exit based on those parameters. Works OK, but hoped to find a better way.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.