| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
Text |
 |
|
68825
|
Thu Jun 14 13:17:33 2018 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 3.1.3 | Re: number of entries in Login user list | Well, many arrays based on MAX_N_LIST are
created on the heap memory, and if you exceed
that, elogd simply crashes. There are compile |
|
|
68826
|
Thu Jun 14 13:20:26 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: edit templates from config page | > Dear all,
> I have some logbook which uses preset
text depending on some option values, and |
|
|
68827
|
Thu Jun 14 18:17:07 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.3 | Re: edit templates from config page | > Dear all,
> I have some logbook which uses preset
text depending on some option values, and |
|
|
68828
|
Thu Jun 14 19:17:41 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: edit templates from config page | As always, Andreas has clever ideas. Never
thought about this possibility.
|
|
|
68829
|
Fri Jul 13 19:14:21 2018 |
| Lars Martin | lmartin@triumf.ca | Question | Linux | 2.9.2 | Re: Entry size too large for email notification | Wouldn't it make sense for ELog (by
default) to still notify, but not send the
attachments by e-mail if the size limit is |
|
|
68830
|
Tue Aug 7 10:53:45 2018 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | elog-3.1.3 | Problem with eloglang.german_UTF8 | I had a problem with restarting ELOG since
about a year, and finally I found the culprit.
I just want to share it here, to prevent |
|
|
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
|
|
|
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. |
|