Re: TR: RE: [ErrorSystem-devel] home page little update

[<son...@ss...>]

Mostly right, but I was infering as MySQL as the default as it supports
republiation, and has tools to make altering tables alot easier then
SQLite. I think that what should be done is that a crontab event (the
crontab is a way to run programs at a certian time on *NIXs). That crontab
would do a data-only dump of the MySQL tables, backup the current SQLite
database, and then recreate it using CREATE TABLE statements and the
INSERT data. Also, you can use SQLite with PHP 4, it's available as a PECL
module, and I have it running on my local copy of PHP. Anyway, as now I
have some desgin, I'm going to write the Database API, so it will be easy
to use the rollover. As an additional option, maybe we should add it so it
can rollover to something else before SQLite, like a backup server ? Also,
what should the file layout for this problem be ?. I was going to put the
database layer in, as well as the default schema:

errorsystem/include/db/db-mysql.php
errorsystem/include/db/schema/base-mysql.sql

Also, what does this mean for this project now that you can do it at your
workplace ? Will they adapt it once we get a working version ?. Stephane,
can you please send me what code you have so I can get it into CVS.

Also, here is some information about using WinCVS with SSH.
http://minimal.cx/wincvsssh.php

However, once you run this part:
---
Now log into the remote machine, and add this ID to the trusted hosts file
[1]:

ssh -l <user> <remote_host>
cat id_dsa.pub >> .ssh/authorized_keys
rm id_dsa.pub
--

Do this:
While still at the command prompt, type cat id_dsa.pub and copy the lines
it generates (it should start with ssh-dss), and then copy that into your
Public Key Management on the SourceForge User page. Once it syncs itself
back to the CVS/Shell server, you should be able to get into CVS. Then
follow the rest of the directions starting with wincvs setup.

Two notes:
I'm loading this project into XCode (The Mac OS X Coder IDE), so it's
going to put some additional files into the directory, but they won't
interfer with anything (though we would have to remove them before making
a release). Second, I'm going to write a Linux shell script that will
strip out the .DS_Store files Mac OS X likes to leave behind, but they
will be there, floating in the CVS files but you can safely ingore them.
>
> Hi McTails,
>
>> -----Message d'origine-----
>> De : err...@li...
>> [mailto:err...@li...]De la part de
>> son...@ss...
>> Envoyé : vendredi 5 décembre 2003 21:32
>> À : bro...@fr...
>> Cc : son...@ss...; ES-devel
>> Objet : RE: [ErrorSystem-devel] home page little update
>>
>>
>> It's McTails, sorry if I mispelt it :-P.
>
> Sorry, I have misunderstood...
>
>> I never figured that ES would be
>> used as a way to report MySQL errors as it already has a good
>> errorsystem.
>
> So do I. But I was thinking about ES should be used for advanced error
> reporting when a system uses MySQL. Imagine a PHP script, run regulary
> with
> the commandline (every 10 minutes for exemple), using MySQL to store
> datas.
> The db server is down, so the query fails. PHP will prompt the error, and
> it
> should be log with a redirection. And this error should run for a long
> time,
> since someone looks in the log file. I think ES should be used to send a
> mail to the admin on the first the error appends. In fact, it exactely a
> feature I require. I should do that in the original script, but I could
> also
> do everything I need in the script, but it should so better to do this
> with
> ES
>
>> Anyway, the CVS respiorty is empty and I find that a bunch of Windows
>> CVS
>> clients just don't report errors when using SSH.
> Shit!
>>WinCVS doesn't report
>> that it can't find putty, and it seems to appear working with
>> everything.
>> Remember that you must have your public key(s) upload to SF.net.
> How can I do that?
>> Also the
>> CVS script is not part of SF itself, it's a seperate one called cvsweb
>> (this I know because I run a private local SF.net server).
> Nice!
>
>>What a
>> possiabile solution to do is to wait for PHP5, as it will be including
>> SQLite, a file based SQL system that doesn't require a server.
> I don't know much about SQLite, but one of the soft I use (bacula :
> www.bacula.org, a nice backup soft!), uses it, and it seems to works well.
>>What could
>> be done is a. Data from MySQL is copied to SQLite at various times b. We
>> use SQLite be default unless the user chooses otherwise c. We use it
>> seperate as a manual failback.
> So, if I understood well : SQLite as default, MySQL as an option, with a
> backup on SQLite. And we should begin with MySQL only, waiting for PHP5. I
> think I can agreed that.
>> Regrads,
>> McTails
>> Regrads,
>> Sonic McTails
>
> Regards,
>
> Stephane
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op¿ick
> _______________________________________________
> ErrorSystem-devel mailing list
> Err...@li...
> https://lists.sourceforge.net/lists/listinfo/errorsystem-devel
>