> Is it possible to add a flag in the configuration file, to specify the 
> maximum size of an attachment?

I implemented a "max content length = xxx" flag, which defaults to 10MB. If an
attachment is larger, an error gets displayed. The problem is that elogd can
only send the error message to the browser *after* it received the whole
request, so it has to "drain" the 240 MB first, which could take quite some
time on a slow connection.

Alternatively, I can cut the connection to the browser immediately, since the
HTTP header contains the content length after the first ~500 bytes, but in
that case the browser only shows a message box "Document contains no data"
which gives the user noe clue of what's wrong.

Anyhow the biggest problem of elog in high stress environments is that it's
single threaded. So if someone issues a search in a large logbook, it could
take some time, in which elog cannot respond to other requests. Maybe I will
find time in the future to make elog multithreaded, but certainly not in the
near future.

> > Is there something else  which is making this difficult to do?
> 
> Not really, but hsearch() & Co. are not available under Windows, so I have to extract the
> source code from the GNU C libarary or so. Since the last discussion I had lots of other
> topics on my to-do list, such as mirroring and cloning, but the speed issue is getting more
> and more up on the priority list.

Speaking of windows I'd like to note that when I moved my call tracking config from a slow BSD
system (PPro 200Mhz) to a faster windows system (P3 733M) I noted a huge slow down in the
interface.  Talking about perhaps 1-2 seconds before to 10-15 seconds after.  Using
sysinternals file monitor I see that elogd is hammering each log file in the directory.  Not
sure what else is going on.  309 log files - only 1.25Meg.  

Anything I can do short of pruning down the files?

[Edit:  In both cases above my default view is filtered and sorted - so that I only see things
with a specific status.  Taking away the filtering resolves this hit - but does not explain the
speed difference between platforms.]

-D

Hi,

I have an ELOG installation on a RedHat linux server, called myserver. I 
can connect to this server with the following entries in the elogd.cfg file:
   [global]
   URL=http://myserver:8080
This works fine. I can log in, select logbooks, edit/create entries etc. 
etc.

However, I want this connection to be encrypted. So I activate stunnel (v4) 
in such a way that stunnel listens to port 8081 and forwards to the 
("remote") port 8080, which is the "original" elog port. I change the URL= 
entry in de elogd.cfg file to URL=https://myserver:8081 in order to use the 
SSL encrypted connection.

At this time, when I connect to https://myserver:8081 I get the 
welcome/login screen, but when I enter the (correct) username and password, 
the elog program does not show the contents of the logbook buts shows the 
loginscreen again. If I enter a wrong username/password, I do get a correct 
error-screen. So it seems that the connection is correct, but there is some 
sort of problem in ELOG. Anyone who can give me a hand here?

That bug has been fixed recently, please update to the newest version.

Is there any way to automatically export the logbook(s)? 

> Is there any way to automatically export the logbook(s)? 

Kind of. You can use "wget" under Linux (use cygwin under Windows to get wget
under Windows). Then issue a

wget "http://midas.psi.ch/elogs/forum/?cmd=Search&mode=xml"

and you will get an XML export. Same works with CSV export. If you put that
command in cron, you have this on an automatic basis.

> > Is there any way to automatically export the logbook(s)? 
> 
> Kind of. You can use "wget" under Linux (use cygwin under Windows to get wget
> under Windows). Then issue a
> 
> wget "http://midas.psi.ch/elogs/forum/?cmd=Search&mode=xml"
> 
> and you will get an XML export. Same works with CSV export. If you put that
> command in cron, you have this on an automatic basis.

Thanks Stefan! That was exactly what I was looking for!

Hi,

I am very much interested in using elog as a shift logbook for SOLEIL
accelerators.

I tested most of the options. Every thing works well except the conditional
attributs when French language is selected. In this case, I lost the
selected list option in the Field Equipement.

Here a simple exemple for testing.
NB: tests were done using the last and before last elog version.

I switched the language from English to French in Global options

Attributes = Accelerateur, Equipement
Options Accelerateur= Linac{1}, LT1{2}
{1}Options Equipement= cannon, section1
{2}ROptions Equipement= Alimentation, Diagnostics

I guess this is a simple bug since this problem does not exist for other
languages.

Best Regards,

Laurent Nadolski