Re: Formatting list page data, posted by Stefan Ritt on Thu Jun 25 15:02:55 2009
|
| Steve Williamson wrote: |
|
Thanks for a great piece of software - it does so much and is (mostly) so simple to use. However, I do have a suggestion that (for me, at least) would make it even better -
I use elog for a variety of logging tasks but find that, because I want to see as complete a summary as possible, the list page can get very crowded with longer fields wrapping over several lines. I would like to have more control over the way attributes are displayed here. Specifically, being able to truncate data (e.g. to show just the first n characters of a description), being able to select a substring (e.g. displaying characters before the '@' character to remove the domain from an email address or displaying characters after the space to remove the day from a date in ddd dd/mm/yy format) and being able to concatenate fields (e.g. to show a reference in a single cell as "Incident 1234" by joining call type and call reference attributes).
regards
Steve
|
Something along these lines is however not implemented (and hard to do). The only chance you have is to export your data into a spreadsheet and do the reformatting/report generation there. |
|
Re: Export and save problem with IE7, posted by Stefan Ritt on Thu Jun 25 15:37:14 2009
|
| soren poulsen wrote: |
|
Hi
Would it be possible to use the "Export to:" function with IE7 on the Forum logbook, and save the logbook.
I can do the export but saving the file with IE7 does not work. Saving the file with Firefox, Chrome, Safari works.
This makes me think that E-log is good and IE7 is bad ?
Soren
|
Right 
It seems to be a well known probmel with IE: http://classicasp.aspfaq.com/files/directories-fso/how-do-i-send-the-correct-filename-with-binarywrite.html
So I tried all variations there, but none of them worked. The interesting thing is that it works if you use it locally, but not with the forum (which has an additional "/elogs" in the URL).
|
attached picture size changed, posted by weiluo on Thu Jun 25 22:58:01 2009 
|
Hello everyone.
Here I found a problem recently with attaching screen-shot to the elog.
I am using "elog -f xxx/xxx.gif" to make elog entry. Recently I found my attached pictures were scaled to the half of the original size horizontally appearing in the log entry, the other half of the picture was filled with black. I need to click it once to magnify the picture to see it.
Does anyone know how to solve this problem? It bugs me a lot.
By the way, I saw some pictures were produced with the name "xxx.gif.png" in the logbook directory.
Thanks, and one of the modified picture is attached.
|
|
Re: attached picture size changed, posted by Stefan Ritt on Fri Jun 26 08:15:16 2009
|
| weiluo wrote: |
Hello everyone.
Here I found a problem recently with attaching screen-shot to the elog.
I am using "elog -f xxx/xxx.gif" to make elog entry. Recently I found my attached pictures were scaled to the half of the original size horizontally appearing in the log entry, the other half of the picture was filled with black. I need to click it once to magnify the picture to see it.
Does anyone know how to solve this problem? It bugs me a lot.
By the way, I saw some pictures were produced with the name "xxx.gif.png" in the logbook directory.
Thanks, and one of the modified picture is attached.
|
When you submit a picture, elogd calls the ImageMagick package to generate a thumbnail out of it, therefore you get the "xxx.gif.png" file (which represents the thumbnail). If you create your GIF images with the ROOT package, ImageMagick will give problems because ROOT does not use standard GIF encoding, therefor the black border on your pictures. You can turn off the thumbnail generation completely by specifying
Thumbnail size = 0
in the configuration file. This option was just introduced recently, so please update to SVN revision 2227 for this option to work. |
|
Re: Formatting list page data, posted by Steve Williamson on Fri Jun 26 14:34:58 2009
|
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
Thanks for a great piece of software - it does so much and is (mostly) so simple to use. However, I do have a suggestion that (for me, at least) would make it even better -
I use elog for a variety of logging tasks but find that, because I want to see as complete a summary as possible, the list page can get very crowded with longer fields wrapping over several lines. I would like to have more control over the way attributes are displayed here. Specifically, being able to truncate data (e.g. to show just the first n characters of a description), being able to select a substring (e.g. displaying characters before the '@' character to remove the domain from an email address or displaying characters after the space to remove the day from a date in ddd dd/mm/yy format) and being able to concatenate fields (e.g. to show a reference in a single cell as "Incident 1234" by joining call type and call reference attributes).
regards
Steve
|
Something along these lines is however not implemented (and hard to do). The only chance you have is to export your data into a spreadsheet and do the reformatting/report generation there.
|
Thanks for looking at the suggestion - it was only a 'nice to have', whereas elog is an essential!
regards |
|
Re: attached picture size changed, posted by weiluo on Fri Jun 26 17:04:23 2009
|
| Stefan Ritt wrote: |
| weiluo wrote: |
Hello everyone.
Here I found a problem recently with attaching screen-shot to the elog.
I am using "elog -f xxx/xxx.gif" to make elog entry. Recently I found my attached pictures were scaled to the half of the original size horizontally appearing in the log entry, the other half of the picture was filled with black. I need to click it once to magnify the picture to see it.
Does anyone know how to solve this problem? It bugs me a lot.
By the way, I saw some pictures were produced with the name "xxx.gif.png" in the logbook directory.
Thanks, and one of the modified picture is attached.
|
When you submit a picture, elogd calls the ImageMagick package to generate a thumbnail out of it, therefore you get the "xxx.gif.png" file (which represents the thumbnail). If you create your GIF images with the ROOT package, ImageMagick will give problems because ROOT does not use standard GIF encoding, therefor the black border on your pictures. You can turn off the thumbnail generation completely by specifying
Thumbnail size = 0
in the configuration file. This option was just introduced recently, so please update to SVN revision 2227 for this option to work. |
Thanks a lot for the detailed explanation! It works! |
|
Elog Crashes, posted by lance on Mon Jul 20 09:26:41 2009
|
Stefan,
Our log is crashing on a regular basis and I have been unable to identify the reason. Now the if the log crashes that is not a major problem however when you try to stop the daemon from the services it fails to stop. This means that the daemon cannot be restarted. The only way then is to start killing processes. This is not something I want none experienced guys to do.
Looking at the processes is look like the elogd.exe is still running and doesn’t die when you try to stop the daemon service.
I checked the times it was crashing with events in the elog logfiles but there was nothing actually happening at these times. It seems something is causing it to just hang.
I have attached the eventlog files for you if you have any ideas I would appreciate them.
I have not run the log in verbose mode as I have thus far been unable to redirect the output of the screen in order to see what is happening. If you have any tips on how to redirect the output I would save the file for off line analysis. Our log is used 24/7 therefore it is critical that it be kept running so if I was to run it with the –v option the guys would have to restart it and I would lose the data.
Any help is much appreciated
Regards,
Lance |
|
Re: Elog Crashes, posted by Stefan Ritt on Mon Jul 20 10:30:44 2009
|
| lance wrote: |
|
Stefan,
Our log is crashing on a regular basis and I have been unable to identify the reason. Now the if the log crashes that is not a major problem however when you try to stop the daemon from the services it fails to stop. This means that the daemon cannot be restarted. The only way then is to start killing processes. This is not something I want none experienced guys to do.
Looking at the processes is look like the elogd.exe is still running and doesn’t die when you try to stop the daemon service.
I checked the times it was crashing with events in the elog logfiles but there was nothing actually happening at these times. It seems something is causing it to just hang.
I have attached the eventlog files for you if you have any ideas I would appreciate them.
I have not run the log in verbose mode as I have thus far been unable to redirect the output of the screen in order to see what is happening. If you have any tips on how to redirect the output I would save the file for off line analysis. Our log is used 24/7 therefore it is critical that it be kept running so if I was to run it with the –v option the guys would have to restart it and I would lose the data.
Any help is much appreciated
Regards,
Lance
|
Using the Windows event log won't help much. I guess in your case elogd is driven into some kind of endless loop (does the CPU go to 100%???). There are only two possibilities to tackle this:
1) You find a way to reliably reproduce this problem, tell me how to do this. When I can reproduce it here, I can fix it easily.
2) You do debugging yourself. Under Linux this is simple, since you have debuggers on most systems. Under Windows however, you first have to install the Visual C++ development environment. I believe there is a free version (Express?) which you can use. You then run elogd under the debugger, and when it hangs you investigate where. This needs some basic knowledge about C++ development and I'm not sure if you have this, but maybe you can find someone around you who does. |
|