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

Is it just my system or do others have this odd issue.

I have a pdf file which is 'upside-down', I attached it to an elog entry, and the .png image thumbnail was
generated.  Now this too was upside-down, so I tried to use the left (or right) rotation buttons along the top
of the image in elog to do a 180 degree rotation.
The first 90 degree rotation was fine, but the second attempt just made a smaller image.  
It happens with various pdf files generated by various software (in case).
I also tried it with a jpg file, in that case the second attempt enlarged the image.

I could not find any way to actually invert the .png image using elog; but I was surprised that a second
rotation ddid something different (change magnification) rather than nothing at all if it could only cope with a
90 degree rotation.

It's not a vital fix for me, but I have found the thumbnail (png) manipulation functions have a few rough edges,
so when necessary I use xv or gimp on the .png file to get what I want.

Or is this just my system?

I'm using Kerberos and SSL and experience problems with individual setting of "Login user =" for different logbooks.
Sometimes (not every time, but most times) the server crashes under the following condition:
When I login at one logbook and then change to a logbook, that has a restricted "Login user" list with my login
name not in it. It created the following GDB output:

Program received signal SIGSEGV, Segmentation fault.
show_elog_list (lbs=0x916b768, past_n=0, last_n=0, page_n=0, default_page=1, info=0x0) at src/elogd.c:19793
19793         message_id = msg_list[index].lbs->el_index[msg_list[index].index].message_id;

Expected behaviour would be to show me the login page with the error message:
"you don't have access to this logbook".
This message is never shown for the attached configuration file.
If I remove the "Guest" commands for logbook "TestB" then elogd behaves properly.

For the moment I've just disabled "Login user" settings.

Regards
Andreas

Forget the previous post:
I cannot reproduce the problem with the latest version of elogd (2.9.2-2475).

Hello,

Is there still a limit of 50 attachments per topic?  If so, is there or could there be a parameter to change this setting?

Thanks,

Devin

Hi all,

I am trying to set up elog here at the University of Minnesota.  It looks very promising for helping to manage a fairly complicated operation.  I've got most of what I want set up without too much difficulty.  However, I find that I'm having some difficulty to get it working properly with email.

In particular, I have my account set up to email me when log entries are made (subscribe to logbooks option is selected).   In the global section of my elogd.conf file I have set up the variables:

SMTP host = factoryserver5
SMTP username = factory

However, when I make a test entry, I get an error at the top:

Error sending Email via <i>"factoryserver5"</i>: 5.5.1 Error: authentication not enabled

I tried setting the password using "elogd -t" but to no avail.  I also tried a few different values for SMTP host

Any suggestions as to what I am doing wrong?

Cheers,

Satish

Updating my toolbox.  Starting to use elog as, well, a logbook.  Kind of liking the short, sweet, to the point capabilities.

Which leads me to wonder if anybody has opinions on trouble ticket systems that work well with elog?

Thanks!

Miles Fidelman