I may have missed it when reading the logs, if so, sorry about that, but I would like to know if there is a way to set a field, let us call it "process run"  Ok let me give you some details on this.

a process run may have several "work orders" or sets of parts/items in it, so it will have several separate entries in the log  such as:

date##, run123, part 1, quantity, comment

date##, run123, part2, quantity, comment

date##, run123, part3, quantity, comment

date##, run123, part4, quantity, comment

I thought perhaps to have them use the reply function to add the other 3 items of the same run, and that would work if I could find a way to set 'process run' to auto increment, say perhaps, when the next 'New' entry was entered.  Is there something in place that can already do this?  If this is possible, I thought I would see if I can change the button for 'New' to something like 'New Run' and reply to 'Add Workorder' or something along that line so there is no confusion when entering the data.

Any suggestions you might provide are greatfully accepted.

Chuck

Hi,

I am having trouble modifying the elog client to allow larger attachment.  I
have elogd configure for attchment sizes of 10Meg and I would like the
option to be able to use the elog client.  Can anyone give me key points as
to how to go about doing this?  I have tried but I must be missing something.

Also, as a suggestion, it might make sense to add a MAX_ATTACHMENT_SIZE def
in a common header file.

Thanks
Kevin

We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time 
it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of 
the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and 
sometimes the images.

The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is 
running on Debian 7. 

Any ideas what the problem could be, or how I could investigate it further to find the bottleneck?

The instructions for securing elogd using an SSL proxy are incomplete.
http://midas.psi.ch/elog/adminguide.html#secure
http://midas.psi.ch/elogs/contributions/11

If you follow these instructions, elogd will still listen for and accept non-SSL connections on it's own TCP port bypassing the SSL proxy.

(True, the elogd TCP port number is somewhat secret, so there is some security-by-obscurity here).

To secure the elogd TCP port against connections that bypass the SSL proxy, elogd has to be started
with the "-n localhost" command line options.

To add this option, one has to edit /etc/init.d/elogd. I do not know if this change will be lost when the elog rpm package is updated.

It would be better if this option could have been specified through elogd.conf.

The "-n" command line option is not documented here
http://midas.psi.ch/elog/adminguide.html#config
but is visible if you run "elogd -h".

P.S. Even with "-n localhost", users of the local machine can bypass the SSL proxy.

K.O.

Is there any way to include the text of a log message in the CSV export? 
Anyway to include a pointer to the attachment?

In version 2.6 the themes do not work right on Windows. 
The URL is fixed at whichever logbook that is selected (e.g. ELOG 2.5.9-4 is <link rel="stylesheet" type="text/css" href="default.css"> & ELOG 2.6.0-1 is <link rel="stylesheet" type="text/css" href="http://localhost:8080/demo/default.css">).

Version 2.0.5 of elog has been released today. Among various bugfixes, the 
display speed for threaded lists has been improved significantly. Display 
all messages of this forum and press the reload button to see the 
difference.