I've managed to get it working and the problem wasn't what I thought it was.  It turns out that ImageMagick v7 doesn't have a "convert.exe" program in the windows version due to some conflict with a disk conversion utility.  The "convert.exe" has been replaced with a "magick.exe" and so I made a CONVERT.BAT script within the elog folder with content "magick %*".  This workaround appears to have solved the problem.

Version: ImageMagick 7.1.1-35 Q16-HDRI x64 d775d2a:20240714 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Channel-masks(64-bit) Cipher DPC HDRI Modules OpenCL OpenMP(2.0)
Delegates (built-in): bzlib cairo flif freetype gslib heic jng jp2 jpeg jxl lcms lqr lzma openexr pangocairo png ps raqm raw rsvg tiff webp xml zip zlib
Compiler: Visual Studio 2022 (194033811)

Just to add some points for others who may find this of use in future.

The hard coded number of entries options or Moptions can have is 100.  You can edit the code and recompile, but that would
not gain you many more before other problems concerning memory come in.

Options allow you to only select one from the list; Moptions allow multiple selections from the list.

As mentioned by Sebastian (previous poster) and  in my suggestion. I imagined that by Wafer 1060 (say), no new work would be 
being done on wafers 1001, ... 1010, so you could edit the config file and remove those (M)options.  It does not remove these 
wafer IDs from past records, simply that they can no longer be selected for new work to be recorded.    In that way the 
Moptions list remains short but allows for hundreds or thousands of WaferIDs,  ON THE ASSUMPTION that say only 50 (and certainly 
less than 100) are being worked on at any one time.

The numbers I chose here were random, it's more to highlight the principle rather than a prescription.

David.

> 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

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

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 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

Hey eloggers,

does anyone have an answer to this question?

Thanks for the help.

Best,


Nick


> 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

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 think what you want already exists, for example, when I reply to this message, there is this "Category" selection box with predefined answers 
"Info", "Bug report", etc. For your case, replace "Category" with "Wafer type ID", replace "Info" with "1", "Bug report" with "2", etc. You numeric 
values will be strings containing numbers "1", "2", etc. That works for you? K.O.

Hi John,

thanks for the info =). Do you known whether there is an example of how to use the list-boxes attributes?

Best,

Nick

Hey eloggers,

I am setting up an ELOG to log the cleanroom fabrication in our startup (Luxtelligence SA). The fabrication is structured in different process steps that are performed by several wafers at the same time (each wafer as an ID).

I am looking for an possibility to put a list of several integers as one of the attributes.

Here an example:

Does something like this exsist?

Thanks in advance for your help.

You can export logbook entries into a CSV file, then load it into Excel.

Stefan

Thanks a lot Stefan,

I asked if it is possible, in general, to create a connection and automatically fill in the tables of a report, or export the data into excell tables to then be connected to the report, having in our case about 24 process tables to be filled in with data or validation, for each report. If the compilation is not automatic, after having compiled the elog in each phase of the processing, the manifacturing report will then have to be compiled manually.

We use elog, having already used it in MEG We must then compulsorily also make manufacturing  and test reports. The expected space-type documentation format for these documents is in word.

Below is a small example of a test table, with just a few steps.

Thanks again

Manuela

You can just copy-and-paste an elog entry into Word. I tested it here wiht a simple table:

Did a copy-and-paste to Word, and got the thing below.

Best,
Stefan

HI,

Is there a way to export the ELOG entries to a file like Microsoft Word?
For ECSS-type documents for space missions, I have to report the data that we enter in the ELOG in a Manufacturing Report, foreseen for ECSS, in word format. It's possible to do it?
The data has to go into tables, inserted in the world file, called "as run procedure".
Is it possible to connect the elog to a report template so that it automatically generates the manufacturing report? Or link the tables placed in it so that they are automatically filled in?

Thank you so much
Manuela

Hi Xuan,

Sorry for the delayed response.  I just got back from my travel.  I tried your solution, but in my system I don't see elogd.h in the src folder.  Here is what I see and also I don't see any "make" binary in the folders.  I'm running the Windows version.

Thanks.
Illam

Hi Illam,

You can find it in src/elogd.h, #define TEXT_SIZE  250000, the original value 250000, you can change it to a larger one like #define TEXT_SIZE    1000000. Then recompile it again, just need typing "make". Elog Version is 3.1.3 in my site. HTH.

Cheers,

Xuan Wu

Hi,  any help will be appreciated on this.  I have not still figured this out.

Thanks.
Illam

Hi Laurent

It is possible to use the attached but the elogd will not start as a service anymore - is there a fix to that aswell?

Kind Regards Finn

Hi,

It's possible to build elogd under windows with cygwin, but not sure that is the best as it requires a lot of dependencies that should be included to dist package to be runnable everywhere.

After

• installation of dependencies (gcc-g++, make, libssl1.1, libssl-devel, opendlap-devel, libopenldap2, libkrb5-devel, libkrb5_3) using CygWin setup program,
• instalkation of git tool and clone the git repo (git clone https://bitbucket.org/ritt/elog --recursive),
• modification of Makefile to build with Kerberos/ldap/ssl support,

from cygwin bash under Windows 11, you can build elog :

/cygdrive/d/Devel/elog $ make
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -o elog src/elog.cxx mxml.o crypt.o strlcpy.o -lssl -lkrb5 -lldap -llber
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -w -c -o auth.o src/auth.cxx
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -o elogd src/elogd.cxx auth.o mxml.o crypt.o strlcpy.o -lssl -lkrb5 -lldap -llber
src/elogd.cxx:217:6: warning: ‘_timezone’ redeclared without dllimport attribute: previous dllimport ignored [-Wattributes]
  217 | long _timezone;
      |      ^~~~~~~~~
src/elogd.cxx: In function ‘int el_submit(LOGBOOK*, int, BOOL, const char*, char (*)[1500], char (*)[1500], int, const char*, const char*, const char*, const char*, const char (*)[256], BOOL, const char*, const char*)’:
src/elogd.cxx:4963:47: warning: ‘%s’ directive writing up to 149999 bytes into a region of size between 100103 and 250102 [-Wformat-overflow=]
 4963 |       sprintf(message + strlen(message), "%s: %s\n", attr_name[i], attrib[i]);
      |                                               ^~
src/elogd.cxx:4963:14: note: ‘sprintf’ output between 4 and 300002 bytes into a destination of size 250104
 4963 |       sprintf(message + strlen(message), "%s: %s\n", attr_name[i], attrib[i]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx: In function ‘void show_edit_form(LOGBOOK*, int, BOOL, BOOL, BOOL, BOOL, BOOL, BOOL)’:
src/elogd.cxx:9655:28: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3993 [-Wformat-overflow=]
 9655 |       sprintf(str, "Preset %s", attr_list[index]);
      |                            ^~
src/elogd.cxx:9655:14: note: ‘sprintf’ output between 8 and 150007 bytes into a destination of size 4000
 9655 |       sprintf(str, "Preset %s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9676:43: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3978 [-Wformat-overflow=]
 9676 |       sprintf(str, "Preset on first reply %s", attr_list[index]);
      |                                           ^~
src/elogd.cxx:9676:14: note: ‘sprintf’ output between 23 and 150022 bytes into a destination of size 4000
 9676 |       sprintf(str, "Preset on first reply %s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9697:37: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3984 [-Wformat-overflow=]
 9697 |       sprintf(str, "Preset on reply %s", attr_list[index]);
      |                                     ^~
src/elogd.cxx:9697:14: note: ‘sprintf’ output between 17 and 150016 bytes into a destination of size 4000
 9697 |       sprintf(str, "Preset on reply %s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9697:37: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3984 [-Wformat-overflow=]
 9697 |       sprintf(str, "Preset on reply %s", attr_list[index]);
      |                                     ^~
src/elogd.cxx:9697:14: note: ‘sprintf’ output between 17 and 150016 bytes into a destination of size 4000
 9697 |       sprintf(str, "Preset on reply %s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9697:37: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3984 [-Wformat-overflow=]
 9697 |       sprintf(str, "Preset on reply %s", attr_list[index]);
      |                                     ^~
src/elogd.cxx:9697:14: note: ‘sprintf’ output between 17 and 150016 bytes into a destination of size 4000
 9697 |       sprintf(str, "Preset on reply %s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9697:37: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3984 [-Wformat-overflow=]
 9697 |       sprintf(str, "Preset on reply %s", attr_list[index]);
      |                                     ^~
src/elogd.cxx:9697:14: note: ‘sprintf’ output between 17 and 150016 bytes into a destination of size 4000
 9697 |       sprintf(str, "Preset on reply %s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9717:36: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3985 [-Wformat-overflow=]
 9717 |       sprintf(str, "Preset on edit %s", attr_list[index]);
      |                                    ^~
src/elogd.cxx:9717:14: note: ‘sprintf’ output between 16 and 150015 bytes into a destination of size 4000
 9717 |       sprintf(str, "Preset on edit %s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9737:41: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3980 [-Wformat-overflow=]
 9737 |       sprintf(str, "Preset on duplicate %s", attr_list[index]);
      |                                         ^~
src/elogd.cxx:9737:14: note: ‘sprintf’ output between 21 and 150020 bytes into a destination of size 4000
 9737 |       sprintf(str, "Preset on duplicate %s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9758:22: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3999 [-Wformat-overflow=]
 9758 |       sprintf(str, "p%s", attr_list[index]);
      |                      ^~
src/elogd.cxx:9758:14: note: ‘sprintf’ output between 2 and 150001 bytes into a destination of size 4000
 9758 |       sprintf(str, "p%s", attr_list[index]);
      |       ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9776:31: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3993 [-Wformat-overflow=]
 9776 |          sprintf(str, "Preset %s", attr_list[index]);
      |                               ^~
src/elogd.cxx:9776:17: note: ‘sprintf’ output between 8 and 150007 bytes into a destination of size 4000
 9776 |          sprintf(str, "Preset %s", attr_list[index]);
      |          ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9797:40: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3984 [-Wformat-overflow=]
 9797 |          sprintf(str, "Preset on reply %s", attr_list[index]);
      |                                        ^~
src/elogd.cxx:9797:17: note: ‘sprintf’ output between 17 and 150016 bytes into a destination of size 4000
 9797 |          sprintf(str, "Preset on reply %s", attr_list[index]);
      |          ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:9817:44: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 3980 [-Wformat-overflow=]
 9817 |          sprintf(str, "Preset on duplicate %s", attr_list[index]);
      |                                            ^~
src/elogd.cxx:9817:17: note: ‘sprintf’ output between 21 and 150020 bytes into a destination of size 4000
 9817 |          sprintf(str, "Preset on duplicate %s", attr_list[index]);
      |          ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx: In function ‘void show_elog_list(LOGBOOK*, int, int, int, BOOL, char*)’:
src/elogd.cxx:20459:43: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 1587 [-Wformat-overflow=]
20459 |                sprintf(str, "Icon comment %s", attrib[i]);
      |                                           ^~
src/elogd.cxx:20459:23: note: ‘sprintf’ output between 14 and 150013 bytes into a destination of size 1600
20459 |                sprintf(str, "Icon comment %s", attrib[i]);
      |                ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:20506:33: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 1600 [-Wformat-overflow=]
20506 |                   sprintf(str, "%s_%d", attr_list[i], j);
      |                                 ^~
src/elogd.cxx:20506:32: note: directive argument in the range [0, 99]
20506 |                   sprintf(str, "%s_%d", attr_list[i], j);
      |                                ^~~~~~~
src/elogd.cxx:20506:26: note: ‘sprintf’ output between 3 and 150003 bytes into a destination of size 1600
20506 |                   sprintf(str, "%s_%d", attr_list[i], j);
      |                   ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:20470:33: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 1600 [-Wformat-overflow=]
20470 |                   sprintf(str, "%s_%d", attr_list[i], j);
      |                                 ^~
src/elogd.cxx:20470:32: note: directive argument in the range [0, 99]
20470 |                   sprintf(str, "%s_%d", attr_list[i], j);
      |                                ^~~~~~~
src/elogd.cxx:20470:26: note: ‘sprintf’ output between 3 and 150003 bytes into a destination of size 1600
20470 |                   sprintf(str, "%s_%d", attr_list[i], j);
      |                   ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:21052:30: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 1600 [-Wformat-overflow=]
21052 |                sprintf(str, "%s_%d", attr_list[i], j);
      |                              ^~
src/elogd.cxx:21052:29: note: directive argument in the range [0, 99]
21052 |                sprintf(str, "%s_%d", attr_list[i], j);
      |                             ^~~~~~~
src/elogd.cxx:21052:23: note: ‘sprintf’ output between 3 and 150003 bytes into a destination of size 1600
21052 |                sprintf(str, "%s_%d", attr_list[i], j);
      |                ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:21538:45: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 1588 [-Wformat-overflow=]
21538 |                   sprintf(str, "Time format %s", attr_list[i]);
      |                                             ^~
src/elogd.cxx:21538:26: note: ‘sprintf’ output between 13 and 150012 bytes into a destination of size 1600
21538 |                   sprintf(str, "Time format %s", attr_list[i]);
      |                   ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:21523:45: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 1588 [-Wformat-overflow=]
21523 |                   sprintf(str, "Date format %s", attr_list[i]);
      |                                             ^~
src/elogd.cxx:21523:26: note: ‘sprintf’ output between 13 and 150012 bytes into a destination of size 1600
21523 |                   sprintf(str, "Date format %s", attr_list[i]);
      |                   ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx: In function ‘void submit_elog(LOGBOOK*)’:
src/elogd.cxx:23293:38: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 2034 [-Wformat-overflow=]
23293 |          sprintf(str, "Subst on edit %s", attr_list[index]);
      |                                      ^~
src/elogd.cxx:23293:17: note: ‘sprintf’ output between 15 and 150014 bytes into a destination of size 2048
23293 |          sprintf(str, "Subst on edit %s", attr_list[index]);
      |          ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/elogd.cxx:23323:39: warning: ‘%s’ directive writing up to 149999 bytes into a region of size 2033 [-Wformat-overflow=]
23323 |          sprintf(str, "Subst on reply %s", attr_list[index]);
      |                                       ^~
src/elogd.cxx:23323:17: note: ‘sprintf’ output between 16 and 150015 bytes into a destination of size 2048
23323 |          sprintf(str, "Subst on reply %s", attr_list[index]);
      |          ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -DHAVE_SSL -DHAVE_KRB5 -DHAVE_LDAP -o elconv src/elconv.cxx -lssl -lkrb5 -lldap -llber

Copy to new dir :

• the 3 binaries(elogd.exe, elog.exe & elconv.exe)
• logbooks, scripts, ssl and themes folders from git clone.
• elogd.cfg.example as elogd.cfg.

/cygdrive/d/Devel/elog/elog-win64 $ ldd elogd.exe
        ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ff9796b0000)
        KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ff978050000)
        KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ff976af0000)
        cygwin1.dll => /usr/bin/cygwin1.dll (0x7ff925010000)
        cygkrb5-3.dll => /usr/bin/cygkrb5-3.dll (0x3fe4b0000)
        cygldap-2.dll => /usr/bin/cygldap-2.dll (0x3fdf70000)
        cyglber-2.dll => /usr/bin/cyglber-2.dll (0x3fe030000)
        cygssl-1.1.dll => /usr/bin/cygssl-1.1.dll (0x3ff4d0000)
        cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3ff2f0000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3ffc30000)
        cygk5crypto-3.dll => /usr/bin/cygk5crypto-3.dll (0x3fe600000)
        cygkrb5support-0.dll => /usr/bin/cygkrb5support-0.dll (0x3fe490000)
        cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3ffa10000)
        cygcom_err-2.dll => /usr/bin/cygcom_err-2.dll (0x3fe9b0000)
        cygcrypto-1.1.dll => /usr/bin/cygcrypto-1.1.dll (0x3ffce0000)
        cygsasl2-3.dll => /usr/bin/cygsasl2-3.dll (0x3fdee0000)
        cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3ffa30000)
        cygz.dll => /usr/bin/cygz.dll (0x3ff280000)

/cygdrive/d/Devel/elog/elog-win64 $ ls
elconv.exe  elog.exe  elogd.cfg  elogd.exe  logbooks  scripts  ssl  themes
 

/cygdrive/d/Devel/elog/elog-win64 $ ./elogd.exe
elogd 3.1.5 built Apr 12 2023, 00:01:15 revision 33884104
CKeditor detected
ImageMagick NOT detected. Image scaling will not work.
Indexing logbooks ... done
Server listening on port 8080 ...

With that, elogd starts and the site is usable.

NB: after installing imageMagick, elogd starts with activation of image manipulation features.

/cygdrive/d/Devel/elog/elog-win64 $ ./elogd.exe
elogd 3.1.5 built Apr 12 2023, 00:01:15 revision 33884104
CKeditor detected
ImageMagick detected
Indexing logbooks ... done
Server listening on port 8080 ...

For who as interested, I enclosed 2 zips, with (elog-win64_wDLL.zip) or without (elog-win64.zip) Cygwin DLL (licence: https://cygwin.com/COPYING). The build uses the current git version.

Regards,

Laurent

Hi Stefan

Is there anything the community or forum can help you with or supply for creating a windows version?

Kind Regards Finn

Hi,

I'm getting the TEXTSIZE TOO BIG message every time I have more text in my entry.  I understand there is a way to increase the TEXTSIZE and re-compile.  Where can I find the TEXTSIZE parameter that I can increase and also how do I re-compile.

Appreciate your help.

Thanks.
Illam

Thanks Stefan for your help.  It works but the only issue is, the screenshots that were included in the body of the entries are not usable.  Not sure if there is any workarounds for that.

...Illam

Find -> Export to...

Hi,

Is there a way to export the ELOG entries into a file like an Excel sheet or something.  I see import but not export.

Appreciate your help.

Thanks.

Illam

Looking forward to the windows installer. 

Thanks a lot and keep up the good work!

cheers,

toto

A new version 3.1.5 of elog has been released with all accumulated fixes over the past actually few years. I made a tar file, a RPM, but I could not compile yet a windows version.

https://elog.psi.ch/elog/download.html

Best,
Stefan

FYI

They seem to have accepted the bug report:
https://bugs.webkit.org/show_bug.cgi?id=249923

It shound't be a "bug report", sorry. I have changed the category to "Info".

It seems to be really a bug in the WebKit core. I have created a bug report there. For reference: https://bugs.webkit.org/show_bug.cgi?id=249923

I am going to try to patch the ELOG code to handle the content of the textarea in the "plain" format.... it doesn't seem possible though. 

Dear Stefan, 

There is a problem with editing an Elog page in "plain" format with the following "User Agent" :

"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.1 Safari/605.1.15"

It duplicates the newline symbols such that "1<CRLF>2" becomes "1<CRLF><CRLF>2". If edited again - "1<CRLF><CRLF><CRLF><CRLF>2".

I blame the new version of the Apple WebKit. 

It works fine with Chrome (user agent: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36"). But fails with Safari. 
 

Could you please have a look? 

Thank you in advance, 

Andrey Pashnin

AMS collaboration

Herrenhemden in St. Gallen
Titel: Finden Sie das beste Herrenhemd für den Büroalltag bei brandmarkt in St. Gallen
Wenn es darum geht, sich für die Arbeit zu kleiden, ist es am besten, eine Vielzahl von zuverlässigen Büromodellen zur Verfügung zu haben. Von allen Kleidungsstücken, die zur Auswahl stehen, sind Herrenhemden für das Büro das attraktivste Kleidungsstück für Berufstätige.
Berufstätige Männer wollen immer gut in ihre Bürokleidung investieren. Die günstigste Herren-Business-Kleidung zu kaufen, ist sehr schwierig.
Möchten Sie die originellen und stilvollen Herrenhemden für die Bürobekleidung in St. Gallen kaufen?
 Bei 9000 in St. Gallen hat Brandmarkt eine Vielzahl von Herrenhemden für die Bürobekleidung. Langärmelige Herrenhemden für den Arbeitsplatz, kurzärmelige Herrenhemden in aktuellen Modetrends sind zu günstigen Preisen erhältlich.
Berufstätige Männer wollen immer stilvoll und bequem aussehen, indem sie leichte Kleidung wie T-Shirts oder kurzärmelige Herren-Arbeitshemden tragen. Sie können ein kurzärmeliges T-Shirt mit einer Jeans oder einer Hose tragen und sind damit bei einem Meeting präsentabel.
Kleiden Sie sich im Sommer mit der bequemsten und stilvollsten Herren-Bürokleidung für das Büro. Herrenhemden für das Büro in hellen Farben sind die perfekte Kleidung für den Sommer. Herrenhemden für den Sommerlook gibt es bei Brandmarkt zu günstigen Preisen.  
Geschäftsleute wollen immer Klasse in ihrem Auftreten mit der aktuellsten Herren-Business-Mode. Meistens werden für die Bürokleidung der Herren Anzüge getragen. Passende Hemden zum Anzug sorgen für Abwechslung im Erscheinungsbild.
 
Bei Brandmarkt in St. Gallen können Sie Marken-Herrenhemden in verschiedenen Farben, Mustern und Designs zu günstigen Preisen kaufen und mit Ihrem Büroanzug kombinieren.
Viele Büros planen verschiedene Tage wie den "Causal Wear Friday" für ihre Mitarbeiter. Es ist Zeit, sich in Freizeitkleidung zu kleiden. Sie können ein Hemd oder T-Shirt mit Jeans tragen. Passende Herren-Accessoires wie Gürtel und Krawatten können Ihren Look ebenfalls aufwerten.
Holen Sie sich die exklusiven Herrenhemden bei Brandmarkt zu den günstigsten Preisen. Sie können die Top-Marken wie Ice Peak bei Brandmarkt, Jako bei Brandmarkt, Tom Taylor bei Brandmarkt, Puma bei Brandmarkt, Nike bei Brandmarkt und viele andere zu einem sehr günstigen Preis bei Brandmarkt in St. Gallen kaufen.
Nicht nur die Hemdenkollektion, sondern auch Herrenschuhe und Herrenaccessoires können Sie bei Brandmarkt in St. Gallen zu sehr günstigen Preisen kaufen.
Unternehmen veranstalten für ihre Mitarbeiter meist Sportveranstaltungen. Es ist an der Zeit, dass die Angestellten ein anderes Outfit als den Dresscode des Büros tragen. Herren-Sportbekleidung Hemden sind die beste Option für Sportveranstaltungen.
Jetzt können Sie sich für das Büro anders stylen als mit einem Anzug, einem Hemd oder einem T-Shirt. Tragen Sie ein schmal geschnittenes, langärmeliges Herren-Sporthemd mit Jogginghose und machen Sie bei Sportveranstaltungen im Büro eine gute Figur.
Für informelle Tage wünscht sich jeder Mitarbeiter einen besonderen Look. Wenn Sie auf der Suche nach Sportbekleidung, Herrenhemden in Slim Fit, Regular Fit, Herren Outdoor Hemden sind. Holen Sie sich diese im Brandmarkt in St. Gallen.
Dort gibt es exklusive Marken von Herren Sporthemden in St. Gallen zu sehr günstigen Preisen. Zu günstigen Preisen, nicht nur das Herren Sporthemd sondern auch die Marken Herren Sportschuhe zu Ihrem Outfit.
 
Wo kann man in St. Gallen günstige Herren-Bürohemden zu günstigen Preisen kaufen?
Unser Modehaus Brandmarkt an der 9000 in St. Gallen hat originelle und hochwertige Herrenhemden in St. Gallen, darunter eine große Auswahl an langärmeligen Herren-Arbeitshemden, kurzärmeligen Herren-Arbeitshemden, Slim-Fit-Hemden und Sporthemden, alles zu sehr günstigen Preisen.
 
Worauf warten Sie noch? Kommen Sie zu Brandmarkt in St. Gallen und kaufen Sie die beste Qualität an Herrenhemden in St. Gallen für Ihre Bürokleidung zu Einzelhandelspreisen. Sparen Sie Ihr Geld und sehen Sie professionell aus.

There is only an open source version.

Good day all ,

does Elog has a paid version that is not open soureced 

regards

William Vasio 

Good day all ,

does Elog has a paid version that is not open soureced 

regards

William Vasio 

I have a PDF file created by root which ImageMagic cannot convert to a .png file. If I do

convert img.pdf img.png

it works on my mac, but under RH7.4 the program goes into an infinite loop eating 100% CPU.

I attached the img.pdf, but compressed it to img.pdf.gz, otherwise I cannot post here.

Can anyone figure out why ImageMagick won't convert that file?

Ubuntu LTS 20.04 and others have elog PDF preview disabled by default. To enable,
please follow these steps, see https://daq00.triumf.ca/DaqWiki/index.php/Ubuntu#Enable_elog_PDF_preview

Enable elog PDF preview
see https://stackoverflow.com/questions/52998331/imagemagick-security-policy-pdf-blocking-conversion

xemacs -nw /etc/ImageMagick-6/policy.xml
remove this section at the end:
<!-- disable ghostscript format types -->
<policy domain="coder" rights="none" pattern="PS" />
<policy domain="coder" rights="none" pattern="PS2" />
<policy domain="coder" rights="none" pattern="PS3" />
<policy domain="coder" rights="none" pattern="EPS" />
<policy domain="coder" rights="none" pattern="PDF" />
<policy domain="coder" rights="none" pattern="XPS" />

K.O.

Recently I have had problems with ELOG not accepting the certificates (in this case from https://letsencrypt.org/) probably due to the old version of the SSL library of the binary distribution for Windows.
I have tried to follow the instructions to set up ELOG to work with Apache but they are probably old.
I have a simple solution for the Apache installation of XAMPP, the example is for two separate logbooks using each its own ELOG service on the same server:

1. I have set up the two ELOG to run as http://my.server.example.com:8080/ and as http://my.server.example.com:8081/

2. in c:\xampp\apache\conf\httpd.conf I have enabled the following (I am not sure if all the modules are really needed but this works for me):

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule headers_module modules/mod_headers.so
LoadModule proxy_html_module modules/mod_proxy_html.so
LoadModule xml2enc_module modules/mod_xml2enc.so

3. still in c:\xampp\apache\conf\httpd.conf, at the very end of the file I added the following:

ProxyRequests off

Redirect permanent /app1 https://my.server.example.com/app1/
ProxyPass /app1/ http://my.server.example.com:8080/
ProxyHTMLURLMap http://my.server.example.com:8080 /app1

Redirect permanent /app2 https://my.server.example.com/app2/
ProxyPass /app2/ http://my.server.example.com:8081/
ProxyHTMLURLMap http://my.server.example.com:8081 /app2

This way I can now connect to the two ELOG using https://my.server.example.com/app1/ and https://my.server.example.com/app2/ without troubles and no additional setting to either the configuration files of ELOG nor any need for virtual hosts, ...

I hope this might be of use.

Excellent, exactly what I was looking for, many thanks!

As you can see, on this forum the author for replies is correct. This is done via the config option:

Preset on reply Author = $long_name

what is the default value for "Author" when replying to a log entry ?  I now see that for each reply to a log entry, the value of "Author" is set to the value of the author of the original entry - this makes it very hard to see which user has replied to a particular log entry, especially when users start replying to replies etc.

This is with elog 3.1.4-3 on CentOS 7

There is a python API to access ELOG via HTTP: https://github.com/paulscherrerinstitute/py_elog

Hi Illam

You actually have to change the source code of elog and then recompile. Download the code from https://bitbucket.org/ritt/elog/src/master/, change the value of the variable TEXT_SIZE in the file src/elogd.h

Default ist #define TEXT_SIZE 250000

Hi,

I'm trying to increase the entry text constraint but not sure how to do this.  Couldn't find it in the documentation or may be I missed it.  Appreciate your help.

Thanks.
Illam

An ELOG vulnerability has been reported, thanks to Asif Akbar of Trend Micro Security Researchworking with Trend Micro's Zero Day Initiative:

https://www.zerodayinitiative.com/advisories/ZDI-20-252/

The issue has been fixed in the current release 3.1.4-033e292 and in the RPM http://elog.psi.ch/elog/download/RPMS/elog-latest.x86_64.rpm

Best,
Stefan

Wow thanks again Stefan for your kind and prompt responses!!

John

In JS, you have access to the browser URL via window.location. So you can write conditional code depending on the actual elog command.

Stefan

I think I know what the answer(s) will be already.. that I will need to address this in JS. I don't want each screen to run/show the same code, other than the ones I want to.  AND I do not want to have to create a custom form for each 'menu option' to achieve this (if possible).

Thanx,

John

Attached the shell scripts using awk and sed how I have migrated two separated logbooks into one single and how I re-adjusted certain attributes.

Dear Andreas,

The same problem by using the shiftchecklist and the cfg in Stefan's mail. It report the no password file, even the absolute path wroten in cfg file.  The author field also failed to be read, it is shown as "?" in the page . Did there miss some other files?

Any suggestion is welcome. Thank you very much.

Qisheng

I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make the same mistake,

The message height option only works if you select either "ELCode" or "plain" for encoding (this can also be made as default in the config file). For the HTML editor, the size is set internally and I don't have any influenc on it.

Stefan

I tried with Message Height = 100 inside the conifguration of my logbook, but nothing changed as you can see in the first picture...

What I'm looking for is a way, if possible, to start by default with a wider message box, someting like fig2. For our purpose, using wide tables, it would be very useful to have a wider message box in order to have a full look to the message content, and also having it by default without modifying it by hand with the mouse every time we submit something to elog.

Beppe 
 

Have you tried

Message height = ...

unit is number of text lines.

Stefan

Hi,

I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px)  is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?

Thank you 

Beppe

Most mail delivery systems have a maximum size for attachments. In the past, if an elog attachment was larger than this size, the email server refused to accept this email and no notification is sent. Now one can specify the maximum allowed email attachment size with

Max email attachment size = <n>

where <n> is the number of bytes. If an email attachment is larger than <n>, the attachment is not sent with the email notification, but rather replaced by a link to the elog server for that attachment. By clicking on the link in the email notification, a browser will then open and download the large attachment. For each each elog installation, the admin has to figure out what the maximum attachment size of their SMTP server is, and then put this number into the elogd.cfg setting  above. For most installations, the default of 10 MB will just work fine.

Stefan

Hi Daniel,

you're the first one reporting about this virus. We have different virus checkers here at our lab and none of them triggered. So I guess it is a false alarm.

Best,

Stefan

Hello.

Today I wanted to download latest elog version, and got information from Eset Endpoint Antyvirus, that downloaded file has trojan horse "Generic.GQWFFXB".

It this false positive alarm?

Daniel

It's very simple, no need for the find command. E.g.: Start page = ?Author=luedeke&Category=Question&mode=summary

in this forum would do https://midas.psi.ch/elogs/Forum/?Author=luedeke&Category=Question&mode=summary

The mxml package has been converted into a submodule in the git repository. At http://midas.psi.ch/elog/download.html you see that you need a "--recursive" flag to clone it. If you have already checked out the sources, you need a

git submodule update --init --recursive

/Stefan

Hello,

I wonder if it's normal that in the sources files, new created mxml directory is empty.

In commit # a6e5962 4 files are deleted but not moved:

- src/mxml.c
- src/mxml.h
- src/strlcpy.c
- src/strlcpy.h 

Thank you

You need the netdb.h header file to compile elog. I see that you compile under Windows. You have to make sure that your compiler installation comes with all header files. The netdb.h file is usually in /usr/include under Unix.

I downloaded the source code from the git repository which contained the new fix that was made for the missing username-crash error. I tried compiling the elogd.c file using a GCC compiler and it gave an error about missing header files. It first gave an error about netdb.h file and when I commented that header file call, it gave further errors for other header files. I do not really understand why it gives an error about that.  

In version 3.1.2-416db9f I implemented a "Restore" button, which should fix the second drawback. If you press it, you should be able to go back to where you started when editing an entry.

Dear all,

there seems to be still lots of confusion with the new "draft modus" introduced in elog 3.1.2. Here is how it works:

If you edit an old or new entry, your changes are written to the elog server every few seconds. The entry in the elog database is marked as "draft". The idea behind that is that if your browser crashes or you navigate away from the elog page without saving your entry, the "draft" entry is sill in the elog database and can be recovered later. This is typically useful on some shift logbooks, where people keep the entry open for many hours and add things every few minutes. If they have a crash, they would loose a few hours of information.

The draft modus now has a few drawbacks:

• If you have some draft entries in your elog database, you don't see them until you hit "New" the next time. Then the system offers you to continue the open draft entries.
• Once you change an existing entry, you cannot go back to the version of that entry before you started to make modifications. The only option is to keep the current version or delete the whole entry. The old version of your entry in the database is overwritten every few seconds with the current contents of your edit text field.

To fix the first problem, I introduced a new flag "List drafts = 0|1". If this flag is 1, the draft entries are shown in the list view. The default value for this flag is 1, so normally you should see the draft entries in the database. You should refrain from editing these entries if you know that currently somebody else is working on them, otherwise you will overwrite each other's modifications. The modification is in the current git version of elog which is 3.1.2-6ec506b.

The scond drawback is harder to address. In order to go back to previous version, you would need a full version system (ala git), which is far beyond the scope of elog. I'm working on a partial fix by storing the contents on an entry inside the browser when you start editing an entry. You can then "cancel" your modifications by pasting back the original version from your browser. This works of course only if your browser does not crash or you do not navigate away from the elog page, in which case the original version will be lost.

If anybody has a strong opinion about these changes, please post them here.

Stefan

A new version 3.1.2 of elog has been released today and can be retrieved through the normal download section. Since it fixes some vulnerabilities, it is recommended to update to this version.

Stefan

What is the string length limit in url tag and how to increase it?

For example,

[url=http://example.com?<text_string>]click here[/url]

When I provide very long <text_string>, it was truncated and showed partial link only.

You might try to specify an absolute path to the password file in the configuration.

I would need a complete minimal configuration that creates that problem.

Hello Stefan,

I created a custom form with the example you provided. When I enter the Data and Submit the Form I get the error message "Datei passwordfile.xml kann nicht geöffnet werden: No such file or directory".  Posting stuff works in all other logbooks.  Only in the "logbook with the form" there seems to be an error. (or misconfiguration on my side)

sections from my conf. File:

I tried copying the password file to the forms directory, the logbook directory, the ShiftCheck logbook directory and the elog root folder.  I always get the same error.  I tried entering the absolute path, there was no difference in the result.

When I disable the password file I am able to post without any problems.  Can you help me out? 

Jonathan

Cool, I didn't know that trick myself, thanks for sharing.

Unfortunately not possible.

Stefan

Want to use the find function from ELOG to search for empty fields ( Attributes that are not defined ) 
How to do that ? 
Could not find it in the Forum.
 

Greetings Arno Teunisse
 

Dear all,

I just wanted to share a small script which I wrote to integrate our ELOG in Slack. This allows us to be notified immediately if there is a new logbook entry directly within the appropriate Slack channels. We're using ELOG V2.9.2-245 but if the log-file format has "Subject, Author, Type" in the header, it should work with any other version. I'm using Pyinotify for the file watch which relies on a Linux Kernel feature (merged in kernel 2.6.13) called inotify, so the script only works on Linux.

Here is the code: https://github.com/tamasgal/elog-slack

Cheers and thanks for ELOG!

Tom

I suspect that this might be a Debian packaging issue; however no one replied to my help request on the Debian forums so I try posting the question also here. I insatlled Elog on my Debian Jessie machine, I can open it with a browser but when entering a new post just a simple plain text editing box is shown instead of the WYSIWYG editor, and no drag and drop area for attachments is shown. When I start the elog service with "systemctl start elog" I get this suspect message in the journal: "FCKedit NOT detected". Indeed, I see that the elog installation creates a symlink which I guess is supposed to point to the fckeditor installation, which nevertheless is missing:

root@static-3-080:/usr/share/elog/scripts# ll fckeditor
lrwxrwxrwx 1 root root 15 Oct 25  2014 fckeditor -> ../../fckeditor
root@static-3-080:/usr/share/elog/scripts# ll ../../fckeditor
ls: cannot access ../../fckeditor: No such file or directory

Is this a Deban misconfiguration or a bug in Elog? thanks

Thanks for reportung that bug. I fixed it in revision f828049.

There seems to be a small problem with the new "Date/Time format <attribute>" implementation. It works great for the detailed view of a single entry:

But fails to work on the list view (same entry, the Date column is formated as it should):

Relevant config part:

Time format Time Start = %H:%M:%S
Time format Time End = %H:%M:%S

I am interested in using LDAP authentication for elogd on Windows for which it looks like I need to compile from source, enabling LDAP in the make file.

Does anyone have advice on build environments for Windows in which they have had success making elog?  Free ones preferably, such as Cygwin. 

Version 3.1.1, released August 4^th, 2015

• Updated CKEditor to version 4.5.1

• Implemented "Date/Time format <attribute> = ..."

• Implemented "Use Email Subject Edit = ..."

• Replaced "Back" by "Delete" button

• Fixed many issues with Draft Messages

• CSS file is now in *addition* to the default file elog.css

• Added LDAP documentation

• Added "Logout to URL = ..." option

• Added description of Apacher server authentication

Thanks, I included your changes in the distribution.

I updated the current version with this change (CKEditor 4.5.1) and indeed it fixes the problem. The change is comitted to the git repository and will be contained in the next release.

Hi,

following the author of imagepaste one should upgrade the version of th CKEditor to a version >= 4.5. So replacing the folder ckeditor with a new version helped.

Best,

Jan

hello, in my spare time, I try to fix some bugs, typo, and update for Indonesian translation

I got some spa

Hi Stefan,

Thanks for the explanation.  I realised it was just an error message of no real import, but it can get irritating at times.

Cookies are sent from your browser. ELOG has no influence on what the browser sends where. Probably you run your calender at the same machine where ELOG is running, so all the cookies your calender app stores in your browser are sent to ELOG as well. ELOG just complains about something it does not know, but otherwise this message can be simply ignored. Of course you can delete your cookies in your browser, but after the next call to your calendar app they will show up again.

On my linux box, every time I select a thread, or start a new entry etc, I see that one or many cookies are sent.

On a terminal, I get the message

Received unknown cookie "CalciumDisplayParams"

Now I do have a perl script called Calcium, (Calendar viewed through the browser) but it's definately not running now, not in any browser window, and in any case why should an action of ELOG trigger this?  I realise it may be due to an idiocyncratic set up of this box.  But in normal operation, I doubt the user would see these cookies being received.

Ok, fixed again.

Hi Stefan,

there is a little problem with the Makefile (on SL5 and SL6): the following line:

        @$(INSTALL) -m 0644 themes/default/* $(ELOGDIR)/themes/default/

/usr/bin/install: omitting directory `themes/default/icons'
make: *** [install] Error 1

When I go back to the old Makefile construct:

        @$(INSTALL) -m 0644 themes/default/icons/* $(ELOGDIR)/themes/default/icons/
        @for file in `find themes/default -type f` ;\
          do \
            if [ ! -f $(ELOGDIR)/themes/default/`basename $$file` ]; then  \
              $(INSTALL) -m 0644 $$file $(ELOGDIR)/themes/default/`basename $$file` ; \
           fi; \
          done

then it seems to work again.

Cheers

Andreas

Hi,

I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.

In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:

elog.css:

td {
  color:black;
  font-size:12px;

}

Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:

td {
  font-size:18px;
}

This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.

The modification is committed to GIT and will be contained in the next release of elog.

/Stefan

The changelog is here: http://midas.psi.ch/elog/download/ChangeLog

It is save to install the new version over the old one.

congrats, any detail changelog? I assume in software packages?

is it save just install and overwrite the old version?

This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments, it contains a long awaited "autosave" feature.

Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). If your browser crashes or closes for some reason, you will loose your entered text. To avoid that, ELOG starting from version 3.1.0 has an autosave feature. Whenever you enter some text, it is saved in the background as a draft message to the server. If your browser is closed by accident, you always can go back to the logbook, click "New" and ELOG will tell you that there is a draft message and asks you if you want to edit it. When you edit and regularly submit this message, it becomes a "normal" entry and the draft flas is removed. In addition to the background saving, there is now also a "Save" button so you can manually save your text to the draft entry.

I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.

Happy Easter,
Stefan

zezerze

 Dear Stefen,

Please help me & reply on my request. Is my global config correct?

 Dear Stefan

Thank you for your reply. Please check is my entry correct?

port = 8080

Admin user = harish

url = http://localhost:8080

;Find Menu commands = Logout, New, Find, Select, Config, Last day, Last 10, Help

;Guest Menu commands = Login, Back, Find, Last day, Last 10, Help, Logout

;Guest Find Menu commands = Login, Back, Find, Last day, Last 10, Help

SMTP host = smtp.omantel.net.om

SMTP port = 25

$telnet smtp.omantel.net.om 25

$AUTH PLAIN

SMTP username = harish.amin@holiday.co.om

SMTP Password = ********

Subst Email = $user_email

Logfile = errorh.log

Email Encoding = 4

Entries per page = 50

;Logfile = harish.log

;Logging level = 2

 For the login to your email sever, the password is encoded in base64 form (actually not really secure). Somehow your server does not support this. Unfortunately I cannot test this without access to your server. But you can try yourself by doing a telnet to your mail server like:

$ telnet <server.domanin> 25

...

$ AUTH PLAIN

With the "plain" method, you should be able to enter your password in plain text (not base64 encoded), and see if that works. If you are successful, I can add this option to elog.

Best,

Stefan

 Dear Team,

I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter

The details are as below : (Please note I have replaced the password with the * marks)

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******

21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******

Please help me to resolve this issue.

Thank you

Harish Amin

Andreas Luedeke wrote:

Chris Jennings wrote: Chris Jennings wrote: I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old? Thanks in advance, Chris  Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort. I think I remember that this has been discussed earlier: it is a little bug in elogd. You can see where it comes from if you type in the little command 'date -d "9-Sep-2001 3:46:40" +%s' Converted to "seconds of the epoche" (seconds since 1970-01-01 00:00:00 UTC) the date "9-Sep-2001 3:46:40" has one digit more than "9-Sep-2001 3:46:39". Since elog makes a string comparison, suddenly 1'000'000'000 is less than 999'999'999; therefore the wrong sorting. Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'. Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again!

Ok, well before 2286 approaches I fixed that bug and committed it to the GIT repository (master branch).

/Stefan 

Workaround: you can modify your old entries and add a leading zero to all entries where your specific date field starts with a '9'.

Stefan: you should fix it at least well before 20-Nov-2286 18:46:40, when the same bug strikes again!

I tried to attach a screenshot showing this, but kept getting a 502 bad gateway error.
The message in the red banner is
Error sending Email via <i>"psquad.psi.ch"</i>
with that html showing, by the way.
> Hi Stefan and Andreas,
> 
> When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
> a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.
> 
> The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
> to it but the change in layout wasn't warmly welcomed.
> 
> Also, shame that moving from Subversion means that the increments are no longer in easy numerical order.  So I
> believe that I am commenting on the latest possible version available, a738232.
> 
> A question.  My logbooks directory is now 1.8GB.  Yes, there are a lot of attachments etc to bulk it out, but
> it's all plain text comments.  Is there a limit as to the size, or total number of entries?  Elog takes a
> notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
> be caused by this.  Anyone any thoughts?
> 
> I don't know how I managed it, but I got elog to generate two entries with the identical ID no.  The new entries
> were different as well.  The log file faithfully had recorded the two separate replies to the entry having the
> same ID no as well.   Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
> copy.  I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
> it appears, it appears in two or three places within the list of threaded entries.

Hi Stefan and Andreas,

When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.

The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
to it but the change in layout wasn't warmly welcomed.

Also, shame that moving from Subversion means that the increments are no longer in easy numerical order.  So I
believe that I am commenting on the latest possible version available, a738232.

A question.  My logbooks directory is now 1.8GB.  Yes, there are a lot of attachments etc to bulk it out, but
it's all plain text comments.  Is there a limit as to the size, or total number of entries?  Elog takes a
notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
be caused by this.  Anyone any thoughts?

I don't know how I managed it, but I got elog to generate two entries with the identical ID no.  The new entries
were different as well.  The log file faithfully had recorded the two separate replies to the entry having the
same ID no as well.   Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
copy.  I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
it appears, it appears in two or three places within the list of threaded entries.

The ELOG repository has been moved from Subversion to GIT. While the old repository will be visible for some time, all new development is done on the GIT repository. To download the repository, do a

git clone https://bitbucket.org/ritt/elog.git
git clone https://bitbucket.org/tmidas/mxml.git


or access it online at https://bitbucket.org/ritt/elog/

/Stefan 

This is one of the rare cases where it helps to read the manual: https://midas.psi.ch/elog/userguide.html#add (You may need to upgrade to elog 2.9)

If you want to replace the old URLs with the new ones, you can edit the logbook files with the entries. The attached script allows you to do so easily. But be careful, try it on a copy of your data first.

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

I am on an experiment that used ELOG for all documentation and meeting notes. In our meeting notes we link to elog posts that had been discussed during the meeting. We had done this by hyperlinking the URL to the entry. Recently we had to move our logbook to another machine and so none of our hyperlinks work since the URLs have changed. I noticed that when one creates a new entry in the subject they can reference another post. Is there a way to link another elog in the body of the elog by using its logbook name and id number without having to use a URL?

Thanks in advance

 I haven't found a specific way to block viewing a log book. 

I use the top groups settings to keep users in the logbooks they only need access to.

Example

Top Group = Logbook Group1, Logbook Group 2

Group Logbook Group 1 = Logbook1, Logbook2

Group Logbook Group 2 = Logbook3, Logbook4

Then only assign users for logbook1 and logbook2 that you wish to view those logbooks only. They would have to go to the specific top group url in order to view the logbooks.

Then you can go to http://elogurl/(top group)/

And essentially just have the users view the only logbooks they are assigned to.

 The only way I find for this trouble is using the "Login user". But we have something best?

 Thanks for help. It work's. 

 But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it? 

I didn't find this in manual.

 Installed both on a Windows 2003 R2 server (32bit) and Kerberos not authenticating, yet gievs me a ticket thru kinit.

The kerberos install, installed the Network Identity Manager and placed krb5 config in my windows directory.  Can a server run lsass.exe only?   or does the krb5 config file and Network Identity Manager need to be on the server?

You can leave the password just blank.

The "Allow password change = 1" does not make any difference. It works here even with this option.

So I have no idea why you have that problem. Does it work on another computer, i.e. is it related to the 64 bit VM machine?

Best regards,
Stefan 

 I have a logbook installed on a Windows 64 bit VM server 2008 R2 and can access it fine using the password file.  However when using Kerberos it does not authenticate correctly.  I installed Kerberos and pointed it to the realm an domain controller.  Using KINIT command line it appears to accept my password.  Any help is appriciated.  Perhaps some other diagnostics i could try against the kerberos install

Here is global settings:

port = 49212

ssl = 1 

url = https://my-elog.domain.com:49212/

Authentication = Kerberos, file

Kerberos Realm = DOMAIN.COM

Admin User = me

Max content length = 10485760

Password file = pw.txt

Allow password change = 1  (perhaps this is an issue???)

Also...when adding users to the logbook, do you leave the password blank if using Kerberos?

 Hello, you can use the "Deny" flag in the config file for each logbook.

Deny <function> = <user>

Example: Deny Edit = Gian

simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.

Hope that helps.

Elog Syntax guide is helpful for this stuff too.

 How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc. 

I want know too, how can I erase configuration of SMTP?  I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host. 

Andreas Luedeke wrote:

David Pilgram wrote: [...] [...]  May I make a suggestion here?  Something I do for other reasons.  I run two separate elog daemons, each with their own configuration files.  In this case you could have one configuration file tout en française, and the other in English.  This gets around the language setting being in the Global section of the configuration file elog.cfg Of course this needs a little planning, for example a small script/batch file to start up each daemon with the correct config file. - so on my linux system, I start one with /usr/local/sbin/elogd -p 8080 -c /home/logbooks/elogd0.cfg -d /home/logbooks and the other with /usr/local/sbin/elogd -p 8081 -c /home/logbooks/elogd1.cfg -d /home/logbooks The disadvantage is that you cannot click between French and English by the tabs along the top of the elog page, you'd have to switch between browser windows. Hope this helps. David. Does this work nice and stable for you? I've tried at the beginning to run two server on one host, one in German and the other in English. I experienced occasional server crashes (every few days) and assumed that they were related to two mirrors running on the same host. A mirror server just for a second language was not of big importance to me, therefore I did shut down the mirror server. And the server stopped crashing then. Was that just coincidence? I recognised that you are not running a mirror, you let both logbook processes access the same data. Is that save? Did you ever see data corruption from two processes modifying the same data? Or is one of the ELOG servers not used much?   Thanks for sharing your experience! Andreas   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English

 I'd better put some caveats in here, then!

The two daemons on my host were never accessing the same subdirectories of /home/logbooks (this is my location, for ease of data backups (*)), and they were running with owner 'nobody', i.e. that's the owner of each directory.  In that sense they were independant, and as I was the only user, only one daemon would be working on files at any one moment. 

Next is that my system is never running for so many days uninterrupted.  The computer sometimes has to be booted into Windoze to use the CAD program, or even was just shut down and switched off.

I realise now that my earlier reply may have lead people to think they could work on the same data with two separate daemons (so as to work in their own language, but the data would be in both....) but I never meant to give that impresssion.  I've simply not tried it.  It might work on a stand-alone system, but I don't know how elog copes with multiple users accessing data at the same time - lock files?  check to see if data has been altered before allowing a submission is probably not done (it would make a branch if branches were allowed, I think) - I don't have the experience of using elog under these circumstances.  I thought Philippe Rousselot wanted a French language logbook and a separate English language one.  If I'm wrong there, sorry to raise his hopes.

Make a nice little project for someone to explore the limits, and maybe find what changes are needed.  Not necessarily to impliment it, though.

As for data corruption, never seen any, but I suppose the general warning of keep the backups well up-to-date.  I have had trouble with data, in particular moving data between logbooks, and this is one reason I have experience of how to make an elog entry using a text editor, as well as how to modify entries - to assemble scattered entries into a thread, or split a long thread into two shorter ones for ease of handling.  But I don't think those were ever connected to having two deamons running on one host, it happens when just one is running.

(*) In principle, all my data can be put on a memory stick - currently 16GB - and then I can run any linux box with full access to all my data, with the memory stick mounted on /home.

Philippe Rousselot wrote:

Philippe Rousselot wrote: Andreas Luedeke wrote: Philippe Rousselot wrote: Bonjour, tout est dans le titre. Merci For those who speak strange languages, I asked how to get a french version of elog. By the way, this is my second mail because I forgot to give an icon to the first mail, and when I hit Back to do so, my text was erased. Bug or normal obnoxious attitude of my browser ? Thanks in advance Philippe  ELOG comes "internationalised": you just need to set your desired language in the configuration files. Language = french in the configuration file elogd.cfg does the trick. If you are capable to read the English language (which I suppose ), then I would recommend reading the manual, e.g. https://midas.psi.ch/elog/config.html#global Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   PS: I happened to have the same problem (text erased after "back") when I had javascript disabled in the browser. If you have it enabled, you'll get a popup window that tells you what mandatory fields are missing in your post. Then you'll not need to use the back button.  Hi, Thanks for the answer. I tried this (directly from de setting menu in the demo account as well as from the onfig file) : I modified of course the text that could be modified directly from there such as menus and submenus. I added Language = french, I restarted the server, clear the cache of firefox (IE as well), but list, new and so on appear in english even they are in the locale file... Indeed, the manual is very interesting concerning javascript, it is activated ... Thanks again Philippe  Found it !   I wanted to have locale set in the folder demo (so I could have one in french and one in english). Once language set in globals everything went fine. Almost... Philippe

 May I make a suggestion here?  Something I do for other reasons.  I run two separate elog daemons, each with their own configuration files.  In this case you could have one configuration file tout en française, and the other in English.  This gets around the language setting being in the Global section of the configuration file elog.cfg

Of course this needs a little planning, for example a small script/batch file to start up each daemon with the correct config file. - so on my linux system, I start one with

/usr/local/sbin/elogd -p 8080 -c /home/logbooks/elogd0.cfg -d /home/logbooks

and the other with

/usr/local/sbin/elogd -p 8081 -c /home/logbooks/elogd1.cfg -d /home/logbooks

 

The disadvantage is that you cannot click between French and English by the tabs along the top of the elog page, you'd have to switch between browser windows.

Hope this helps.

David.

Philippe Rousselot wrote:

Andreas Luedeke wrote: Philippe Rousselot wrote: Bonjour, tout est dans le titre. Merci For those who speak strange languages, I asked how to get a french version of elog. By the way, this is my second mail because I forgot to give an icon to the first mail, and when I hit Back to do so, my text was erased. Bug or normal obnoxious attitude of my browser ? Thanks in advance Philippe  ELOG comes "internationalised": you just need to set your desired language in the configuration files. Language = french in the configuration file elogd.cfg does the trick. If you are capable to read the English language (which I suppose ), then I would recommend reading the manual, e.g. https://midas.psi.ch/elog/config.html#global Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   PS: I happened to have the same problem (text erased after "back") when I had javascript disabled in the browser. If you have it enabled, you'll get a popup window that tells you what mandatory fields are missing in your post. Then you'll not need to use the back button.  Hi, Thanks for the answer. I tried this (directly from de setting menu in the demo account as well as from the onfig file) : I modified of course the text that could be modified directly from there such as menus and submenus. I added Language = french, I restarted the server, clear the cache of firefox (IE as well), but list, new and so on appear in english even they are in the locale file... Indeed, the manual is very interesting concerning javascript, it is activated ... Thanks again Philippe

 Found it !

I wanted to have locale set in the folder demo (so I could have one in french and one in english).

Once language set in globals everything went fine. Almost...

Philippe

Andreas Luedeke wrote:

Philippe Rousselot wrote: Bonjour, tout est dans le titre. Merci For those who speak strange languages, I asked how to get a french version of elog. By the way, this is my second mail because I forgot to give an icon to the first mail, and when I hit Back to do so, my text was erased. Bug or normal obnoxious attitude of my browser ? Thanks in advance Philippe  ELOG comes "internationalised": you just need to set your desired language in the configuration files. Language = french in the configuration file elogd.cfg does the trick. If you are capable to read the English language (which I suppose ), then I would recommend reading the manual, e.g. https://midas.psi.ch/elog/config.html#global Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   PS: I happened to have the same problem (text erased after "back") when I had javascript disabled in the browser. If you have it enabled, you'll get a popup window that tells you what mandatory fields are missing in your post. Then you'll not need to use the back button.

 Hi,

Thanks for the answer. I tried this (directly from de setting menu in the demo account as well as from the onfig file) :

I modified of course the text that could be modified directly from there such as menus and submenus.

I added Language = french, I restarted the server, clear the cache of firefox (IE as well), but list, new and so on appear in english even they are in the locale file...

Indeed, the manual is very interesting

concerning javascript, it is activated ...

Thanks again

Philippe

If you are capable to read the English language (which I suppose ), then I would recommend reading the manual, e.g. https://midas.psi.ch/elog/config.html#global

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

PS: I happened to have the same problem (text erased after "back") when I had javascript disabled in the browser. If you have it enabled, you'll get a popup window that tells you what mandatory fields are missing in your post. Then you'll not need to use the back button.

Bonjour,

tout est dans le titre.

Merci

For those who speak strange languages, I asked how to get a french version of elog.

By the way, this is my second mail because I forgot to give an icon to the first mail, and when I hit Back to do so, my text was erased. Bug or normal obnoxious attitude of my browser ?

Thanks in advance

Philippe

 I managed to package Elog v2.92 build 2462 into and QNAP installer QPKG package.

This is for x86 based QNAP NAS only.

Note: You must have adduser package installed prior to installation.
Login to the NAS with SSH and type:
apt-get update
apt-get install adduser

BR,

Per

You haven't found it. Just look here:

http://midas.psi.ch/elog/config.html#access

You need Password file and Login user. 

Hi,

the manual says:

"
There are four ways through which access to a logbook may be controlled:

it may be open for all to read ;
it may require a common "read" password for all users ;
it may require each user to have an individual user account (login name) and password ;
finally, access may be granted or not depending on the address of the workstation you are using.
"

But it doesn't say how to do so or at least I didn't find it.

If I have each user have to log in with an individual accout, can I define which logbooks he can read and/or modify?
If yes, how to do that?

Also, please accept my vote for user groups. We can use that, too.

TIA,
Roland.

I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)

Per

Dear ELOG users,

the ELOG discussion forum at PSI contains in meantime many old accounts with non-functional email addresses. Since this causes some overhead, it has been decided to clean up the current account database. In order to keep your account alive, please log in at the above forum before Friday, Sept. 30th, 2011.  If you fail to log in until that date, your account will be automatically deleted. Note that it will be always possible to re-create your account afterwards by simply clicking on "Register as new user", but before that you won't get automatic email notifications any more once your account has be deleted.

Sorry for the inconvenience, but the database contains currently too many wrong email addresses causing some flooding of our mail systems.

Best regards,

     Stefan Ritt

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt

 Andreas, thank you very much. I was able to get the stand alone function working fine on my site, including a number of add'l attributes and options (SSL, etc).

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt