Re: elog@Ubuntu 18.04, posted by Stefan Ritt on Mon Jan 31 09:10:41 2022
|
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 |
|
Re: elog@Ubuntu 18.04, posted by Carsten Winkler on Tue Feb 1 09:13:40 2022
|
sudo ldconfig didn't solve the problem
Is there any other solution than elog static linking? |
Default "Author" when replying to a log entry, posted by Jan Just Keijser on Tue Feb 1 15:39:38 2022
|
what is the default value for "Author" when replying to a log entry ? I now see that for each reply to a log entry, the value of "Author"
is set to the value of the author of the original entry - this makes it very hard to see which user has replied to a particular log entry, especially when
users start replying to replies etc. |
|
Re: Default "Author" when replying to a log entry, posted by Stefan Ritt on Tue Feb 1 15:43:00 2022
|
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
Jan |
|
Re: elog@Ubuntu 18.04, posted by Carsten Winkler on Tue Feb 1 16:16:34 2022
|
downloading the sources and building them on the target system solved the problem
Carsten
Winkler wrote:
sudo ldconfig |
|
Re: Default "Author" when replying to a log entry, posted by Jan Just Keijser on Tue Feb 1 16:43:34 2022
|
Excellent, exactly what I was looking for, many thanks!
Stefan |
Need help with permission, posted by Dan Witteman on Fri Sep 23 01:32:15 2022
|
Hello,
I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.
When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or |
Invalid Content-Length in header when running behind a load balancer, posted by Tamas Gal on Wed Jan 25 14:36:33 2023 
|
I am still struggling to get ELOG running behind a load balancer and hope to get some advice here. As already reported in https://elog.psi.ch/elogs/Forum/69542 I
observed an infinite loop of redirects when prompted to log in and using a non-empty password file. Without a password, the service worked as
expected. This was with version 3.1.3. |