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

> > may be add a parameter
> > 
> > Restrict Search all logboog = 1 or 0
> > if 1 the switch will not appear 
> 
> The flag "Search all logbooks" is already there! (I forgot about it!). So 
> just set it to "0" and you should be fine.
> 
> - Stefan

I do and it work fine

> We are interested in using your ELOG (which we consider to be a wonderful 
> application) even more. We would like to make a few adaptations in your 
> source code, above all to add some functionality that we are missing.
> 
> I was wondering if there is a way we could coordinate the development 
> together. For instance, would it be of your interest to receive the code 
> adaptations we do and implement it in your future releases? 

Sure, I'm very interested in those and ready to merge it into the main 
development tree.

- Stefan

Hello

I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
Attachments =" is not being read.  Looking at the changelog, I found that
"Number Attachments" has been removed in favor of "enable attachments".  I
tried looking in the documentation but I can't find a discription of the way
 in which multiple attachments are handled.  Can someone give me a pointer?

Thanks
Kevin

You guessed right. I give it a try soon as I get a chance. Thanks.

> I guess you have a global password file and use "login user" statements for 
> your logbooks. I have added some code which does per default not send any 
> email to people who are not in the "login user" list, in case this list is 
> present. New code under CVS. Please give it a try and let me know if it works 
> for you.
> 
> - STefan

This problem has been fixed recently. The new code is

   /* special case: "Change %s" */
   if (strstr(orig, "Change ") && strcmp(orig, "Change %s") != 0) {
      sprintf(result, loc("Change %s"), orig + 7);
      return result;
   }

Alternatively you can get the updated version from CVS.

- Stefan

> Like this one ^^^ ???
> 
> I'm joking! I fixed the bug and updated the elogd server. Please find the new 
> version under CVS.
> 
> - Stefan

Blimey! That was quick!

Many thanks for amending this.  You'll be pleased to hear that my IT Operations  
Team think this is the best thing since sliced bread...its going to replace a 
blizzard of spreadsheets.

Cheers
Fergus

Thank you, I misunderstood how the "Guest menu commands" worked I thought I had to specify
a limited set of commands to actually limit guest users.

Thanks again for your wonderful work on this program too.

Regards,

Alexandre

> Ok, now I see your problem. You defined a "Guest menu commands" which explicitly allows
> not-authorized access (that's what it's for). If you only want to allow authorized
> access, remove the "guest menu commands" from the logbook sections and also from the
> [global] section.
> 
> Please note that if an option is not preent in a logbook section, it is looked for in
> the [global] section. I see that most of your logbooks have similar settings. Just put
> them into the [global] section, and override it in the logbook section if they are
> different.