Re: Too many open files - issue?, posted by Stefan Ritt on Mon Oct 25 13:34:06 2021
|
The code segements you show are from the command line tool elog.c, not the server elogd.c. The tool is called to submit a new message from the command
line. Even if there would be a file not properly closed, it will be closed by the operating system once the program finishes. So no problem of too many
open files there. |
|
Re: results of security scan, posted by Stefan Ritt on Tue Nov 2 12:07:46 2021
|
The elgod.c progarm itself is rather weak in SSL, since I just don't have time to catch up with the latest SSL enhancements. The safest you can do
is to put an industry-strenth web server like Apache in front of elogd and let that server handle the SSL layer.
Stefan |
|
Re: Display edit time, posted by Stefan Ritt on Wed Nov 24 08:38:33 2021
|
Creat an attribute "last edit" and set it to the last edit time. Something like this:
Attributes = ...., Last edit
Preset Last edit = $date |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 1 13:05:14 2021
|
Please issue the elog command with an added "-v" flag and post the output here.
Stefan
Jose |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 14:46:16 2021
|
If you use HTTPS, you have to connect to port 443 of your server, using the "-p" option.
Furthermore, you run under an Apache server, right? How do you do the redirecting to elogd? I guess you specified a subdir in the URL named /LogBook
to redirect to elogd. The you use another part of the URL to select the logbook, which again might be "LogBook". Is that correct? So your full |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 17:50:37 2021
|
The reply from the server
Response received:
HTTP/1.1 404 Not Found |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 8 10:59:58 2021
|
Ok, you Apache listes on two ports. On port 80 with HTTP and on port 443 with HTTPS. If you connect to port 80, there is no fowarding to elogd, that's
why Apach complains
The requested URL /LogBook/ was not found on this server. |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 8 13:19:55 2021
|
That reply indicates that the login was not successful. So something went wrong with the authentication. You can try to switch off passwords to see if
that makes a difference.
Jose |