We use ELOG inside a local network, but we want to allow access also from outside the firewall.

The suggested solution from Elog Admin Guide worked fine until version ELOG V2.6.5-1844 (essentially without FCK Editor):

ssh -L 1234:your.server.name:8080 your.firewall.name
firefox http://localhost:1234/

Howerver, since the update to ELOG V2.7.1-2002 the FCK Editor uses absolute links to insert images.

An image uploaded from the local network will have an address like:

http://your.server.name:8080/logbookname/080207_101110/Picture.jpg

while the same image uploaded through the firewall tunnel will have a link like:

http://localhost:1234/logbookname/080207_101110/Picture.jpg

Obviously images uploaded from outside are not visible from inside and vice versa.

Is it possible to convince FCK Editor to use relative links?

PS
ELOG is great!!

ssh -L 1234:your.server.name:8080 your.firewall.name
firefox http://localhost:1234/

http://your.server.name:8080/logbookname/080207_101110/Picture.jpg

http://localhost:1234/logbookname/080207_101110/Picture.jpg

I fixed this in SVN revision #2038.

ssh -L 1234:your.server.name:8080 your.firewall.name
firefox http://localhost:1234/

http://your.server.name:8080/logbookname/080207_101110/Picture.jpg

http://localhost:1234/logbookname/080207_101110/Picture.jpg

Thank you for the quick support!

I installed elog 2.7.2 rev 2041 into /data/elog on Redhat ES 4 Update 4. This is my initial elogd.cfg file:

[global]
port = 80
Resource dir = /data/elog/elog
Logbook dir = /data/elog/elog/logbooks
Logfile = /data/elog/elog/logs/access_log
Logging level = 2
Resolve host names = 0
Usr = nobody
Grp = nobody

[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

and start elogd - all is right with the world, everything is working properly. I shut down elog and try to add more logbooks using this template:
[A-B]
Subdir = cr_a-b
Comment = Change requests for Customers A-B
Menu commands = New, Reply, Download, Find, Last day
List Menu commands = New, Find
Display mode = summary

I create 14 of them, one for every 2 letters of the English alphabet and 0-9. The logbook name and Subdir change appropriately. When I start elog, it stays up for about 30 seconds, then crashes. No messages are recorded in syslog nor in the logfile. The only thing that looks suspicious are a couple lines in syslog:
Feb 15 17:11:05 iadopsutil04p elogd[23761]: elogd 2.7.2 built Feb 14 2008, 20:55:38 
Feb 15 17:11:05 iadopsutil04p elogd[23761]: revision 2041
Feb 15 17:11:05 iadopsutil04p elogd[23761]: FCKedit detected
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot restore original GID/UID.
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Feb 15 17:11:05 iadopsutil04p elogd[23761]: Server listening on port 80 ...

This is obviously the child process responsible for the highlighted lines and it's coming from the cleanup function. Why it's getting called is beyond me.
Ideas?

Feb 15 17:11:05 iadopsutil04p elogd[23761]: elogd 2.7.2 built Feb 14 2008, 20:55:38 
Feb 15 17:11:05 iadopsutil04p elogd[23761]: revision 2041
Feb 15 17:11:05 iadopsutil04p elogd[23761]: FCKedit detected
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot restore original GID/UID.
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Feb 15 17:11:05 iadopsutil04p elogd[23761]: Server listening on port 80 ...

The error message above come from the PID file /var/run/elogd.pid which cannot be removed. This file is only for information purpose, to tell any script which PID the elogd daemon has. If one elogd crashed in the past, the file might still be there although the program is not running, causing some error to show up, but which can normally be ignored.

The fact that elogd stays for about 30 seconds can only be contributed to the fact that you have very large logbooks, which are scanned during startup. You can check this by starting elogd interactively with the "-v" option. Then you will see the scanning process. The next thing is if you really get a crash, you can produce a core dump, so it can be analyzed to figure out where elogd has crashed. To my knowledge the only way you can do that is by having some logbooks with invalid data. Can you try your set-up with empty logbooks?

- Stefan

The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:

MXMLDIR = src/mxml

Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.

From your point of view that request is reasonable, but the reason of having mxml in a separate top level directory is that I use it in many different projects. If I would keep a copy of mxml in each project, I would have to update all of them manually if there is a bug. On the other hand the code of mxml changes very seldom. If you look at the history, it got ~5 changes last year, while elog itself had hundreds. And since I do not change the API, a bugfix in mxml should be to the benefit of all elog versions. It is like with other projects which depend on a number of packages. Like if you install Apache for example, you need a certain version of OpenSLL, a certain version of libcrypt, and so on.  So think of mxml like another package you have to combine with elog.