|
From: | Brian Dee |
Subject: | RE: Comments on the diagram (was:RE:[Pyatcron-devel-list]Cronbackend: a correction) |
Date: | Wed, 19 Nov 2003 11:28:19 -0700 |
Brian,
About the getCommand of the CronEntry and AtEntry class. I think that they must be renamed to getRegisterString.
This function should return a string used to register the task. For the CronEntry, the getRegisterString will return:
"* * * * * /the/command/to/run -its -parameters"
This first fileds will be build with the Schedule fields and the command to run will be build with the GenericTask pointed by the Schedule object.
Does this makes things a bit clear to you?
Now, I'm currently thinking about a CronEntryCollector and an AtEntryCollector who will be in charge of parsing the existing cron and at entries (ie retrieve the definitions from system), manage list of CronEntry and AtEntry (addition and deletion of some), export those list to a GtkList, and rebuild the system cron and at entries.
The process flow will then be as follow:
1. Create CronEntryCollector
2. CronEntryCollector.parseUserCrontab(<username>)
[Prev in Thread] | Current Thread | [Next in Thread] |