| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69716
|
Mon Jan 8 16:18:45 2024 |
 | Dr Marta Divall | marta.divall@epfl.ch | Question | Windows | ELOG V3.1.3-a38 | Re: Maximum number of attributes | To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome.
| David Pilgram wrote: |
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes. In your case suffixes may be better, but I hope you get the point.
Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.
| Dr Marta Divall wrote: |
|
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best,
Marta
| Stefan Ritt wrote: |
|
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best,
Stefan
| Dr Marta Divall wrote: |
|
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks!
|
|
|
|
|
|
69717
|
Mon Jan 8 16:25:05 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V3.1.3-a38 | Re: Maximum number of attributes | Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in full text search.
Stefan
| Dr Marta Divall wrote: |
|
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome.
| David Pilgram wrote: |
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes. In your case suffixes may be better, but I hope you get the point.
Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.
| Dr Marta Divall wrote: |
|
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best,
Marta
| Stefan Ritt wrote: |
|
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best,
Stefan
| Dr Marta Divall wrote: |
|
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks!
|
|
|
|
|
|
|
69718
|
Mon Jan 8 17:30:42 2024 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | ELOG V3.1.3-a38 | Re: Maximum number of attributes | Or what about the "ticket number" feature? Every new entry thread (sorry, confusing terminology on my part) would increment the ticket number by one, and there is no limit as far as I am aware. This is all explained in the elogd configuration documentation.
| Stefan Ritt wrote: |
|
Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in full text search.
Stefan
| Dr Marta Divall wrote: |
|
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome.
| David Pilgram wrote: |
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes. In your case suffixes may be better, but I hope you get the point.
Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.
| Dr Marta Divall wrote: |
|
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best,
Marta
| Stefan Ritt wrote: |
|
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best,
Stefan
| Dr Marta Divall wrote: |
|
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks!
|
|
|
|
|
|
|
|
69719
|
Mon Jan 8 21:08:43 2024 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | ELOG V3.1.3-a38 | Re: Maximum number of attributes | As for my suggestion earlier, now I'm at my computer with working elog. I think that the following four lines (three I guess already there but need alteration for this) need to appear in your elogd.conf file. The first three should also include any other thing you need to display etc. I've cut this down to the bear bones, and ... means anything else you want to add.
Attributes = Die, Organisation, ...
List display = Die, Organisation. ...
Thread display = $Die: $Organisation ...
Preset Die = D_#####
Now the first time you run this, it will give D_00001. You can edit that to D_00100 and it will increment from there. You may wish to have two types of user, those who can start a new thread, such as yourself, and others who can contribute but not start a new thread / new Die discussion.
Now it may be that the attribute name you gave D_001 etc can be used where I have used "Die" here, which would appear to give a seemless transition. and perhaps without the need of editing the first new thread.
I have tried these as changes to an existing logbook on my system. and they appeared to work fine. but in my case as a single user, I could always change the Die number, a feature I guess you do not want. I guess there is a way in the config file, but I'm running out of steam for today. David.
| David Pilgram wrote: |
|
Or what about the "ticket number" feature? Every new entry thread (sorry, confusing terminology on my part) would increment the ticket number by one, and there is no limit as far as I am aware. This is all explained in the elogd configuration documentation.
| Stefan Ritt wrote: |
|
Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in full text search.
Stefan
| Dr Marta Divall wrote: |
|
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome.
| David Pilgram wrote: |
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes. In your case suffixes may be better, but I hope you get the point.
Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.
| Dr Marta Divall wrote: |
|
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best,
Marta
| Stefan Ritt wrote: |
|
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best,
Stefan
| Dr Marta Divall wrote: |
|
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks!
|
|
|
|
|
|
|
|
|
1566
|
Thu Dec 22 15:14:39 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.6.0 | Re: Maximum number of LogBooks? Bug? |
| Mike wrote: | Is there a Maximum number logbooks?
I have run into a problem but I'm not sure if to call it a Bug or not. We have started using Elog to keep a work log for each of our production servers. After a short trial I put generated a config file using groups for all of our servers which is 294 logbooks. Almost every thing works except the config screen. You get a list of all the logbooks with the checkboxes for the email notifications. If you click save (Doesn't make a difference if you make changes or not) you get the following.
Error: Too many parameters (> 120). Cannot perform operation.
I was able to recompile using cygwin under windows after changing MAX_PARAM from 120 to 400. That fixes the problem, but eventually you get a stack overflow.
Any suggestions? I have considered separate instances running 100 logbooks each but I would like to have a global search.
Thanks for a Great tool. I've been using it as a personal log for sometime and was finally able to convince my team we sould use it. |
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. |
|
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 |
|
67857
|
Fri Apr 10 08:37:19 2015 |
| Oliver Kleinau | oliver.kleinau@it.niedersachsen.de | Question | Linux | 3.1 | Re: Max Logbooks for Email notify | It seems to be the GET buffer of the elog-Server. The GET statement is cut off after &sub_lb72=1&sub_ eg. 1000 chars.
| Oliver Kleinau wrote: |
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
|
|
67858
|
Fri Apr 10 09:59:42 2015 |
| Oliver Kleinau | oliver.kleinau@it.niedersachsen.de | Question | Linux | 3.1 | Re: Max Logbooks for Email notify | It was str variable in function process_http_request in elogd.c.
This should have the size of received buffer.
PROBLEM SOLVED!!!
| Oliver Kleinau wrote: |
|
It seems to be the GET buffer of the elog-Server. The GET statement is cut off after &sub_lb72=1&sub_ eg. 1000 chars.
| Oliver Kleinau wrote: |
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
|
|
|