Dear ELOG users,

this is to announce an important security update. As proposed by Lukasz Olejnik (CERN/PSNC), ELOG has now switched to strong encryption of password. So everybody concerned in security is advised to update to the new version 2.8.0. Existing password files for Windows users and Linux users not using HAVE_CRYPT are automatically converted. Those installations which used HAVE_CRYPT in the past under Linux have to ask their users to re-enter their password (via the link "Forgot password") after the upgrade to version 2.8.0.

Best regards,

  Stefan Ritt

I just realized that the command line elog utility did not yet use the new encryption. So automatic elog submissions using passwords are broken in version 2.8.0. I made an intermediate version 2.8.0-2 which fixes that. However you only need to update it if you use the elog utility and have problems with the 2.8.0 version.

Actually the thumbnail files are only created if they are not there. This is done in the function crate_thumbnail():

   i = get_thumb_name(file_name, str, sizeof(str), 0);

   if (i)

      return i;

So if these files are recreated always, something must be wrong there. Or you sysadmin runs a cron job which deletes them every evening 

Well, first RTFM: "Fields marked with a * are required" on top of the elog entry page. Then, use a reasonable browser on a reasonable OS  

On Google Chrome the text is still there (actually I just tried it with this entry). No idea what Safari under OSX does. Under Windows, Safari keeps the text. Actually this is controlled by the FCKEditor inside elog which is written by someone else. So complain there! Funny: We have about 1000+ entries in this forum, and you are the first one complaining about this.

I could never get shell execution work when elogd is started as a service. This has probably to do with system permissions or so under Windows. If anybody has a clue, please let me know. Under Linux this works nicely, but this is probably not an option for you...

Please have a look at https://midas.psi.ch/elogs/Forum/66872 

Running through a SQL database requires a major rework of the software. I'm planning this in the long run, but not for this year. I'm also not sure how much this would buy you. If you do a full-text search on 140k entries in a SQL database (not index search), this might also take some time.

But what you can do is to "archive" part of your logbooks. Since the files are named YYMMDDa.log, you can move all 09XXXXXa.log files into a separate "archive" which you then do not include in your search.  

> Hi Stefan,
> 
> I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.
> 
> In searching, I either can search one logbook (still relatively quick), or all of them.
> 
> I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
> much quicker were the search confined to just that group.  I don't think I've missed anything in the
> documentation on this matter.  
> 
> If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?

You can't do that right now. I would have to extend the functionality to allow searching in groups. Also have a look 
at https://midas.psi.ch/elogs/Forum/66901. Maybe that helps a bit in meantime.