[EMAIL PROTECTED] writes:
> Wow, I'm impressed. I've been vaguely thinking that somehow, unix
> doesn't have enough sophistication for submitting jobs, but stopped
> short of thinking how to solve it.
Yeah, this is just another one of those things that's been bugging me,
and now that I use an OS where I have all the source, I don't have to
put up with this sort of thing anymore if I'm willing to slave a bit.
The lameness of "make" is another one of these pet peeves. If I ever
get the time, I'm going to see about fixing that one too. I have
something *way* better in mind that would be much smaller, much
simpler, and probably a *lot* faster.
> Maybe gnucash is currently the only app that really wants this sort
> of stuff, and since it seems to be exceptional in this way, maybe we
> should indeed have a customized internal solution.
Well, it really seems to me that the at and cron modifications I'm
talking about are just really useful features, and the reason no one
else uses them more heavily might be because they're just not
generally available. If we do decide that this should be something we
handle, then rather than creating a gnucash-specific daemon (which
would be trivial to make if you base it on cron's code --- cron's a
really tiny program so it's easy to deal with), I'd rather create a
new general purpose daemon that we just happen to distribute with
gnucash and use in gnucash, but that people can also use for other
things.
The things I'd like to see in at (which it may already have):
* guaranteed (optional) unique job ID's. If you say something like
"echo job | at --unique-id now + 10 minutes" I'd like it to return
something like exim's unique message ID's. You'd then be able to
use that to refer to the job completely uniquely later with no
possible race conditions on removal, etc.
* job labels "echo turn-on-disco-lights | at --label 'Disco time.' ..."
that show up in at listings. Just so it's easier to see what's
going on (or going to go on :>)/
* (maybe) sections (namespaces) for at "at --section foo ..."
For cron, I just want --sections.
If I did anything for GnuCash, I'd be likely to just copy the at/atd
or cron code and add the few features we need and call the resulting
app something else. We'd have to discuss first whether we'd rather
have an at-esque daemon, or a cron-esque daemon. Either would do the
job. After I finised the modifications, I'd contact the upstream
authors and see if they were interested. If so, great, if not, then
we just go with our separate daemon.
> except for cron.d, the rest of this is in redhat I think.
Now that I think about it. It think maybe the Debian cron maintainer
is now also the upstream cron maintainer, but I'm not sure...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
