suggestion for "new user registration" page, posted by Mark Bergman on Sat May 6 02:12:10 2006
|
I'm testing elog, and one user was having difficulty creating a new account for himself. This problem had three reasons:
1. the user expected a "submit" button or some other way to exit the account registration screen to appear near the password boxes, at the bottom of the |
Re: suggestion for "new user registration" page, posted by Stefan Ritt on Thu Nov 9 22:40:06 2006
|
[quote="Mark Bergman"]Suggestions for improving the registration page:
Put a "submit" button after the password entry.
|
Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 16 16:20:06 2006
|
Hi Stefan,
I have posted an entry of approximately a thousand lines (ten thousand words). Posting it took some time, which is logical to a certain degree. However, |
|
Re: Problem with large entry size, posted by Stefan Ritt on Mon Oct 16 16:53:43 2006
|
[quote="Dimitrios Tsirigkas"]I have posted an entry of approximately a thousand lines (ten thousand words). Posting it took some time, which is logical
to a certain degree. However, whenever a user asks for "Full" view of the logbook, the page takes around two minutes to load and the CPU usage on the elog
server goes to beyond 90% for all this time. Is this to be expected for an entry of that size or is there something going wrong here?[/quote]
|
|
Re: Problem with large entry size, posted by Stefan Ritt on Mon Oct 16 17:18:58 2006
|
I improved the performance by some factor in SVN revision 1733. Can you give it a try and report your speed improvement? Depending on the result, I can
probably do even a bit better with some more effort.
|
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 16 17:32:58 2006
|
[quote="Stefan Ritt"]I improved the performance by some factor in SVN revision 1733. Can you give it a try and report your speed improvement? Depending
on the result, I can probably do even a bit better with some more effort.
|
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:39:29 2006
|
[quote="Stefan Ritt"]
The problem lies in the ELCode parsing. When you post an entry in ELCode form, the elogd server has to parse every word to see if it's any of the ELcode
tags. This is right now implemented in a kind of poor way, such that it takes very long for long entries. I will work to optimize that. In the meantime, |
|
Re: Problem with large entry size, posted by Stefan Ritt on Tue Oct 17 14:42:58 2006
|
[quote="Dimitrios Tsirigkas"]I was wondering what is the cleanest way of changing old entries already submitted in ELCode into plain text. If I do not include
ELCode in the allowed encodings does this apply to already submitted entries as well or will they still be treated as ELCode?[/quote]
|
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Tue Oct 17 14:47:53 2006
|
Thanks Stefan,
[quote="Stefan Ritt"] Did you try the new version, would be interesting to see if it's any better... [/quote]
|
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Mon Oct 23 12:53:08 2006
|
Hi Stefan,
A lot of performance-related trouble for us comes from the ability of users to click on "All" and display thousands of entries on the same page. Is there |
|
Re: Problem with large entry size, posted by Stefan Ritt on Tue Oct 24 21:58:54 2006
|
[quote="Dimitrios Tsirigkas"]Hi Stefan,
A lot of performance-related trouble for us comes from the ability of users to click on "All" and display thousands of entries on the same page. Is there |
|
Re: Problem with large entry size, posted by Dimitrios Tsirigkas on Thu Nov 2 10:14:11 2006
|
[quote="Stefan Ritt"]What about a threshold for the "All" display? If a logbook contains less than, let's say, 500 entries, the "All" link is displayed,
and above 500 entries it's hidden. Would that make sense?[/quote]
|
|
Re: Problem with large entry size, posted by Stefan Ritt on Thu Nov 9 21:22:27 2006
|
[quote="Dimitrios Tsirigkas"][quote="Stefan Ritt"]What about a threshold for the "All" display? If a logbook contains less than, let's say, 500 entries,
the "All" link is displayed, and above 500 entries it's hidden. Would that make sense?[/quote]
|
|
ELCode, posted by Alexandre Lindote on Wed Oct 25 18:00:24 2006
|
Hi,
can you think of any obvious reason why the ELCode would not work in the logbooks I set up?
|
|
Re: ELCode, posted by Stefan Ritt on Wed Oct 25 19:44:11 2006
|
[quote="Alexandre Lindote"]can you think of any obvious reason why the ELCode would not work in the logbooks I set up?[/quote]
There is a good reason why this forum contains a [B]ELOG Version[/B] tag which you are supposed to fill out for new entries. Without knowing which version |
|
Re: ELCode, posted by Alexandre Lindote on Wed Oct 25 21:52:13 2006
|
[quote="Stefan Ritt"][quote="Alexandre Lindote"]can you think of any obvious reason why the ELCode would not work in the logbooks I set up?[/quote]
There is a good reason why this forum contains a [B]ELOG Version[/B] tag which you are supposed to fill out for new entries. Without knowing which version |
|
Re: ELCode, posted by Alexandre Lindote on Fri Oct 27 13:02:50 2006
|
[quote="Alexandre Lindote"]Hi,
can you think of any obvious reason why the ELCode would not work in the logbooks I set up?
|
|
Re: ELCode, posted by Stefan Ritt on Thu Nov 9 21:03:03 2006
|
[quote="Alexandre Lindote"][quote="Alexandre Lindote"]Hi,
can you think of any obvious reason why the ELCode would not work in the logbooks I set up?
|
|
calling a shell in the Options tag, posted by Alexandre Lindote on Tue Oct 31 20:05:07 2006
|
Hi,
is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
|
|
Re: calling a shell in the Options tag, posted by Steve Jones on Tue Oct 31 22:07:06 2006
|
[quote="Alexandre Lindote"]Hi,
is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
|
|
Re: calling a shell in the Options tag, posted by Alexandre Lindote on Wed Nov 1 09:53:05 2006
|
[quote="Steve Jones"][quote="Alexandre Lindote"]Hi,
is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
|
|
Re: calling a shell in the Options tag, posted by Stefan Ritt on Thu Nov 9 20:59:01 2006
|
[quote="Alexandre Lindote"]Hi,
is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
|
|
Denial of Service Vulnerability of elog 2.6.2-6, posted by Stefan Ritt on Wed Nov 8 13:59:52 2006
|
Dear ELOG users,
a denial of service vulnerability has been reported which affects all elog versions prior to 2.6.2-7. With a special request one can crash the elogd server, |
SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Mon Sep 18 20:35:44 2006 
|
On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system call) and shows precisely
where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively". Both runs are as root,
simply one with and one without the "-D" |
|
Re: SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Mon Sep 18 22:09:23 2006
|
[quote="Steve Jones"]On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system
call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively".
Both runs are as root, simply one with and one without the "-D"[/quote]
|
|
Re: SVN1714 will not run in 'daemon" mode on Solaris8, posted by Stefan Ritt on Fri Sep 22 07:47:58 2006
|
[quote="Steve Jones"]On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system
call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively".
Both runs are as root, simply one with and one without the "-D"[/quote]
|
|
Re: SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Fri Sep 22 19:32:45 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a
dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it
runs but "interactively". Both runs are as root, simply one with and one without the "-D"[/quote]
|
|
Re: SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Fri Sep 22 22:12:18 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a
dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it
runs but "interactively". Both runs are as root, simply one with and one without the "-D"[/quote]
|
|
Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Tue Oct 10 23:29:53 2006
|
[quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS
(which provides a dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where it errors out and
the other where it runs but "interactively". Both runs are as root, simply one with and one without the "-D"[/quote]
|
|
Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Wed Oct 11 00:19:05 2006
|
[quote="Steve Jones"][quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]On Solaris, SVN1714 will not go into daemon mode. Running the compiled
version under TRUSS (which provides a dump of every system call) and shows precisely where elog is failing. I have attached two TRUSS outputs: one where
it errors out and the other where it runs but "interactively". Both runs are as root, simply one with and one without the "-D"[/quote]
|
|
Re: SVN1723 (was SVN1714) will not run in 'daemon" mode on Solaris8, posted by Stefan Ritt on Wed Oct 11 08:18:14 2006
|
[quote="Steve Jones"]There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but the the non-daemn
mode also sets to nobody and works fine.[/QUOTE]
|
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Thu Oct 26 21:54:40 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but
the the non-daemn mode also sets to nobody and works fine.[/QUOTE]
|
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Stefan Ritt on Wed Nov 8 08:20:34 2006
|
[quote="Steve Jones"]BUG: In the initial comment section of elogd_fancy.cfg the line [CODE]# This [global] section contains settings common to all logbooks[/CODE]
is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking
"[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting |
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Wed Nov 8 12:55:58 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]BUG: In the initial comment section of elogd_fancy.cfg the line [CODE]# This [global] section contains settings
common to all logbooks[/CODE] is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup
the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine |
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode, posted by Stefan Ritt on Wed Nov 8 13:07:31 2006
|
[quote="Steve Jones"]Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately
after that "cd /" test that things appeared to start not working - basically, elogd could not find anything.[/quote]
|
|
Bug? Password file location changed, posted by David Spindler on Thu Nov 2 18:02:44 2006
|
I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid. I tried this on 2 machines
and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password file in a different
location.
|
|
Re: Bug? Password file location changed, posted by David Spindler on Thu Nov 2 18:10:07 2006
|
[quote="David Spindler"]I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my password to be invalid.
I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was creating a new empty password
file in a different location.
|
|
Re: Bug? Password file location changed, posted by Steve Jones on Thu Nov 2 23:17:10 2006
|
[quote="David Spindler"][quote="David Spindler"]I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the elog, it showed my
password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command prompt that it was
creating a new empty password file in a different location.
|
|
Re: Bug? Password file location changed, posted by David Spindler on Fri Nov 3 14:40:36 2006
|
[quote="Steve Jones"][quote="David Spindler"][quote="David Spindler"]I just tried to upgrade from 2.6.1-1633 to 2.6.2-1734. Whenever I tried to access the
elog, it showed my password to be invalid. I tried this on 2 machines and same results. I did notice on the second one when I started it from a command
prompt that it was creating a new empty password file in a different location.
|
|
Re: Bug? Password file location changed, posted by Stefan Ritt on Tue Nov 7 09:22:52 2006
|
[quote="David Spindler"]Thanks. I checked the changelog and the documentation for any such changes but did not see them. I just looked again, and still
do not see them. Anyway, I know what to expect, now, and will adjust. Again, thanks![/quote]
|
|
Push button for Menue Command, posted by An Thai on Fri Nov 3 15:53:44 2006
|
Dear Stefan,
in your documentation: ELOG - Syntax of elog.cfg I see two screenshots in the Themes section. The left one shows a layout with Push buttons on the Menue |
|
Re: Push button for Menue Command, posted by Stefan Ritt on Tue Nov 7 08:38:57 2006
|
[quote="An Thai"]Dear Stefan,
in your documentation: ELOG - Syntax of elog.cfg I see two screenshots in the Themes section. The left one shows a layout with Push buttons on the Menue |