Re: length of condition names, posted by Stefan Ritt on Thu Dec 3 09:57:20 2020
|
You can easily use multi-character conditionals, up to 256 chars.
Harry
Martin wrote:
The documentation describing the use of conditionals uses a single |
|
Re: Options <...> vs ROptions <...>, posted by Stefan Ritt on Thu Dec 3 09:58:44 2020
|
For conditional attributes, you have to use Options, not ROptions. Maybe I will implement that one day, but only if I will have plenty of time...
Harry
Martin wrote:
Same problem here, in version 3.1.3. It would be very |
|
Re: length of condition names, posted by Harry Martin on Fri Dec 4 02:03:56 2020
|
Could we update the doc for this?
Stefan
Ritt wrote:
You can easily use multi-character conditionals, up to 256 chars. |
outdated debian package, posted by Chris Körner on Fri Dec 18 18:08:54 2020
|
Hi everyone,
I am currently trying to setup elog as a docker container. I wonder if there is any reason why the elog debian package is stuck at version 3.1.3?
Would it be possible to update it to the latest version? |
Re: Path disclosure on unfound file, posted by prinnydood on Thu Dec 31 18:35:19 2020 
|
I can confirm this issue exists on version 3.1.3, which I have installed elog on Debian 10.
The issue also exists on version 3.14 (1.20190113git283534d97d5a.el7), which I tested on an AmazonLinux EC2 instance.
This is what I found: |
|
Re: Path disclosure on unfound file, posted by Stefan Ritt on Fri Jan 8 13:47:14 2021
|
Ok, I fixed the code in the current commit (395e101add19f0fe8a11a25d0822e511f34d94d1). The path gets stripped, and we see a
prinnydood |
|
elog slowness, posted by Giuseppe Cucinotta on Thu Jan 14 11:43:00 2021
|
We run elog on a server to provide a logbook for our laboratory. We noticed that elog is very slow on loading pages: browser pages spend a lot of
time in charging (actually one can speed the procedure refreshing the page but it is quite annoying).
I checked the server load with top and it doesn't show any abnormal CPU or memory usage. Then I ran lsof and I noticed that there are |
|
Re: elog slowness, posted by Stefan Ritt on Thu Jan 14 14:05:19 2021
|
Have you tried to restart the elogd server? The CLOSE_WAIT could be dangling network connections, which were not properly closed by the browser.
Giuseppe
Cucinotta wrote:
We run elog on a server to provide a logbook for our laboratory. |