job number should be on server

[rcoreilly]

the job number is stored locally on the client -- that is a problem! we don't quite have a good place to put it -- currently in ~/gruntdat/projs//nextjob.id could just be in top-level on repo under jobs/nextjob.id -- issue is potential conflict of client vs. server updating -- in general, we try to always have one direction do the updating, otherwise conflicts easily arise. Also it is not really viable to have 2 diff clients active at the same time because they could both submit the same job at the same time.

But, despite all that, it is ind of weird making everything depend on one machine. So maybe we have a specific command to pull the job number down from server, but otherwise the client is always doing the updating?

[rcoreilly]

This is now mostly fixed: jobs/maxjob.id contains the maximum job number for the server, updated after every command, and then grunt ensures that its nextjob.id is always at least greater than that maxjob -- should keep in reasonably in sync without having contention over updating the same file on both sides..