Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 284 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  66926   Tue Nov 9 19:28:53 2010 Question harleyh9s@ornl.govQuestionMac OSX2.7.8Execute a python command?

Is there a way to add a button to the elog interface which would execute a python command?

  66927   Tue Nov 9 19:36:40 2010 Angy harleyh9s@ornl.govOtherMac OSX2.7.8locking entries & auto-submission?

We have multiple users for a single elog.  Aside from making an entry only editable by the author, is there a way to secure the entry if it is being edited so that only one user may edit a particular entry at one time?

Also, is there a way to auto-submit entries after x minutes?

 

Your help and support are appreciated.

Harley

  66935   Fri Nov 12 16:46:28 2010 Reply Stefan Rittstefan.ritt@psi.chOtherMac OSX2.7.8Re: locking entries & auto-submission?

harley wrote:

We have multiple users for a single elog.  Aside from making an entry only editable by the author, is there a way to secure the entry if it is being edited so that only one user may edit a particular entry at one time?

Also, is there a way to auto-submit entries after x minutes?

 

Your help and support are appreciated.

Harley

You can use

use lock = 1

as described in the documentation. Auto-submission is on the wishlist and will be implemented in the not-so-far future. 

  66936   Fri Nov 12 16:50:18 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSX2.7.8Re: Execute a python command?

harley wrote:

Is there a way to add a button to the elog interface which would execute a python command?

No, there are only the options

execute new = ...

execute edit = ...

execute delete = ...

though which you can execute external scripts. Maybe this is enough? 

  67337   Sun Sep 16 21:14:12 2012 Warning Josef Uherjosef.uher@gmail.comBug reportMac OSX2.9.2Crash with long image names

Hi All,

I found that elog crashes if I try to upload an image with long name. It actually uploads the file after the crash. It crashes also if in the full view with attachments visible. If I shorten the name all is fine.

The crash report screenshot is attached. It looks like a too small buffer (?).

 

Screen_Shot.png

  67602   Tue Nov 5 23:21:52 2013 Question A.G. Schubertalexis4@stanford.eduBug reportMac OSX2.9.2-2494Compilation failure on Mac OSX 10.9

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

 

$ make

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall  -I../mxml  -DHAVE_SSL -w -c -o crypt.o src/crypt.c

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall  -I../mxml  -DHAVE_SSL -o elog src/elog.c crypt.o -lssl

src/elog.c:125:8: error: expected parameter declarator

size_t strlcpy(char *dst, const char *src, size_t size)

       ^

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

                                                             ^

/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'

#    define _USE_FORTIFY_LEVEL 2

                               ^

src/elog.c:125:8: error: expected ')'

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

                                                             ^

/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'

#    define _USE_FORTIFY_LEVEL 2

                               ^

src/elog.c:125:8: note: to match this '('

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:53: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

 

                                                    ^

  67603   Wed Nov 6 09:04:32 2013 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX2.9.2-2494Re: Compilation failure on Mac OSX 10.9

A.G. Schubert wrote:

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.

Best regards,
Stefan 

  67605   Thu Nov 7 02:18:17 2013 Reply A.G. Schubertalexis4@stanford.eduBug reportMac OSX2.9.2-2494Re: Compilation failure on Mac OSX 10.9

Stefan Ritt wrote:

A.G. Schubert wrote:

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.

Best regards,
Stefan 

Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74.  I undid my changes to Makefile, tried to compile, but got the same errors.  

I then pulled down elog and mxml with git, and these are working for me with no errors.  Thanks!

ELOG V3.1.5-3fb85fa6