| 1 |
On Sunday, August 03, 2014 07:50:57 AM Martin Vaeth wrote: |
| 2 |
> J. Roeleveld <joost@××××××××.org> wrote: |
| 3 |
> > Depends on the specific requirements. |
| 4 |
> |
| 5 |
> > If you want: |
| 6 |
> In a sense, most you require can be done with my mentioned "schedule" |
| 7 |
> tool, although perhaps the usage is not in the way you expected. |
| 8 |
|
| 9 |
I agree, based on a quick look. |
| 10 |
|
| 11 |
> I reorder your points for a clearer explanation: |
| 12 |
|
| 13 |
<snipped explanation> |
| 14 |
|
| 15 |
A useful addition to your schedule-tool would be to store the scripts in a way |
| 16 |
that makes editing simpler and then add an editing tool to make this process |
| 17 |
simpler. |
| 18 |
Add monitoring (email alerts, webpage, front-end) to check the status of all |
| 19 |
the batch-jobs. |
| 20 |
|
| 21 |
|
| 22 |
I might be mistaken, but I think the server keeps the entire queue in-memory |
| 23 |
and when the process dies, the status is lost? |
| 24 |
Or is it kept somewhere? |
| 25 |
|
| 26 |
-- |
| 27 |
Joost |
Archives