Hi All,

I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?

Regards,

Per

Hello folks,

Can we have a better support under modern Linux distributions?

I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.

The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:

First of all because it's in /etc/rc.d.

The second problem is in this line:

# Source function library.

#. /etc/rc.d/init.d/functions

The file doesn't even exists.

The third problem is the echo_success; echo_failure commands that doesn't even exist. As I can see it's definitions are sourced in the functions file that doesn't exist.

After removing this missing commands or files from the init.d; I can call elogd script and start the daemon under root. Appears to be working...

And last but not least; there's a way to standardize the init script to run in other Linux distros, so we can put it to start automatically at boot time?

Many thanks in advance,

Vinícius Ferrão 

PS: I'm not asking to support any creepy distros, but to support the .deb package format and system style.

I'm not using Debian so I cannot give support there. There was some Debian support a few years ago, but the maintainer has gave this up. If you find someone who volunteers to do the job (yourself?) I'm happy to include the Debian specific files in the distribution. 

Stefan

The Debian init script contributed here has been working quite well for me for the last few Ubuntu versions. Unless you edit it, it sets the elog base directory to /etc  so that's where you have to put your themes dir, resources, .conf file, scripts, logbooks, etc. I use symlinks to actually store my logbooks elsewhere.

I would also vote for a sane deb package. Right now, when I upgrade ELOG, I don't even run make install, I just copy the compiled binaries to their respective directories (/usr/bin or /usr/sbin). The rest stays the same.

Hi Louis,

I'm a little surprised by your comment that you use symlinks 'to store your logbooks elsewhere'.

I start the daemon with

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

so that both my logbooks *and* the config file are both based on my preferred location, which is a subdirectory of /home.  No symlinks  OK, themes are elsewhere, but for backup purposes, that's a rather lesser issue. 

I have no idea why the default logbook location is /usr/local/elog/logbooks which does not strike me as a sensible location (at least on Slackware).  Maybe such an odd location was to force users to choose a better location...(the -d switch).

To all:

I use Slackware (currently 13, I hear there are some issues with 14 for programs I wish use), and I compile from the sources.  Usually from random svn versions as a general pain-in-the-neck for Stefan.  I've never had to make a [Slackware] package for distribution - I have issued patches and/or source distribution, depending on your point of view.  If someone can provide the advice, I'd certainly try and do a Slackware distribution, but I do have Real Work to do as well, so it may not be done immediately.  I think Ubuntu is fairly close to Slackware, not sure about Debian, which I *thought* was close to Red Hat.

Now I *do* understand what some of the other contributors to this thread are doing, as I do something similar for other programs that are now unmaintained and no longer compile with GCC4 or earlier.  The email program I use is a ten-year-old binary & libraries I compiled under Slackware 7 (if not, 4), and I copy the relivent binaries, libraries and dependances across when I upgrade the o/s.  Yes, one day it will fall down.  Three other programs I regularly use are similarly now 'legacy'.  My 'C' coding isn't up to the major changes apparently needed to allow them to compile again with a modern compiler.
 

Hi everyone,
we have formerly used the DOOCS eLogBook from DESY for a couple of years for some application at our large
research facilities. Now we have standardized on ELOG and I've got a request to import the old DOOCS eLogBook
data into the new logbooks.
I've looked into it and the import appears to be fairly straight forward. I have two questions to the community,
before I start to program an import script:

1) Has anyone created such an import function already, and if the answer is yes, can I have it?

2) Would anyone else be interested in such a "cross logbook import", and if yes, what are your requirements?

Thanks
Andreas

Hello community,

I have a feature request for the form of the ELOG.

For some users, especially coming from a MAC background, it is very inconvenient to press enter (ie. on the subject field) and post a message (or get prompted to do so). Instead, enter in these fields should work as a tab.

Cheers, keep up the good work,

Daniel