Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 292 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject Text Attachments
  68785   Sun Apr 15 08:03:21 2018 Agree Michael Kelseykelsey@slac.stanford.eduBug reportMac OSX3.1.3Re: "Slow script" problem posting/editing from Safari -- browser hangs, times outThank you for your suggestion, Stefan! 
The sysadmin who handles our e-Log server
implemented your suggestion earlier today
  
  68786   Mon Apr 16 08:19:16 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.3Re: "Slow script" problem posting/editing from Safari -- browser hangs, times outOk, I removed the code from the official
code now. 

A bit background: The "autosave"
  
  68932   Tue Apr 23 14:06:36 2019 Warning Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4elogd Service exited with abnormal code: 1Dear all.

I am running elog 

elogd
  
  68933   Tue Apr 23 14:26:51 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1This kind of behavior we typically see
if some elog entry is corrupt. After a few
hours you might access this corrupt entry
  
  68942   Thu Apr 25 11:16:06 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1Thanks for the prompt feedback.

a) I confirm that the problems
shows up also when running interactively
  
  68943   Thu Apr 25 11:27:21 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1What you recommend is enough. Just make
sure to compile elogd with the flags mentioned
before, and when you get the segment violation,
  
  68951   Tue Apr 30 12:47:46 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1I was finally able to catch the crash.

I paste below the info provided
by lldb..
  
  68952   Tue Apr 30 14:07:52 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1Actually it is a little bit more difficult
than that.

I have restarted elogd and got
  
ELOG V3.1.5-3fb85fa6