Public SourceMage Discussion List

[Jeremy Blosser <jblosser-smgl AT firinn.org>]

On Mar 06, Juuso Alasuutari [iuso AT sourcemage.org] wrote:
> On Monday 05 March 2007 23:20, Jaka Kranjc wrote:
> <snip>
> > > The init stuff is a possibility.  So is ledger... I would really like to
> > > see ledger in our scm repository.  It's difficult for me to push it on
> > > users or make it part of the install or anything when the project as a
> > > whole doesn't really have hands on it.
> >
> > Ok, two confirmed candidates then.
> >
> > Ladislav, can you get the current ledger code somewhere public? Or send it
> > to someone that can?
> > What all do we want from this ledger2?
> 
> I think Ledger might be a good candidate. What I'd like to see in Ledger2 
> is 
> automatization. It really puts me off that I have to manually send stuff 
> over; call me lazy or evil, but I don't actually use Ledger at all because 
> I 
> tend to not bother. I want to be able to cast it -- consciously saying 
> 'yes' 
> to 'Do you give permission to automatically send DNA samples to the 
> Overlords 
> at planet Vulcan?' -- and have it set up a cron job for itself.

Before we can have any spells insert themselves into cron we need some kind
of standard approach to cron.  We completely don't have this now.  We have
several cron implementations that all install different ways, use different
syntaxes, different crontab locations, etc.  I'm not saying we should
change however the upstream installs them, but we should have all crons
optionally depend on run-parts, have cron/ directories in spells that
contain entries that should be added, etc.  These may have to be aware of
the different cron system capabilities, but for basics the regular
hourly/daily/weekly run-parts stuff should do.

Maybe this is another one for some kind of 'config management' component,
like was mentioned for init scripts, sysadmin scripts, etc.

> - Init script. Let's have it start on each boot.

Start what?

> - Data encryption. Some SSL pubkey wizardry to make sure our users' log 
> data 
> is protected during transfer.

This probably only needs curl posting to an ssl-enabled site with a server
cert the user boxes know about.  We can get cacerts easily; if curl doesn't
trust those out of the box we can put our CA keys in smgl-pubkeys or
something.

> - Bug reports. A cast failure could trigger Ledger2 to automatically send 
> in 
> the logs. They could be sent immediately, or stored and queued to be sent 
> as 
> attachments with the next scheduled system report.

I agree with the notion that ledger isn't a bug reporting tool.

Attachment: pgpVUy0TD_Fz9.pgp
Description: PGP signature