Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 193 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6444 Entries 
Goto page Previous  1, 2, 3 ... 192, 193, 194 ... 804, 805, 806   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subject
  68275   Thu Mar 3 14:51:55 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows2.9.2Re: Attribute Field Size Limited to 255 Characters

No. At least there is no simple method.

You would need to edit the source code and recompile elogd. But the number 256 is used for about 300 times in the source code, you'll have a hard time finding the right one to increase.

Cheers, Andreas

Mike Bodine wrote:

I currently have an Attribute defined in my .cfg file as  "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?

 

  68274   Thu Mar 3 00:12:45 2016 Question Mike BodineMike.Bodine@alcatel-lucent.comQuestionWindows2.9.2Attribute Field Size Limited to 255 Characters

I currently have an Attribute defined in my .cfg file as  "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?

  Draft   Thu Mar 3 00:02:26 2016  Mike BodineMike.Bodine@alcatel-lucent.comQuestionWindows2.9.2Attribute Field Size Limited to 255 Characters

I currently have an Attribute defined in my .cfg file as  "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?

  68272   Sun Feb 28 18:24:58 2016 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux3.1.1Re: Execute new|edit doesn't seem to work

Juergen Diefenbach wrote:
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
[...]
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected. Frown
[...]
Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you!


I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0

If that is the case then Stefan will know where to look Wink

Cheers
Andreas
  68271   Fri Feb 26 18:11:14 2016 Reply Devin Bougiedevin.bougie@cornell.eduBug reportLinux3.1.1Re: Links to images in notification message

From the notification I received, it looks like "2" is a problem with this server.  In the email notification, we would like images to be a link to a URL displaying the full-size image (as they are in v2.9.2).

Thanks,

Devin

  68270   Fri Feb 26 17:35:54 2016 Entry Juergen Diefenbachdiefenba@uni-mainz.deBug reportLinux3.1.1Execute new|edit doesn't seem to work
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.

When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script will then automatically stage all changes and create an appropriate git commit message. For a "new" entry in the logbook the commit message is a bit more verbose. When editing or deleting a message only a short commit message like "Edit message 25" should be created. Therefore I really need to distinguish between "new", "edit", and "delete".

However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected. Frown

What I did so far to understand what goes wrong is I looked into elogd.c and found in
void submit_elog(LOGBOOK * lbs)
that bedit is sometimes true and sometimes false, when creating a new entry, although it should be false then (right?).
This is why elogd then sometimes retrieves the wrong shell command from getcfg(lbs->name, "Execute edit"...) instead of getcfg(lbs->name, "Execute new"...) around line 23610 (not exact due to some eprintf()s inserted here and there to look at bedit and so on).

When deleting an entry, everything works fine: the shell command defined via "Execute delete=" is run, but this happens somewhere else in the code so it's not a surprise.

Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you!
  68269   Fri Feb 26 17:20:52 2016 Question Devin Bougiedevin.bougie@cornell.eduBug reportLinux3.1.1Links to images in notification message

We see two problems with the notificaiton email when attaching an image inline using drag-and-drop.

  1. The thumbnail does not appear in its proper location inline.  There is a ? placeholder where the thumbnail should be, and the thumbnail then appears at the end of the message.
  2. Neither the ? placeholder nor the thumbnail that do appear are clickable.

Our v2.9.2 test installation exhibits the desired behavior.  

  1. The thumbnail appears in its correct location inline.
  2. If you click on the thumbnail, you arrive at a URL displaying the full size image.

I am not able to drag-and-drop into the body of this message to test the behavior here.  I am attaching  a screenshot showing an example of the problem from our server.

Any suggestions would be greatly appreciated.

Many thanks,

Devin

 

 

 

 

  68268   Fri Feb 26 09:09:03 2016 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.1-1Re: Possible bug in elogd execute_shell

Absolutely correct! Nice to see compilers getting better and better. I changed the code and committed it.

Nigel Warr wrote:

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:

      for (i = 0; i < MAX_ATTACHMENTS; i++)
         generate_subdir_name(att_file[i], subdir, sizeof(subdir));
         if (att_file[i][0] && strlen(shell_cmd) + strlen(lbs->data_dir) + strl$
             < sizeof(shell_cmd) + 1) {
            strcpy(p, "\"");
            strcat(p, lbs->data_dir);
            strlcat(str, subdir, sizeof(str));
            strlcpy(str, att_file[i], sizeof(str));
            str_escape(str, sizeof(str));
            strcat(p, str);
            strcat(p, "\" ");
            p += strlen(p);
         }
and the if statment is accessing the loop variable i but it is actually outside the loop. Presumably, there should be some more curly brackets here. gcc6 gave the warning:

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++)
       ^~~

 

Goto page Previous  1, 2, 3 ... 192, 193, 194 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6