elog start with number of entries are zero (0) for all logbook, posted by pirat sriyotha on Wed Dec 23 08:47:35 2009
|
hi sirs,
am using freebsd, this morning i started elog and did a few record with no problem.
just this afternoon when i enter firefox3 http://localhost:8000/, i got zero number of records for all of my logbooks.
but the data are not erased though.
any idea would be appreciated.
regards,
jotawski
|
ELOG Crash by many email address, posted by An Thai on Fri Jan 12 15:28:46 2007
|
Hello,
when I try to set above 112 email addresses in
"Email All = ..."
the Elog service will crash with the error ntdll.dll or memory addresses x0000000.
This problem does not happen when I reduce the number of email addresses.
Have you had the same problem? |
Re: ELOG Crash by many email address, posted by Stefan Ritt on Tue Jan 16 23:01:30 2007
|
An Thai wrote: | Hello,
when I try to set above 112 email addresses in
"Email All = ..."
the Elog service will crash with the error ntdll.dll or memory addresses x0000000.
This problem does not happen when I reduce the number of email addresses.
Have you had the same problem? |
I fixed that crash in the current version, but there is actually a limit of 100 email addresses. So anyhow you won't get the 12 ones above 100. I will try to increase that limit in the next version of elog. |
Re: ELOG Crash by many email address, posted by Grant Jeffcote on Tue Feb 6 18:19:57 2007
|
Stefan Ritt wrote: |
An Thai wrote: | Hello,
when I try to set above 112 email addresses in
"Email All = ..."
the Elog service will crash with the error ntdll.dll or memory addresses x0000000.
This problem does not happen when I reduce the number of email addresses.
Have you had the same problem? |
I fixed that crash in the current version, but there is actually a limit of 100 email addresses. So anyhow you won't get the 12 ones above 100. I will try to increase that limit in the next version of elog. |
Hi Stefan,
I'm also having a problem in the latest version with Elog crashing with multiple email addresses.
I am using 'MOptions' for email list selection using the execute shell script to send a predefined list (ie. the email list is in a text file not in the Elog config).
It seems when the list contains exactly 9 addresses it causes Elog to crash with a failure similar to An's, any less or any more and they are sent fine? Also when certain combinations of multiple list selections are made the Elog process will also crash? I am running the Elog process as an application (ie. not as a service, as per An's workaround) as it's the only way I can get the -x switch to work with Windows, this means the Elog daemon has to be manually restarted. Running WinXP SP2.
Any suggestions?
Thx |
Is there (planned) support for <A NAME> and <HR /> in ELCODE?, posted by Kevin McCarty on Thu Apr 26 16:43:45 2007
|
Hello,
I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. This would be useful for long log messages in order to provide a table of contents and divide them into clear sections. If this support already exists, I'm afraid it is not obvious to me how to access it in ELCODE. If it does not yet exist, would you consider a patch for it?
As a related issue, to support <a name> usefully, it will also be necessary for ELCODE to support things like [url=#tag], which it currently converts to <a href = "http:///#tag"> instead the expected result of <a href = "#tag">.
(Please send me replies also by email at kmccarty AT princeton DOT edu, as I don't check this forum often.)
Thanks for writing ELOG; our group has been using it very productively on our server for the last few weeks.
best regards,
-- Kevin McCarty |
Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE?, posted by Stefan Ritt on Fri Apr 27 08:38:58 2007
|
Kevin McCarty wrote: | I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. |
Very good idea. The horizontal line is already implemented via [LINE] and the anchor tag will soon follow. |
Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE?, posted by Kevin McCarty on Fri Apr 27 08:56:10 2007
|
Stefan Ritt wrote: |
Kevin McCarty wrote: | I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. |
Very good idea. The horizontal line is already implemented via [LINE] and the anchor tag will soon follow. |
Wonderful, thanks!
-- Kevin McCarty |
Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE?, posted by Stefan Ritt on Fri Apr 27 13:06:59 2007
|
Kevin McCarty wrote: | I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. This would be useful for long log messages in order to provide a table of contents and divide them into clear sections. If this support already exists, I'm afraid it is not obvious to me how to access it in ELCODE. If it does not yet exist, would you consider a patch for it?
As a related issue, to support <a name> usefully, it will also be necessary for ELCODE to support things like [url=#tag], which it currently converts to <a href = "http:///#tag"> instead the expected result of <a href = "#tag">. |
I implemented anchor tags. You can write something like
[ANCHOR]top[/ANCHOR]
and you can then reference it either by directly entering
http://midas.psi.ch/elogs/Forum/2223#top
or by entering simply
elog:2223#top
To make your table of contents, you can put a complete URL tag like
[URL=http://midas.psi.ch/elogs/Forum/2223#top]Goto top[/URL]
or inside the same entry simply
[URL=#top]Goto top[/URL]
which will be shown as
Goto top
I have added these link again at the bottom of this entry so you can try it with this entry directly.
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
elog:2223#top |