I was just playing around with gcc6's new feature for warning about misleading indentation (which can often hide real bugs) and I think it found one in elog-3.1.1-1 at src/elogd.c:22538. Here there is an if statement, which looks as though it should be inside a loop, but it isn't. The code is:

src/elogd.c: In function ‘execute_shell’:
src/elogd.c:22538:10: warning: statement is indented as if it were guarded by... [-Wmisleading-indentation]
          if (att_file[i][0] && strlen(shell_cmd) + strlen(lbs->data_dir) + strlen(subdir) + strlen(att_file[i])
          ^~
src/elogd.c:22536:7: note: ...this ‘for’ clause, but it is not
       for (i = 0; i < MAX_ATTACHMENTS; i++)
       ^~~

I was just playing around with gcc6's new feature for warning about misleading indentation (which can often hide real bugs) and I think it found one in elog-3.1.1-1 at src/elogd.c:22538. Here there is an if statement, which looks as though it should be inside a loop, but it isn't. The code is:

src/elogd.c: In function ‘execute_shell’:
src/elogd.c:22538:10: warning: statement is indented as if it were guarded by... [-Wmisleading-indentation]
          if (att_file[i][0] && strlen(shell_cmd) + strlen(lbs->data_dir) + strlen(subdir) + strlen(att_file[i])
          ^~
src/elogd.c:22536:7: note: ...this ‘for’ clause, but it is not
       for (i = 0; i < MAX_ATTACHMENTS; i++)
       ^~~

Hi, 

I was just searching your online discussion forum for entries with the 
word 'password' in the subject. I noticed that the 'Full' option in 
the 'full/summary/threaded' line displays the results of all entries in the 
logbook, and not only the entries with the word 'password' in the subject.

I think there is an error in the URL, because when looking for the word 
password in the subject, the URL for the 'Full' option is:
http://midas.psi.ch/elogs/Forum/page1?mode=full&reve&npp=8&Subject=password

If I change the word 'reve' in this URL to 'reversed=1', the results are 
correct

Bartjan Wattel

> > I know I can simply copy the settings for logbook B and repeat the settings 
> > for all logbooks C-S. But is there a better way to accomplish this?
> 
> Yes. Put all common settings into the [global] section, only differences into
> the individual logbook sections. Like
> 
> [global]
> Attributes = ....
> Options ....
> 
> [A]
> ; Logbook A is different
> Attributes = ....
> Options = ...
> 
> [B]
> Option X = ...
> 
> [C]
> Option X = ...
> 
> [D]
> Option X = ...
> 
> This way all logbooks "inherit" the settings from the [global] section, only the
> differents are superseeded in the individual sections. Still you need two lines
> for each logbook, but all recurring configuration can be omitted.

Thanks for you quick and correct answer. I have one question left ;-)

Suppose I want to have different password files for all the logbooks, but I want to 
have a single (admin) user that can log in to all logbooks... Do I need to specify 
the admin data in all the different password files, or can I use one global 
password file containing the login name and password for the administrator?

Hi - again a configuration question.

How can I suppress all email notifications? The "Suppress default = 2" flag 
allows me to always produce a notification, but the flag does not provide 
an option to never produce a notification. The flag "Suppress Email on 
edit" does help a bit, but still notifications for new messages will be 
sent.

I'm looking forward to your fast response... So far your support is 
fantastic!

Bartjan Wattel

hi again,

we have been doing a bit of stress testing for Elog. The most important 
thing we found is that Elog stops responding when a user uploads a large 
attachment (we used a 240 Mb attachment). 

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

Bartjan Wattel

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?