| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1788
|
Mon Apr 3 17:09:19 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
| Steve Jones wrote: | | BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No. |
There is a 2.6.1-4 version for Windows for download, which contains the most recent code. |
|
1800
|
Fri Apr 7 05:07:20 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No. |
There is a 2.6.1-4 version for Windows for download, which contains the most recent code. |
| Quote: | Ok, I loaded the new Windows version ELOG V2.6.1-1681. The new version has the same behavior and it is entirely related to Top Group. With a simple Top Group setup things appear to work fine until one attempts to either create or delete a new logbook. There are other quirky things - I don't think Top Group is ready for really complex setups. In fact, this URL that is constructed by elog (http://localhost:8080/Engineering%20Compute%20Change%20Logs/Test/?cmd=Config) will cause elog to coredump but only with a very complex configfile. If I simply remove the "Top" from the "Group" directive I get the expected message "Error: logbook "Engineering Compute Change Logs" not defined in elogd.cfg
Please use your browser's back button to go back".
Another interesting point of reference - I went back to 2.5.9-4 (windows) and get the same behavior.
Now, making things really simple I added Top Group support to the demo that comes with the Windows install. This configfile:
[global]
port = 8080
Show top groups = 1
Top Group Demo Groups = demo, test7
[global Demo Groups]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
[demo]
results in this redisplay after a new logbook create I have included in an attached screenshot. Please note that everything is generally not correct. So, even though eLog does not crash with this simple config it does support my observation that as I render the congfile more complex I corrupt eLog more until it finally crashes. Stefan, I would be interested in seeing how the above config runs on one of your windows systems. |
| Attachment 1: elog_2.JPG
|
|
|
1818
|
Thu May 4 17:26:41 2006 |
 | Alex H | alex@synergie-inf.com | Question | Windows | 2.6.1-1668 | Date automatically generated by another one | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
|
1819
|
Fri May 5 07:58:53 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.1-1668 | Re: Date automatically generated by another one |
| Alex H wrote: | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
No, this is not implemented right now. |
|
1820
|
Fri May 5 09:01:04 2006 |
| Alex H | alex@synergie-inf.com | Question | Windows | 2.6.1-1668 | Re: Date automatically generated by another one |
| Stefan Ritt wrote: |
| Alex H wrote: | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
No, this is not implemented right now. |
OK! Thank for your response. |
|
1748
|
Sat Mar 4 06:08:29 2006 |
 | Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Crafted URL causes elog to coredump | While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.
Can this be reproduced by others? |
|
1752
|
Mon Mar 6 14:04:12 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
| Steve Jones wrote: | While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.
Can this be reproduced by others? |
No. This forum has the "elog" as the top group, "Forum" as the logbook, so if I write
http://midas.psi.ch/elogs/elog/Forum
it does not crash. |
|
1753
|
Mon Mar 6 17:35:52 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1660 | Re: Crafted URL causes elog to coredump |
| Stefan Ritt wrote: |
| Steve Jones wrote: | While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.
Can this be reproduced by others? |
No. This forum has the "elog" as the top group, "Forum" as the logbook, so if I write
http://midas.psi.ch/elogs/elog/Forum
it does not crash. |
|
|
|
ELOG V3.1.5-3fb85fa6 |