Hello Harry,

the elog server (elogd) is a standalone application written in C and contains a full webserver and logfile management system.
There are no other dependencies to apache or python.

You can use a webserver like apache or nginx in combination with elog to act as a proxy,
e.g. to handle the encryption part of the communication between your web browser and the elogd, but you don't need to.

Regarding the first part of your message:
The elog server worked normally; entries (including the text body) got saved correctly until the last update? 
The only thing in your list of updates, I can think of making this problem could be the update of ckeditor as it is the text editor used by elog.
The other packages should not be related to elog... but I am not a package maintainer.
I compiled elog from source and it brings the necessary files with it.

Best wishes,
Sebastian

Hello,

I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."

I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.

I have requested an undeletion of the article. The article was deleted  "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.

I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.

If there iy an paper on the elog, maybe it could be cited for more creditability.

Just my 2 cents:

There is a hardcoded limit how many entries the Option list can have. Without looking into the source, I assume the limit also exists for MOptions.
If you want more, you have to recompile elog with the changed limit.

We have used the normal Options attribute and a "Execute new"-script to alter the elog config for the Options list: to sort the list (5 last used entries on top, the rest alphabetical) and remove very old entries, which are not needed any more.
Remark: if you change the elog.cfg, you have to tell elog to reload the cfg. e.g. using "killall -HUP elogd".

Alternatively, you can add javascript code via a html file and the attributes "Top text" or "Bottom text" to manipulate the input fields on the client side.

Both ways are a little bit hacky, but they work.
Best wishes,
Sebastian

> Thanks for you help. This is almost it. 
> 
> The problem is that the items are options and not freely closable numbers. In the end, with your solution, it will show you all of the previously put IDs which will be 1000s of entries for us. I think I will just put a convention that we have to write the numbers spread with a comma in a string 
> field.
> 
> Thanks.
> 
> Best,
> 
> Nick 
> 
> 
> > I have replied to this entry, because, for some reason I don't understand, if I reply to your latest entry, I am
> > automatically logged out.  I tried this multiple times, and also on many other entries and had no issues other than
> > entry 69787 - any reason for this, Stefan?
> > 
> > Anyway, what about MOptions? That appears to do what your example, and needs two lines in elog.cfg file:
> > 
> > Moptions WaferID = 1001, 1002, 1003, 1004, 1005
> > Extendable Options = WaferID
> > 
> > I've done a couple of quick tests on a test logbook I keep for such experimentation, and it appears to do all 
> > you have asked of it.  I added a new option 1006.  However, I found that one has to add that new one on its own, 
> > let the entry become proper, and then edit the entry to add the other, existing, values.   If you tick entries and 
> > also add a new one, then your new entry is all those listed on their own, that is you would get and new entry
> > in the config file such as "1002 | 1004 | 1006", rather than just 1006
> > 
> > This is probably an result of an unexpected use of Moptions and extendable options, rather than a bug per se.
> > 
> > > Hey, 
> > > 
> > > thanks for your answer. I completely get your point. However, I think my question as not precise enough.
> > > 
> > > I would like to have a numeric input, but many at the same time. When I make a new post, I would like to have an attribute 'wafer_IDs' that specifies the list of wafers this process has been performed with. So for a single post I would like to have a list like this:
> > > 
> > > wafer_IDs = numeric value, numeric value, numeric value, extendable
> > > 
> > > Note: I am not referring here to the option. The numeric values are freely chooses numbers, the only this that varies from post to post is the number of numeric values put.
> > > 
> > > Let me make an example (If the attribute were a string this would be the equivalent):
> > > 
> > > 1st post: A process that was run with 3 wafers (ID: 1000, ID: 1001 and ID: 1002):
> > > wafer IDs = 1000, 1001, 1002
> > > 
> > > 2nd post: A process that is run with 2 wafers (ID: 1000 and ID: 1002):
> > > wafer IDs = 1000, 1002
> > > 
> > > The string solves the issue, but is not as nice as having directly a list of integers.
> > > 
> > > Thanks for your help!
> > > 
> > > Best,
> > > 
> > > Nick

I've been asked to export one of our logbooks to xls or csv. Doable?

Thanks,

Scott

Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
as soon as it is accessed.

Under 2.5.7, a login page will come up, and the logbook will work, but only
if a valid username/password is given.  If an invalid login is given, then
elogd crashes.  We have a cron job that periodically restarts elogd if it is
has crashed.

Steve

[global]
logbook tabs = 0
port = 8080
Protect Selection page = 1
Password file = user.info
Admin user = saw
 

> > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
> 
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
> 
> - Stefan

That was fast!  I put the elogd.c from the cvs on top of 2.5.8 and now I can run
the server with Protect Selection page=1 again.

Logins work OK if the username/password is valid.  However, if I try to login
with invalid authentication, the server crashes.  If I turn off the protect
selection page, then invalid authentication does not crash elogd.

Thanks, Steve

> > Logins work OK if the username/password is valid.  However, if I try to login
> > with invalid authentication, the server crashes.  If I turn off the protect
> > selection page, then invalid authentication does not crash elogd.
> 
> Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
> 
> I fixed that as well and committed the changes.

That seems to do the trick!  Thanks, Steve