Re: when using webserver authentication, how can I restrict the users that can edit any given elog?, posted by Christian Ospelkaus on Sun Jun 20 14:38:06 2021
|
Dear all,
I figured it out. Current global config is (using kerberos instead)
[global] |
Re: weird date bug, posted by Stefan Ritt on Tue Sep 24 17:05:43 2002
|
> i have a forum with one message. the forums is displayed with the search
mode set to threaded.
>
|
Re: weird date bug, posted by tony summerfelt on Tue Sep 24 17:24:38 2002
|
> I vaguely remember there was once a problem with that date. So can you please
> try again with a recent version of ELOG?
|
Re: view connecting account, posted by Andreas Luedeke on Mon Sep 14 17:25:08 2020
|
Yes, you can see that in the logging file, if you turn on logging. You might want to read the manual https://elog.psi.ch/elog/config.html. Here's
the relevant excerpt:
|
Re: view connecting account, posted by Lahreche Abdelmadjid on Tue Sep 15 12:31:09 2020
|
Thank you, I found it.
Andreas
Luedeke wrote:
Yes, you can see that in the logging file, if you turn on logging. |
Re: very long subject cause buffer overflow, posted by Stefano Lacaprara on Thu Apr 16 10:07:18 2020
|
Additional information: I tried to recompile with -g (debug) and run it in gdb but the crash is not reproduced that way (w/ or w/o gdb). I guess that the
memory handling in debug mode is different so the corruption is not
there anymore.
|
Re: very long subject cause buffer overflow, posted by Stefan Ritt on Thu Apr 16 10:11:13 2020
|
Can you try to reproduce it on this (!) server? I cannot reproduce it on my home copy server, so I guess that might be fixed in meantime. Can you update
to the current version of elog?
|
Re: v3.1.3 does not work with logbooks from v2.9.2? - solved, posted by Yves on Fri Feb 2 00:02:54 2018
|
Hi Andreas,
Thanks - you pointed me in the right direction. It appears that my logbooks were a combination of the two versions. I had all the year-directories
(version 3) but also all the entry files in the main logbook directory. Seems version 2 does not care but version 3 does not like it. After carefully checking |