| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
318
|
Sat May 3 15:06:16 2003 |
 | Stefan Ritt | stefan.ritt@psi.ch | Other | | | Re: ELOG Skins Showcase |
> Let's share some inspiration. I'll post mine as soon as finished the re-
> look.
Excellent idea. I added a category "CSS File" in the logbook "Config
Examples" next to this forum. You can login with the same user name and
password as for this forum. As an example, I posted the new CSS file. Please
note that one need small changes in elogd.c to accomodate for the new 3D
look (basically don't display lines between cells), so it won't work very
nice with pre-2.3.7.
So everybody is invited to post his favourite CSS files an icons there.
Maybe we can even make a competition about the nicest ELOG icon... |
|
2114
|
Tue Jan 16 23:01:30 2007 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.6.3-1776 | Re: ELOG Crash by many email address |
| 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. |
|
2123
|
Tue Feb 6 18:19:57 2007 |
| Grant Jeffcote | grant@jeffcote.org | Bug report | Windows | 2.6.3-1776 | Re: ELOG Crash by many email address |
| 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 |
|
940
|
Sun Feb 13 17:21:19 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | V2.5.6-2 | Re: ELOG Command Line Utility |
> I am trying to use the command line utility elog. Some of the attributes
> that I have setup are multiple options. When I run the command line
> utility to create a new message, any attribute that is setup with multiple
> options will not be filled in. The syntax I am using is as follows:
>
> elog -h localhost -p 8080 -l Lab -a "Site=xxxx" -a "Area=System" -
> a "Priority=Low" -a "Shift=1" -a "Status=Open" -m text.txt
>
> Site and Area are defined in the config file as MOptions. Is there a way
> to use this feature with multiple options on attributes with the
> attributes = to one or more variables?
For MOptions, you have to append an "_n" to each attribute to distinguish
different options for the same attribute, like
elog -h localhost -p 8080 -l Lab -a "Site_0=Home" -a "Site_1=Work" ...
Even if you only use one attribute, the trailing "..._0" is necessary. I will
add a note to the documentation. |
|
68073
|
Wed Aug 5 12:09:47 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.0 | Re: ELOG 3.0 plus and MS Windows issues. |
I recompiled the executables according to
https://msdn.microsoft.com/en-us/library/jj851139.aspx
and replaces the elog311-1.exe distribution. Can you try if it works? Unfortunately I don't have a XP machine here.
/Stefan
| William Wong wrote: |
|
Greetings all. A few ELOG users have posted issues with ELOG 3.0 and newer not working with a variety of MS Windows operating systems,.
I have also encountered a similar problem in my environment.
For the following operating systems:
1) Windows XP SP3 (32-bit)
2) Windows Server 2003 SP 2 (32-bit)
when either elog.exe or elogd.exe are run from command line or file manager, the operating system reports the program is not a Win32 application.
I have other test computers that succesfully ran ELOG 3.0, 3.1 and 3.1.1
1) Windows Vista Enterprise (32-bit)
2) Windows 7 Professional (64-bit)
Has ELOG 3.x and newer changed in regards to support for MS Windows but is not documented on the
official ELOG documentation?
Any help would be most appreciated.
NOTE: The current production ELOG I use on Windows Server 2003 is 2.92-2475 but I would like to use the
features available on the 3,.x versions. Unfortunately, I am not able to change my production operating system.
|
|
|
68074
|
Wed Aug 5 23:36:29 2015 |
| William Wong | william.wong@fortisbc.com | Question | Windows | 3.0 | Re: ELOG 3.0 plus and MS Windows issues. |
Thank you for recompiling ELOG. Unfortunately, there is no change in all the test machines
I ran the newly compiled ELOG 3.1.1-1 on. I will use the 2.x version until our systems move
to a new operating system or I can find someone in my IT department who knows how to compile programs
from the source code.
If anyone else has suggestions or could compile the source for us to try, please speak up. There are
many installations of obsolete operating systems in production :
| Stefan Ritt wrote: |
|
I recompiled the executables according to
https://msdn.microsoft.com/en-us/library/jj851139.aspx
and replaces the elog311-1.exe distribution. Can you try if it works? Unfortunately I don't have a XP machine here.
/Stefan
| William Wong wrote: |
|
Greetings all. A few ELOG users have posted issues with ELOG 3.0 and newer not working with a variety of MS Windows operating systems,.
I have also encountered a similar problem in my environment.
For the following operating systems:
1) Windows XP SP3 (32-bit)
2) Windows Server 2003 SP 2 (32-bit)
when either elog.exe or elogd.exe are run from command line or file manager, the operating system reports the program is not a Win32 application.
I have other test computers that succesfully ran ELOG 3.0, 3.1 and 3.1.1
1) Windows Vista Enterprise (32-bit)
2) Windows 7 Professional (64-bit)
Has ELOG 3.x and newer changed in regards to support for MS Windows but is not documented on the
official ELOG documentation?
Any help would be most appreciated.
NOTE: The current production ELOG I use on Windows Server 2003 is 2.92-2475 but I would like to use the
features available on the 3,.x versions. Unfortunately, I am not able to change my production operating system.
|
|
|
|
Draft
|
Fri Aug 7 16:13:09 2015 |
| Richard Stamper | richard.stamper@stfc.ac.uk | Question | Windows | 3.0 | Re: ELOG 3.0 plus and MS Windows issues. |
| William Wong wrote: |
|
Thank you for recompiling ELOG. Unfortunately, there is no change in all the test machines
I ran the newly compiled ELOG 3.1.1-1 on. I will use the 2.x version until our systems move
to a new operating system or I can find someone in my IT department who knows how to compile programs
from the source code.
If anyone else has suggestions or could compile the source for us to try, please speak up. There are
many installations of obsolete operating systems in production :
| Stefan Ritt wrote: |
|
I recompiled the executables according to
https://msdn.microsoft.com/en-us/library/jj851139.aspx
and replaces the elog311-1.exe distribution. Can you try if it works? Unfortunately I don't have a XP machine here.
/Stefan
| William Wong wrote: |
|
Greetings all. A few ELOG users have posted issues with ELOG 3.0 and newer not working with a variety of MS Windows operating systems,.
I have also encountered a similar problem in my environment.
For the following operating systems:
1) Windows XP SP3 (32-bit)
2) Windows Server 2003 SP 2 (32-bit)
when either elog.exe or elogd.exe are run from command line or file manager, the operating system reports the program is not a Win32 application.
I have other test computers that succesfully ran ELOG 3.0, 3.1 and 3.1.1
1) Windows Vista Enterprise (32-bit)
2) Windows 7 Professional (64-bit)
Has ELOG 3.x and newer changed in regards to support for MS Windows but is not documented on the
official ELOG documentation?
Any help would be most appreciated.
NOTE: The current production ELOG I use on Windows Server 2003 is 2.92-2475 but I would like to use the
features available on the 3,.x versions. Unfortunately, I am not able to change my production operating system.
|
|
|
|
|
67283
|
Fri May 18 13:10:59 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.0 | Re: ELOG 'Dashboard' |
| NOCinator wrote: |
|
First, I really appreciate this software. Thank you.
Next, I have question - am wanting to have a 'dashboard' of sorts that shows all entries that are 'open'. That part is easy enough. But, then I want to color the time (or some other field) if the ELOG has not been updated/created for more than X hours. This will help us keep track of events that need status updates.
Doable?
Thanks!
|
Unfortunately not. What I would do is to define a quick filter, so with one click all 'open' entries are shown. Then you can look at the date column and see how long they have been open (actually when they have been submitted, so the difference you must calculate in your head!). |