Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 209 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded  Show all entries    6459 Entries 
Goto page Previous  1, 2, 3 ... 208, 209, 210 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject Text Attachments
  68840   Wed Sep 12 11:10:18 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceThis warning is triggered by the use of
the sprintf() funciton, which can write beyond
the boundary of the destination string. I		   
  Draft   Wed Sep 12 15:20:11 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceI don't see the update on elog/download/tar/.
Do you keep builds elsewhere, perhaps
on get or sourceforge?		   
  68842   Wed Sep 12 15:25:07 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceI would like to try the new code, I don't
see it on elog/download/tar/.
Do you keep updates elsewhere like		   
  68843   Wed Sep 12 15:57:31 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceA quick test suggests I can't just
replace sprintf with snprintf.
Original error:		   
  68844   Wed Sep 12 20:52:22 2018 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceStefan said "code is commited":
that means you can download the latest version
from https://bitbucket.org/ritt/elog, as		   
  68845   Thu Sep 13 06:12:59 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceLatest compile effort on Fedora 28 using
the bitbucket source downloaded at 21:12
PDT:		   
  68849   Fri Oct 19 08:38:06 2018 Question Sergio Navarretesergionavarrete+elog@gmail.comQuestionWindows3.1.3Logfile not registering entry numbers?I have configured a logbook with the logfile
on, but when a user replies to an entry
the line logged goes		   
  68850   Fri Oct 19 13:08:30 2018 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.3Re: Logfile not registering entry numbers?It looks like you've found a bug in
ELOG. I've checked my elog.log and see
that all NEW entry lines show "#0".		   
Goto page Previous  1, 2, 3 ... 208, 209, 210 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6