At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog.  Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).  

Is there an option in the elog.cfg to only display certain files (like .gif
or .jpg).

> Hello friends, 
> 
> Exist some form to increase limits of items (100) in the Options List
> 
> 
> 
> Thanks for any help

I believe only through an edit of the C code and a recompile, as the values
are set as constants.  I think this might be the line:

#define MAX_N_LIST      100

So, yes, there exists a way and the ease of this way is dependent upon your
comfort level with changing stefan's code.

I have a question about ELOG. Let's say after the user finishes his shift 
and passess on to the next user on duty. A staff member would want to look 
through the entries and vet them. The staff could lock the entries to 
maintain integrity of the information. How can that be done with ELOG? Can 
you enlighten me. Thank u.

Hello friends, 

Exist some form to increase limits of items (100) in the Options List



Thanks for any help

> Noee. Here it works immediately.
> 
> Can you try with a fresh server from the distribution, with the example 
> elogd.cfg, to see if there is any difference?
> 
> The killing is handled in the funciton ctrlc_handler(), which sets _abort = 
> TRUE. This  is checked in line 16195, just after the select(), and the main 
> loop is exited. The select finishes after one second, although I believe 
> that the kill signal also terminates the select prematurely. The kill 
> command and a Ctrl-C keystroke should work the same way, they both generate 
> a SIGTERM or SIGINT signal.

elogd does not exit if there is an 'unprocessed' HUP.  So when you do 

kill -HUP <pid>
kill <pid> 

elogd will only exit after it was accessed.

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?

I think the text display of ASCII files, which is new in version
2.5.4, is not a good idea.  E.g. I had a large ps file attached
to one entry and it took a long time display this entry (over DSL).
Then I saw that the ps-file is displayed as text, which is not really 
useful.  

Probably it is fine to display only files ending in '.txt' per default.
In addition a file that has more than say 1000 lines should probably 
also not be displayed (as default, optional OK).  

Cheers, Heiko

Here are some things for your wish list:                                        
                                                                                
1) elogd should report quota or disk-full problem:  In case a logbook           
   entry cannot be saved (quota or disk full) then a message like               
   'Could not save last entry.  Please contact administrator.' should           
   be displayed.  Currently nothing happens.  Only the submitted                
   entries 'vanish'.                                                            
                                                                                
2) default page view per user, i.e. the 'Back' link goes to                     
   ?mode=Full,summary,... depending on the user that is logged in.              
   Some users complained that 'Back' is not really back.  Maybe                 
   consider renaming 'Back' to 'Default View' or something.                     
                                                                                
3) (related to 1) the 'Back' link should go back to the last used mode          
   (full, summary, threaded,...) and not to the default mode                    
                                                                                
4) mark messages as unread/read on a per user basis: The                        
   implementation of this might be quite involved but it would be               
   rather useful.  One way would be to add a default attribute 'Seen            
   by' to each entry, which lists the login names of the users.  Or 
   files LOGIN_NAME.has_seen can be created which contain the entry 
   IDs of the viewed entries for each user.   
                                                                                
5) alignment of attribute table (using <td colspan=2> for multi line            
   stuff): see elog:669 :)                                                      
                                                                                
You can count my vote for:                                                      
                                                                                
- Use "and" and "or" operands in queries