Re: Maximum number of attributes, posted by Dr Marta Divall on Mon Jan 8 16:18:45 2024
|
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. |
|
Re: Maximum number of attributes, posted by Stefan Ritt on Mon Jan 8 16:25:05 2024
|
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 |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 17:30:42 2024
|
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 |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 21:08:43 2024
|
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. |
|
Re: Maximum number of LogBooks? Bug?, posted by Stefan Ritt on Thu Dec 22 15:14:39 2005
|
[quote="Mike"]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. |
Re: Maximum number of LogBooks? Bug?, posted by Mike on Thu Dec 22 15:39:23 2005
|
[quote="Stefan Ritt"]
You're really pushing to the limit ;)
|
|
Re: Max Logbooks for Email notify, posted by Oliver Kleinau on Fri Apr 10 08:37:19 2015
|
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, |
|
Re: Max Logbooks for Email notify, posted by Oliver Kleinau on Fri Apr 10 09:59:42 2015
|
It was str variable in function process_http_request in elogd.c.
This should have the size of received buffer.
PROBLEM SOLVED!!! |