Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate v
|
> indeed, I'll try to move to ELOG V3.1.4-80633ba
>
> > My try on this server ->> see the subject
|
|
... subject erased ..., posted by Stefan Ritt on Thu Apr 16 11:03:03 2020
|
I found two potential memory leaks which I fixed in the git version, so you can try again.
Another possibility, which is actually preferred, is to limit the size of the subject filed to a reasonable number. You can do that with following option
|
|
... subject erased ..., posted by Stefano Lacaprara on Thu Apr 16 11:12:32 2020
|
> I found two potential memory leaks which I fixed in the git version, so you can try again.
Just tested, and it works! Many thanks for very quick patch!
|
"New User" option does not work when Authentication=Webserver, posted by Jan Just Keijser on Fri May 29 09:27:32 2020
|
Our setup uses "Authentication=Webserver" + no automatic user registration. Thus, logbook admins should add a user by clicking "Config"
and then "New user". However, no matter what they fill in in the "new user " dialog, as soon as they hit "Save" an error
pops up saying that their username (the admin one, not the new one) already exists. I found the following code: |
|
SSL does not work, posted by Hisataka YOSHIDA on Fri Jun 5 03:49:20 2020
|
Hello.
I installed the latest elog (3.1.4-2) in CentOS 7, and it is working well without SSL.
When I enalbled SSL option (SSL = 1) in the "elogd.cfg", and tried to start the elogd, the message below was shown and failed to run. |
|
Re: SSL does not work, posted by Stefan Ritt on Fri Jun 5 13:24:01 2020
|
When you compile elog from the soruces, you need the OpenSSL library to be installed. The CMake build process will then find it and include it in the
compile process. When you use the "make" build process, you have to make sure that SSL is enabled there:
USE_SSL = 1 |
|
Re: SSL does not work, posted by Hisataka YOSHIDA on Thu Jun 11 08:23:01 2020
|
Dear Stefan,
Thank you for your comment. I successfuly compiled the latest elog from source code, and now elogd could work with SSL.
In fact, I reported the case of installation with rpm file. Maybe, the latest elog rpm doesn't support SSL, I guess. |
|
bug in elog.spec, posted by Janusz Szuba on Mon Jul 6 19:09:48 2020
|
Hi,
in commit 1812e7c, specifying CFLAGS to make
command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, |
|