| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69581
|
Mon Oct 24 14:55:44 2022 |
 | Finn Junker | fj@tvis.net | Request | Windows | 3-1-4 | Re: Up to date windows version | > Hi Finn,
>
> I've just tested the same archive on new laptop with Windows 11.
> I unzip it and double-click elogd.exe file, bypass defender warning and the server is running.
> To test, i open localhost:8080 on web client and it displays the demo logbook.
>
> Btw i didn't test it as a service. What are the 2 libs you said it misses ?
>
> .
> Laurent
>
> >
> > Hi Laurent
> >
> > I've found the attached zip files in post 69491. The one containing the ELOG probgram libary won't run on my test laptop - the service wont start
> > There is in the same thread a post from Just Keijser containing only the executables, and it won't start either. Starting the elog.exe though gives me that the exe is missing 2 dll files which can be downloaded seperately.
> > It is not easy cause there are several versions of the 2 dll files and only one working, but now my elog reports version ELOG V3.1.4-1ebfd06c
> >
> > But this cant be the solution - if so the windows version is put to the grave
> >
> > Kind Regards Finn
Hi Laurent
OK, i can recreate the unzip to folder and run elogd.exe and it works :-). If i unzip to the folder of the version installed (with the windows installer) where it runs elogd.exe as a service, the service won't start.
The problem with the dll files only applies to the post from Just Keijser containing only the executables (3 files) and these executables repport missing: libcrypto-1_1-x64.dll and libssl-1_1-x64.dll
These versions are a black box for me, are the important?
The unzip version (your version) reports: ELOG V3.1.4-395e101 (I think this is the same number as for the 2018 installed version)
The version with the 3 exe files (my version) from Just Keijser reports: ELOG V3.1.4-1ebfd06c
This site reports: ELOG V3.1.4-bcd7b50
Kind Regards Finn |
|
69586
|
Mon Nov 21 09:46:46 2022 |
 | Finn Junker | fj@tvis.net | Question | Windows | 3-1-4 | Planned maintenance at the top of ELOG listing | We use our instance of ELOG as a operations log so that newest events are sorted at the top.
Sometimes we are also up front informed about planned maintenance, and i would be nice to could "pin" them at the top - before the sorting, so that operatores could have them in mind when starting a new shift. Have anyone found a way to solve this?
Kind Regards Finn |
|
69665
|
Wed Apr 12 15:08:15 2023 |
| Finn Junker | fj@tvis.net | Info | Linux | Mac OSX | 3.1.5 | Re: New elog version 3.1.5 | 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
| Laurent Jean-Rigaud wrote: |
|
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
| Finn Junker wrote: |
|
Hi Stefan
Is there anything the community or forum can help you with or supply for creating a windows version?
Kind Regards Finn
| Stefan Ritt wrote: |
|
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
|
|
|
|
|
680
|
Wed Sep 1 03:42:22 2004 |
| filantoro | filantoro@yahoo.com | Question | All | 2.5.42 | Locking entries | I have a question about ELOG. Let's say after the user finishes his shift
and passess on to the next user on duty. A staff member would want to look
through the entries and vet them. The staff could lock the entries to
maintain integrity of the information. How can that be done with ELOG? Can
you enlighten me. Thank u. |
|
225
|
Wed Feb 19 01:46:03 2003 |
| Fred Hooper | fhooper@sushisoft.com | Question | | | Postdating the Entry Date | Is is possible to postdate the Entry Date for an entry?
The documentation lists the ability to forward date an entry, but I don't
see any ability to backdate an entry (edit the date to a date in the past).
Given that the entry date is part of the logbook entry file structure, it
wasn't obvious how to make this change.
thanks
fred |
|
345
|
Mon May 19 19:14:35 2003 |
 | Fred Hooper | fhooper@sushisoft.com | Bug report | | | Possible Bug: 2.3.7 : Welcome Title = < img src=""> not working |
Just upgraded (using rpms) elogd from 2.3.5
I am running on RH 7.3
I noticed that my custom start page did not display the Welcome title icon.
It worked fine in prior elogs.
Here's the syntax of the config file:
Welcome Title = <img src="thumb.gif"><p><font size=4 color=white>Elog</font>
Resource dir = /usr/local/elog/
"thumb.gif" is located in /usr/local/elog, and is readable by all.
I also tried the full file name in src=
<img src="/usr/local/elog/thumb.gif"> - same result.
any hints? |
|
348
|
Tue May 20 19:09:26 2003 |
| Fred Hooper | fhooper@sushisoft.com | Bug report | | | Re: Possible Bug: 2.3.7 : Welcome Title = < img src= | > > I noticed that my custom start page did not display the Welcome title icon.
> > It worked fine in prior elogs.
> >
> > any hints?
>
> Indeed there is a bug, it has to do that some icons wnt into the themes
> directory and are served now from there. So the bug will fixed in the next
> version (the fix is already avaliable from CVS). As a temporary workaround
> you just move your image to the themese/default/ directory and it should
> work.
>
> An absolute path like /usr/local/... does not work, because this would open
> a security hole (someone could access any picture on your computer just by
> requesting an absolute path in the URL), so I removed that option from the
> software and the documentation.
I did the work-around (moving icon to theme/default) and it worked. Thanks.
Now if you just port elog over to an apache and mysql enviroment, it would be
perfect! |
|
387
|
Thu Jul 3 07:25:49 2003 |
 | Fred Hooper | fhooper@sushisoft.com | Info | Linux | 2,3.8 | elog2sql - a script to convert elog logbooks to a MySQL database | Announcing: elog2sql
elog2sql was created to help translate logbooks created by the program
``elog'' from the native elog flat file format to a MySQL database. I had a
need to have the elog data in a database, and it appears from the forum that
several others had a similar need.
I created a set of perl scripts that will allow the translation of elog
logbooks into a MySQL database. The design and implementation of these
scripts are a simple one, and allow the one-time copying of a set of logbooks.
The elog2sql toolkit consists of two scripts. The first script, parsecfg.pl,
reads a elogd.cfg, and creates a sql file that will create a set of db
tables corresponding to elog logbooks. The second script, parselog.pl, takes
a set of elog logfiles, and creates a sql file that will enter the logbook
data into the database. The result is a copy of the elog logbook that can
used as desired inside the framework of MySQL. Attachments are handled by
inserting an entry of the attachment name into an seperate attachment table.
This allows multiple attachments per entry.
You can download the elog2sql program archive at
http://www.davidfannin.com/elog2sql/elog2sql.tar.gz . It contains the
scripts and basic documentation. You can read the man page at
http://www.davidfannin.com/elog2sql/index.html
email for questions or comments. |
|