Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 801 of 801  Not logged in ELOG logo
    Reply   , posted by on Mon Nov 15 13:24:44 2004 
> > I didn't see the RSS button in Firefox, however the URL:
> > 
> >  	http://midas.psi.ch/elogs/Forum/elog.rdf
> > works fine in with Bloglines (http://www.bloglines.com/myblogs
> 
> You need Firefox 1.0 Preview or later.
> 
> > I've installed the lastest elog (v2.5.5)--how do I turn it on for a particular
> > logbook?
> 
> It's on by default for all logbooks.

Hmmm, I've made some entries to several logbooks (running 2.5.5), but I still don't
see the elog.rdf file:

find /usr/local/elog -name elog.rdf

<no files found>
Entry   , posted by on Fri Dec 3 08:43:49 2004 
God really STRANGE and problematic effect on 2.5.5-1 (can't remember it this
was with 2.5.5 or 2.5.4-X but i'm nearly sure it worked well):

Entering a date (Formate Bithday = date) may crash down the server:
Value is 22.2.2004: Everything is well
Value is 22.2.1962: Server crashes emmediatly (menas restarzing several
times, always the same problem)

I do not have time to check true all the years for finding out where the
problem may beginn, sorry. Also I was not able to check on other systems
right now. My system: Win XP Pro SP 1, IE 6 as well as Mozilla Calssic 1.7.3. 

Didn't check it under Linux right know in case of a lot work.

Clould you this fix please Stefan???  THANK'X!!!
    Reply   , posted by on Tue Mar 1 19:41:29 2005 

For some reason it looses the "m" so line 5 instead of having
"hh:mm" has "hh: m"


Please ideas ;)
Cheers,
GL.
    Reply   , posted by on Tue Mar 1 19:41:29 2005 

For some reason it looses the "m" so line 5 instead of having
"hh:mm" has "hh: m"


Please ideas ;)
Cheers,
GL.
Entry   , posted by on Tue Mar 1 19:41:29 2005 
 
Entry   , posted by on Sat Oct 6 14:05:01 2007 

I ended with 125384 entries like the one above.

Everything works fine but ......... [U]tteerrrriibbllee[/U] [B]slow[/B].  CPU usage is constant at 99%.  

I tried to split the one file produced by the import into 2 chunks but that did not improve the situation.

My question is : Is there a rule of thumb for the size of the "database" in which elog keeps it's performance, or better : is there a solution for this for elog.


 
Entry   , posted by on Wed Mar 24 15:07:14 106 
 
Entry   , posted by on Wed Mar 24 15:07:14 106 
 
ELOG V3.1.5-3fb85fa6