Placeholders in Python API, posted by Florian Feldbauer on Wed Nov 25 15:10:34 2020
|
Hey all,
In the configuration of the Elog one can use
Preset Author = $long_name |
|
length of condition names, posted by Harry Martin on Wed Dec 2 22:45:16 2020
|
The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change
to that rule anywhere in the docs.
I have been using multi-character condition names successfully. I find these are easier to use since they can be more descriptive |
Re: Options <...> vs ROptions <...>, posted by Harry Martin on Thu Dec 3 01:51:49 2020
|
Same problem here, in version 3.1.3. It would be very nice if this worked.
Wolfgang
Bayer wrote:
According to section "Syntax of elogd.cfg" of the "Administrator's |
|
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: |