Real-time mirroring?, posted by Frank Baptista on Mon Apr 26 15:40:36 2021
|
Hello!
We have a number of local ELOG servers, all mirrored to a single "remote" ELOG server. We have users that create updates at the |
Re: Real-time mirroring?, posted by Sebastian Schenk on Mon Apr 26 16:41:50 2021
|
Hello Frank,
It seems, you are using the mirror function of elog. It should resolve conflicts by itself acording to the documented rules. (https://elog.psi.ch/elog/config.html)
As I don't use this function, I can't say how good it works. |
|
Re: Real-time mirroring?, posted by Frank Baptista on Fri Apr 30 20:29:45 2021
|
Hi Sebatian,
Thank you for taking the time to answer...very much appreciated!
|
|
Re: Real-time mirroring?, posted by Sebastian Schenk on Fri Apr 30 21:13:39 2021
|
Hi Frank,
I am not sure, if I understood your setup correctly. But in my eyes, you don't need the local elog servers. The only difference for
the users at the chambers would be to directly use the 'mirror' remote elog url instead of the local elog url in their browsers. "which |
|
Re: Real-time mirroring?, posted by Frank Baptista on Fri Apr 30 21:55:23 2021
|
Hi Sebastian,
You're absolutely correct that the users at the chambers could directly use the remote ELOG server (without having a local server),
and I did originally think about this. Unfortunately, there are times that our network "goes down" (for maintenance and other issues), |
[Bug?] Admin restrict edit time, posted by Faith on Fri Apr 30 07:27:31 2021
|
I would like to know, if the command "Admin restrict edit time = " does really work as intended.
In my case I have the following global configuration:
Admin user = <me> |
|
segfault in auth.c:366, posted by gary holman on Fri Apr 23 04:59:58 2021
|
Elog version: ELOG V3.1.4-611489ba
I am running openldap on the localhost. For some reason now, elogd is segfaulting when (I believe) when a new user is being added to the
password file. For example: |
|
Re: segfault in auth.c:366, posted by Sebastian Schenk on Fri Apr 23 15:46:39 2021
|
Hi Mr. Holman,
The problem you are facing is more likely the issue, that the LDAP method is only provided as-is from a different developer.
I had a similar issue with the LDAP of my university. |
|
Re: segfault in auth.c:366, posted by Stefan Ritt on Fri Apr 23 16:21:05 2021
|
Well, if you find a solution with works for everybody, I'm happy to commit it to the main repository. But unfortunately I cannot test it because
I don't have LDAP here, so I'm flying blind.
Stefan |
|
Re: segfault in auth.c:366, posted by Laurent Jean-Rigaud on Sun Apr 25 15:17:27 2021
|
Hi,
Maybe it could be useful to add new parameters in elogd.cfg to define the attribute name to use to retrieve the given name, login name and email
from LDAP server. |
|
Re: segfault in auth.c:366, posted by gary holman on Wed Apr 28 04:01:49 2021
|
Dear Mr Ritt, Mr Schenk,
Thank you for the responses. This was indeed my issue and direction to fix the crash.
Thank you, |
|
How to make personal ELOG to public, posted by Hien Doan on Tue Mar 30 12:56:48 2021
|
Dear experts,
I am trying to use ELOG for my projects which we want to record every daily activities.
|
|
Re: How to make personal ELOG to public, posted by Sebastian Schenk on Tue Mar 30 18:08:37 2021
|
Dear Hien,
your problem is more general the question, how to get the elog to the network.
|
|
Re: How to make personal ELOG to public, posted by Hien Doan on Thu Apr 8 06:25:58 2021
|
Dear Sebastian,
Thank you very much for the instruction.
|
|
Re: How to make personal ELOG to public, posted by Frank Baptista on Mon Apr 26 16:14:49 2021
|
Hello Hien,
If you are sharing ELOG with users on the same network, here's something you can try. First, on the machine running ELOG, you need
to find the "Computer name". To do this, locate "This PC", and right click it to get to "Properties" in |
, posted by Vinzenz Bildstein on Fri Apr 23 18:53:16 2021
|
| |
auto pre-fill fields issue, posted by Gys Wuyts on Fri Apr 9 16:48:54 2021
|
Hello,
what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:
Subst Author = $long_name from $remote_host |
|
Re: auto pre-fill fields issue, posted by Stefan Ritt on Fri Apr 9 17:54:42 2021
|
You need user-level access control, using
Password file = ...
Stefan |
|
Re: auto pre-fill fields issue, posted by Gys Wuyts on Sat Apr 10 20:58:35 2021
|
Thank you but that is already in place. I have the same issue on both Windows 10 and Windows Server 2016 and 2019.
tnks
g |
|
Re: auto pre-fill fields issue, posted by Andreas Luedeke on Sun Apr 11 18:16:02 2021
|
If you would post a minimal config file where the problem occurs, then we could look what the problem is.
Gys
Wuyts wrote:
Thank you but that is already in place. I have the same issue |
|
Re: auto pre-fill fields issue, posted by Gys Wuyts on Mon Apr 12 13:32:53 2021
|
[global]
port = 8080
ssl = 0 |
|
Re: auto pre-fill fields issue, posted by Stefan Ritt on Mon Apr 12 13:57:18 2021
|
"Subst xxx" replaces after you submit an entry, while "Preset xxx" replaces before you create an
entry. I believe you want the second one.
Stefan |
|
Re: auto pre-fill fields issue, posted by Gys Wuyts on Mon Apr 12 14:17:52 2021
|
Super, overlooked that one. Works now
g |
|
Parsing log files, posted by Alan Grant on Fri Jan 8 05:48:45 2021
|
Sometimes we change the attributes in a config file for a given tab as time goes on, which naturally can get out of sync with the older data in
that tab.
I can imagine some other Elog users have encounterd this too at some point so I'm wondering if there's a utilty or some way |
|
Re: Parsing log files, posted by John on Fri Jan 8 06:14:49 2021
|
Hi Al; if I understand your situation correctly you want to access Elog db (logbooks) via another way. There are many ways depending on your knowledge,
type of work needed, and ease of use. I have found that accessing whatever I need via Elog gui is satisfactory in many situations-- by simply exporting.
THEN take the raw csv/xml file and manipulte it more easily from there. There are MANY free web sites that will take your data then, and put it in |
|
Re: Parsing log files, posted by Alan Grant on Fri Jan 8 15:28:06 2021
|
John
wrote:
Hi Al; if I understand your situation correctly you want to access Elog db |
|
Re: Parsing log files, posted by Stefan Ritt on Fri Jan 8 15:35:35 2021
|
Well, you could put the old options back to the config file, do the export, then remove them again.
But have a look at the Elog database files ZZMMDDa.log in your logbook directory, they are pure ASCII files, which are relatively simple to parse.
Hi |
|
Re: Parsing log files, posted by Lagarde on Wed Apr 7 17:11:28 2021
|
Hi,
I had similar needs (access and parse logs ) so I'm a small library in cpp. Have a look on https://github.com/flagarde/elogpp maybe
it could be usefull for you too. |
|
Pre-fill Attribute with last entry, posted by Dominic Schneider on Wed Mar 24 16:20:37 2021
|
Hi all together,
I struggle a lot with the following problem:
I try to prefill certain attributes with the value of exactly the same attribute in the last entry made in the same logbook. |
|
Re: Pre-fill Attribute with last entry, posted by Stefan Ritt on Wed Mar 24 16:25:36 2021
|
Nope, there is no way to acces the last value of an attribute. Sorry.
Stefan
Dominic |
|
Re: Pre-fill Attribute with last entry, posted by Sebastian Schenk on Wed Mar 24 17:36:15 2021
|
Sorry Stefan, but it is possible as you have the scripting ability.
The idea is to use "Preset Test_Attribute = $shell(script_to_get_the_last_entry)", where the script asks elog about the details and
parses them. |
|
Re: Pre-fill Attribute with last entry, posted by Dominic Schneider on Wed Mar 24 19:30:50 2021
|
Hi Stefan, hi Sebastian,
thank you for your help. Ok I see its not that simple.
Is there maybe a way of executing a Script on submitting, writing the values of the Attributes into an temporary file and loading the values |
|
Re: Pre-fill Attribute with last entry, posted by Stefan Ritt on Wed Mar 24 19:45:41 2021
|
That would actually be my recommendation. There is a "execute new" which you can call when submitting a new entry.
Stefan
Dominic |
|
Re: Pre-fill Attribute with last entry, posted by Dominic Schneider on Thu Mar 25 07:48:24 2021
|
Thank you very much.
So far I testet all functionalities and scripts to reach my goal. I will post a dummy of the solution later on for future purposes.
Best wishes |
|
Re: Pre-fill Attribute with last entry, posted by Sebastian Schenk on Thu Mar 25 12:50:08 2021
|
I am glad, we could help.
I can see a caveat in the recommendation.
By having "Execute New = echo $attrib > /path/last_attrib" and "Preset attrib = $shell(cat /path/last_attrib)" as the most |
|
Re: Pre-fill Attribute with last entry, posted by Richard Stamper on Tue Mar 30 13:43:46 2021
|
Just noting that, depending on what you want to achieve, you may be able to use the threading functionality so that a "new" entry is actually
a "reply" to a previous entry. This will allow you to populate attributes with values from that previous entry without having to rely on
storing information outside the system, with all the attendant concurrency risks already identified. |