| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1567
|
Thu Dec 22 15:39:23 2005 |
 | Mike | mlmoore@pella.com | Question | | 2.6.0 | Re: Maximum number of LogBooks? Bug? |
| Stefan Ritt wrote: |
You're really pushing to the limit 
The maximum number of logbooks is indeed 120. If you have too many logbooks, they are also hard to handle (too many check boxes in the config page etc.). What if you make not one logbook per server, but have a single logbook and use the server as an attribute, like
Attributes = ..., Server, ...
Options Server = Server1, Server2, ...
Now you can ask: How many options are possible for an attribute, and the answer is 100, which is even less than the number of logbooks. But you can make three logbooks, each covering 100 servers, and that covers your 294 servers. |
Thanks for the quick reply and suggestion. I will give that a try.
You might want to consider adding a check that there aren't over 120 logbooks. I manually created the elog.cfg with 294 logbooks. Everything works, except for running into this problem.
Thanks again |
|
1569
|
Thu Dec 22 21:15:19 2005 |
 | Edmundo T Rodriguez | edrodrig@chpnet.org | Request | | 2.6.0 | "Syntax of elogd.cfg" - Document |
The document "ELOG - Syntax of elogd.cfg" is outdated!
Are we going to have an updated documented?
How much difference exists between the one posted as a reference
and new one covering all new options in ELOG? |
|
1570
|
Fri Dec 23 09:07:14 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | 2.6.0 | Re: "Syntax of elogd.cfg" - Document |
| Edmundo T Rodriguez wrote: | | The document "ELOG - Syntax of elogd.cfg" is outdated! |
I forgot to update the web server, but the document distributed in the 2.6.0 package was up to date.
| Edmundo T Rodriguez wrote: | | Are we going to have an updated documented? |
I copied the actual version to the web server.
| Edmundo T Rodriguez wrote: | How much difference exists between the one posted as a reference
and new one covering all new options in ELOG? |
For the changes from one version to the other, have a look at the changelog. |
|
1571
|
Tue Jan 3 17:20:16 2006 |
 | Mike | mlmoore@pella.com | Bug report | | V2.6.0 | elogd 2.6.0 crash on password Forgot? |
I have been having a repeatable crash on V2.6.0 everytime someone tries to recover a password using the option from the login screen. See attachment for a jpg of the message.
This is occuring on windows 2003. But I have also tested it on windows XP and it occurs there as well. In addition on XP I did a generic installtion and added the password option to the DEMO application and it fails there as well.
Mike |
| Attachment 1: elog-pw-crash.jpg
|
|
|
1579
|
Tue Jan 10 00:32:19 2006 |
 | David Brody | dbrody@echo-inc.com | Question | | 2.5.8-2 | Date imports from CSV incorrectly |
When I import from a CSV file, dates formatted as mm/dd/yy always get imported as 12/31/1969
Here are the parameters I am using for dates:
Attributes = Ticket #, Status, Assigned To, Status Date, Install Date, Category, Activity, Environment, Component, TstTrk
Type Status Date = date
Type Install Date = date
Date format = %A, %d %B, %Y
Preset Status Date = $date
Thanks!
DB |
|
1581
|
Tue Jan 10 19:30:09 2006 |
| David Brody | dbrody@echo-inc.com | Question | | 2.5.8-2 | Re: Date imports from CSV incorrectly |
| David Brody wrote: | When I import from a CSV file, dates formatted as mm/dd/yy always get imported as 12/31/1969
Here are the parameters I am using for dates:
Attributes = Ticket #, Status, Assigned To, Status Date, Install Date, Category, Activity, Environment, Component, TstTrk
Type Status Date = date
Type Install Date = date
Date format = %A, %d %B, %Y
Preset Status Date = $date
Thanks!
DB |
Never mind. I figured it out! |
|
1588
|
Thu Jan 12 16:06:16 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.6.0-beta | Re: Thread sort / display order |
| Michael Husbyn wrote: | Is there a way to choose the display order in threaded mode.
Eg:
1 Test
2 Version 2.0 Testing 1
3 Version 2.5 Testing 2
4 Version 2.3 Testing 3
But the preferred sort order (not the ID) is something like this:
1 Test
2 Version 2.0 Testing 1
4 Version 2.3 Testing 3
3 Version 2.5 Testing 2
Example of parameter perhaps:
Thread order = Field1, $id
Or is this something too difficult to implement? Or already there?
Best regards
Michael Husbyn |
In summary mode, you can sort by clicking on a column header. You will then see something like
http://.../?sort=Field1
in the address bar. If you now switch to threaded display, this vanishes of course, but you can put a
Start page = ?sort=Field1
into your config file. Use sort for ascending order, rsort for descending order. |
|
1595
|
Tue Jan 17 01:01:05 2006 |
| Jason Koglin | koglin@astro.columbia.edu | Question | | V2.6.0 | localhost definition problem |
I've been running elog on my laptop for about a year. I have had a problem several times now when I have had a bad crash of my computer that afterwards elog does not run correctly. The problem appears to be that "localhost" (e.g., http://localhost:8080/) gets changed to a domain name (http://sylvester.columbia.edu:8080/) which is not registered. I only want it to access this elog database locally on my machine and do not even want to set it up as a web server.
I freshly installed it and when I type in http://localhost:8080/ it sends me to http://localhost:8080/demo/ . If I click on the first and only entry it sends me to http://sylvester.columbia.edu:8080/demo/1 and an error occurs loading the page. However if I type in http://localhost:8080/demo/1 it brings up the first entry correctly, but with no formatting because presumably it is looking in the wrong place for the default theme.
How do I fix this since this time reinstalling and rebooting hasn't fixed the problem?
Thanks,
Jason. |