On 3 Jun 1999, Rob Browning wrote:
> [EMAIL PROTECTED] writes:
>
> > 3) these scripts typically would get scheduled from a cron job.
> > Great answer for unix gurus, but a problem for newbies.
>
> This suggests that sticking them on the menu is only part of the
> problem. Though once they're schemified, invoking them from a command
> line (minus locking/synchronization issues) just involves adding an
> arg like perl's "-e" to the startup process. It's critical to make
> sure that it gets invoked at the right time (after initialization),
> though.
>
> I still want to do a more automated automated task system, but I've
> put that on the back burner. I want gnucash to be able to schedule
> events that are guaranteed to happen, even if you don't have gnucash
> running, and I want it to be able to do this itself, without having to
> ask the user to modify their crontab, etc. by hand. Unless we're
> going to get in the business of editing the user's crontab
> automatically, something I'd vhemently oppose, we need either a
> modification to cron, or an "at" with a few guarantees.
>
> I got in a long discussion with the at/cron/anacron maintainers and
[... Interesting discussion about at, cron, etc. deleted for brevity...]
To me, this seems like overthinking the issue (for the time being).
What would be the problem with gnucash simply checking the last startup
date against the current date and then add any scheduled transactions
that should have happened during that time? No at, no cron, no
unnecessary complexity. Am I being naive?
--
Chris Ingram
[EMAIL PROTECTED]
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
