Reuqest to extract X-Forwarded-Name and X-Forwarded-Email when using webserver, posted by Liam Gaffney on Sun Dec 8 22:00:32 2024
|
When using the Webserver authentication in combination with "File" and "Self register = 3", it is possible to keep track of registrations
and control access still. This is very useful, and upon clicking on the logbook for the first time, the user is asked to register by typing their username,
full name and email address. |
Re: Probleme TLS, posted by Olivier MARTIN on Mon Dec 9 10:23:32 2024
|
Thanks,
Does email notification from a Gmail address work? It is noted that port 465 must be used for SSL use? Is this correct :
|
|
Re: Probleme TLS, posted by Konstantin Olchanski on Mon Dec 9 21:55:53 2024
|
What Stefan meant to say is that Elog does not implement sending email using encrypted SMTP over TLS.
In theory it could be implemented, but if you try to use it, you may find that most
|
Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 18:45:49 2024 
|
I am receiving a segfault whenever I attempt to upload a file. Please see attached .txt for valgrind output. This occurs in version
elog-3.1.5-1. I reverted back to version elog-3.1.4-3 and the segfault does not occur.
Segfault occurs in Elog version: elog-3.1.5-1 |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 19:01:39 2024
|
Looks like duplicate report to https://elog.psi.ch/elogs/Forum/69826
gary
holman wrote:
I am receiving a segfault whenever I attempt to upload a file. |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 19:01:39 2024
|
Looks like duplicate report to https://elog.psi.ch/elogs/Forum/69826
gary
holman wrote:
I am receiving a segfault whenever I attempt to upload a file. |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Thu Dec 12 19:46:02 2024
|
A statement like "core dumped" does not help much. Same with valgrind memory leaks. I need a full strack trace with all parameters when the
segment violation occurs. The easiest is when you run elogd vom inside gdb, and once you get the signal, do a "where" to see th full stack trace.
As you can see from this forum, there is absolutely no crash when you upload any file, so it must have to do with your config file or anything |
|
Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 20:29:40 2024
|
Thanks for further instructions here is full stack trace:
Program received signal SIGABRT, Aborted. |