I downloaded the last elog-3.1.5-1.tar.gz to install elog.

All *.cxx files are missing.

Hi all,

I am using the Apache webserver authentication and redirection over http (not https). I have configured it 1:1 as described in the Adminguide. In the elog.cfg I set Authentication = Webserver.

All works fine; the webserver requests an authentication and elog recognizes me correctly.
However, when I close and reopen the browser and log in as a different user, elog does not change the user (tested with Firefox and Edge).
I can only change the user if I use a different browser or restart the elogd (reload is not enough).
The X-Forwarded-User header is set to the correct username - I have checked it with a CustomLog in Apache.

Best regards,
Frank

Hi,
as I understand right you can do this in the elogd.cfg via
Interface = 127.0.0.1
port = 8080

however than this can be changed by any user how has global admin rights in elog.

So I changed the line in the elogd.service startscript
ExecStart=/usr/local/sbin/elogd -D -p 8080 -n 127.0.0.1  -c /usr/local/elog/elogd.cfg

I hope this has the priority (not tested).

I found the reason of the bug:
In line 27441 of elogd.cxx the http_user is overwritten by the user saved in the sid_ array as a sideeffect of the sid_check function:
sid_check(getparam("sid"), http_user)

It can solved by changing elogd.cxx @ line 27441

27441c27441,27446
<          if (!sid_check(getparam("sid"), http_user)) { /*  if we don't have a sid yet, set it */
---
>          i=sid_check(getparam("sid"), thumb_name);
>          if (i && strcmp(http_user,thumb_name)!=0) {  /* user changed */
>             sid_remove(getparam("sid"));
>             i=FALSE;
>          }
>          if (!i) { /*  if we don't have a sid yet, set it */

Remark: I have used the variables i & thumb_name of the function in a local context.

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

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?

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

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.