Have you tried to connect directly to elogd and not going through Apache? 

ELog does not use the Log4j library so no issue there. If you run a web server like Apache in front of ELog, you however have to check if you use log4j there.

You can manually modify the CSS style to adjust column widths. Locate elog.css which resides under elog/themes/default/elog.css, then find the class “.listtitle”, and modify the line

width: 0%;

to something like

width: 10%;

you can play with the width until it suits your needs. After each change, you have to reload the page in the browser to see the effect.

If you only want to change the width of a specific column, add following lines to your elog.css:

.listtitle:nth-child(4) {
  width:30%;
}

where ‘4” is for example the 4th column. You can have several of these statements for different columns.

To hide the text, use the option 'summary lines' as described in the manual.
 

Looks like you don't have shared libraries correctly configured on your system. Try "ldconfig" on your system or link elogd statically (google how to do that).

Stefan

As you can see, on this forum the author for replies is correct. This is done via the config option:

Preset on reply Author = $long_name

> /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output 2 or more bytes (assuming 4097) into a 
> destination of size 4096

Yeah, I like those warnings "up to 4097 bytes written to a buffer of 4096 bytes". And it's even not a security issue, since the source of the data comes from elogd.cfg which only the owner can modify.

Basically this calls to rewrite elog completely with std::string. Maybe one day I retire and have some time for that...

Stefan

Can you try the "top groups" option, which means putting each logbook into a separate top group as described in the documentation. For us this works well, new users are only added to the right password file. There is however the problem that as admin you might be logged in to several logbooks (as remembered in your browser via cookies), so you might want to log out from all logbooks first (or clear all cookies of elog), then log in to one logbook and add the user there. In worst case you still can modify the password file by hand, they are plain ASCII files. Only the password has to be entered later since it's encrypted.

Stefan

Thanks for your patch, I committed it.

Stefan