ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68800
|
Tue May 15 10:35:32 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.2 | Re: about shiftcheck | An attribute is similar to a variable. Do you know any programming language that allows to start a variable with a digit? I don't.
The solution is very obvious: start your attributes with a letter.
Cheers, Andreas
Xuan Wu wrote: |
Hi all,
I try to implement a shift check list for our facility. The attributes called "a1, a2, b1, b2 etc" are used in original shiftcheck.html, However, we would like to use "1.1, 1.2, 2.1, 2.2 etc". So I try to change the name of checkbox in shiftcheck.html and the attributes in elogd.cfg file to "1.1, 1.2, 2.1, 2.2 etc". The elog web page can display the attributes like "1.1, 1.2...", but the checked value of "on" seems not working. And I have used wirshark to monitor the http package, the request message seems correct, but the service response seems can't deal with attributes like "1.1, 1.2...", so is there a way to work around?
|
|
68810
|
Wed May 23 16:19:48 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2+2014.05.1 | Re: Report Generating Tool? | Here's a little example for a query for this logbook:
curl -f -s -k "https://elog.psi.ch/elogs/Forum/?jcmd=Search&mode=CSV1&last=7&Category=^Question%24"
You can easily process this output with perl, to create reports. I use it for example to create counts for specific enties, like "Bug reports" that are not "closed", and show the results in some other user interfaces.
Cheers, Andreas
Stefan Ritt wrote: |
Switch to the "summary" display (try it with this forum). You get headers (like "category"). Clicking on it sorts by that attribute. Then display "all" entries, or use the "find" option to search in certain time periods, then just print the web page.
Alternatively, expeort logbook entries as CSV files, load them into a spreadsheet program, and do the sorting and printing there.
Stefan
Hal Goldfarb wrote: |
Has anyone developed a report tool for elog? I would like to be able to sort certain items and send them to either a printer, or an email (external to my own use).
If not, any ideas on an easy means of doing this? I write a lot of Perl, so that would be an option for me if the text is easily obtained.
Thanks
|
|
|
68822
|
Thu Jun 14 12:37:22 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Linux | 3.1.3 | Re: number of entries in Login user list | Hi Janusz,
You can change the following line in elogd.h and recompile:
#define MAX_N_LIST 100
That'll change the login user list limit. But it'll change other list length as well - which should not do harm unless you are very short of memory.
I don't see the Admin user list limit of 10 - aparently that is hard coded somewhere deep within (or I've just missed it).
Cheers, Andreas
Janusz Szuba wrote: |
Hi,
could it be possible to increase the limit of entries in Login user list from 100 to somewhat reasonably higher? Like twice or 3 times as much. Similar limit exist also on Admin user list, which is afair 10, could this also be increased?
best
Janusz
|
|
68827
|
Thu Jun 14 18:17:07 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.3 | Re: edit templates from config page | > Dear all,
> I have some logbook which uses preset text depending on some option values, and uses text files for this.
>
> something similar to:
>
> Options Type = Start of shift{1}, 2h{2}, 4h{3}, 6h{4}, End of shift {5}
>
> {1} Preset text = MCProdStart.txt
> {2} Preset text = MCProd2h.txt
> {3} Preset text = MCProd4h.txt
> {4} Preset text = MCProd6h.txt
> {5} Preset text = MCProdEnd.txt
>
> I wonder if there is a way to change/edit the text files from the web interface if you are admin of that logbook, or if the only way is to change the files directly in the elog server.
>
> thanks Stefano
Hi Stefano,
it is not directly foreseen in the web functionality of ELOG, but it can be done like this:
You could have a second logbook that has the content of these files each in one logbook entry.
You call a script "Execute edit =" that runs on the server and converts the specific ELOG entry into a file on the server.
Of course this is a security vulnerability, but you can confine the possibilities of the script.
E.g. to a hard-coded list of ELOG entries and files in a specific directory.
Still, someone could place a file on the server and then calls that file with an "Execute edit=" himself.
But if you do all this within a protected network that should be okay.
I do like the idea, thank you for the question! If you manage to do it please post it under Contributions :-)
Cheers, Andreas |
68830
|
Tue Aug 7 10:53:45 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | elog-3.1.3 | Problem with eloglang.german_UTF8 | I had a problem with restarting ELOG since about a year, and finally I found the culprit. I just want to share it here, to prevent anyone else to make the same mistake,
Apparently the files resources/eloglang.* are rather sensitive to the syntax. But it doesn't tell you: no warning or error message comes up.
The file eloglang.german_UTF8 contains some "missing translations" at the end - and it looks like they produce some problems.
If you don't follow the instructions to create eloglang.german_UTF8 from eloglang.german, but use the file as it is, then the language handling will be corrupted:
some (very few) language strings will point into some void and display garbage strings.
In very rare cases this will even crash "elogd", in all other cases it will confuse your users.
Sometimes ELOG commands like "?Cmd=New" were affected, which makes ELOG unusable.
What made it very hard to debug was the fact that with every restart a different string was affected.
Everything looked fine, and later you see a string in the configuration page is wrong. Restarting fixed that string, but then some other string is gone.
So if you see such a behaviour, check your language file for "unusual syntax".
I haven't checked if the problem is limited to UTF8 - I only saw the problem with the eloglang.german_UTF8 file.
Cheers, Andreas |
68844
|
Wed Sep 12 20:52:22 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source | Stefan said "code is commited": that means you can download the latest version from https://bitbucket.org/ritt/elog, as described in https://elog.psi.ch/elog/download.html, and then compile it. Clear now?
Stefan Ritt wrote: |
This warning is triggered by the use of the sprintf() funciton, which can write beyond the boundary of the destination string. I replaced it by snprintf(), which should make the compiler happy. Code is committed. Unfortuantely I have no FC27 here, so if there is still some waring with the current code, please post the full warning list here.
Stefan
|
|
68850
|
Fri Oct 19 13:08:30 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.3 | Re: Logfile not registering entry numbers? | It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving drafts and editing entries. I'll discuss with Stefan if that should be fixed.
Andreas
Sergio Navarrete wrote: |
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply?
|
|
68859
|
Tue Nov 27 08:19:11 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | 3.1.2 | Re: Need to change port 25 | This is nicely explained in the documentation: https://elog.psi.ch/elog/config.html#global
The following options are specific to the [global] section:
Port = <port>
Specifies the TCP port under which the server is listening. Default is 80. Can be superseeded via the '-p' command line flag.
Yanick Vachon wrote: |
Hi,
We've made changes in our network and now we have to use port 587 instead of port 25, how can i edit that parameter?
Thanks
|
|
|