| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
Text |
 |
|
68844
|
Wed Sep 12 20:52:22 2018 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source | Stefan said "code is commited":
that means you can download the latest version
from https://bitbucket.org/ritt/elog, as |
|
|
68843
|
Wed Sep 12 15:57:31 2018 |
| Allen Tuttle | AllenEmail@wavecable.com | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source | A quick test suggests I can't just
replace sprintf with snprintf.
Original error: |
|
|
68842
|
Wed Sep 12 15:25:07 2018 |
| Allen Tuttle | AllenEmail@wavecable.com | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source | I would like to try the new code, I don't
see it on elog/download/tar/.
Do you keep updates elsewhere like |
|
|
Draft
|
Wed Sep 12 15:20:11 2018 |
| Allen Tuttle | AllenEmail@wavecable.com | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source | I don't see the update on elog/download/tar/.
Do you keep builds elsewhere, perhaps
on get or sourceforge? |
|
|
68840
|
Wed Sep 12 11:10:18 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source | This warning is triggered by the use of
the sprintf() funciton, which can write beyond
the boundary of the destination string. I |
|
|
68839
|
Tue Sep 11 19:46:40 2018 |
 | Allen Tuttle | AllenEmail@wavecable.com | Bug report | Linux | 3.1.3 | Compile issues on Fedora withe current elog source | Tried compiling on FC27 and 28, both result
in binaries but with serious issues; writing
data larger than then allowed. |
|
|
68838
|
Tue Aug 28 23:38:55 2018 |
| Andrew Wade | awade@caltech.edu | Question | Linux | Other | 3.1.2 | Re: Reverse proxy of Elog using Docker and Nginx? | It does indeed seem to be a cookie stripping
issue. I just need to figure out how
to get Nginx to forward these properly. |
|
|
68837
|
Mon Aug 27 13:07:28 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2 | Re: Entry size too large for email notification | That's how it is implemented. If you
use
|
|