Different logbook files when running elogd as admin or normal user, posted by Antonio Bulgheroni on Thu Jul 21 07:44:04 2016
|
Dear all, I have a problem with my window elog installation (2.9.2) and I would like to ask your help for solving it.
I'm using elog on my lab computer for a single user installation, so something very simple. It was running smoothly for many months using
the automatic window service (i.e. elogd was started automatically at boot). I need to add that the service is started as the local administrator, while |
Re: Different logbook files when running elogd as admin or normal user, posted by Stefan Ritt on Thu Jul 21 08:08:07 2016
|
I don't know why elogd uses different logbook directories depending on the user. Maybe you start it in different directories, or one user cannot
read the config file and falls back to some default. Anyhow, you can start elogd interactively wit the -v flag which tells you which logbook files are
parsed. There are no cache files or similar, everything is stored in Yymmdda.log files, you just have to search for them. |
|
Re: Different logbook files when running elogd as admin or normal user, posted by Antonio Bulgheroni on Thu Jul 21 09:37:47 2016
|
So I found the my log files, but this issue should probably be documented.
When running as admin my logbook files are where they should (C:\Program Files (x86)\ELOG\logbooks)
When running as local user (with no admin rights), elogd has no writing access to the logbooks directory. So it falls back to use C:\Users\[MyUserName]\AppData\Local\VirtualStore\Program |
string length limit in url tag, posted by Don on Wed Jul 20 16:03:24 2016
|
What is the string length limit in url tag and how to increase it?
For example,
[url=http://example.com?<text_string>]click here[/url] |
|
Re: string length limit in url tag, posted by Andreas Luedeke on Thu Jul 21 06:15:44 2016
|
Several strings in ELOG are limited to 256 chars. It is likely the limit for URLs, too.
The magic number "256" appears 285
times in the elogd.c file.
It is probaly easier if you compress long URLs with goo.gl
Cheers, Andreas
Don wrote:
|
|
Escape character [ or ] doesn't work within [url], posted by Don on Fri Jul 15 19:46:26 2016
|
Here is the problem:
[url=http://example.com?arrays[]=v1&arrays[]=v2]click here[/url]
How can I escape [] inside url tag? |
Re: Escape character [ or ] doesn't work within [url], posted by Andreas Luedeke on Mon Jul 18 23:37:22 2016
|
The URL encoding of ']' as '%5D' appears to work:
[url=http://example.com?arrays[%5D=v1&arrays[%5D=v2]click here[/url]
Cheers, Andreas |
|
Re: Escape character [ or ] doesn't work within [url], posted by Don on Tue Jul 19 21:08:08 2016
|
Andreas
Luedeke wrote:
The URL encoding of ']' as '%5D' appears to work: |
Email report has incorrect pictures, posted by Austin Reid on Tue Jul 12 21:23:13 2016 
|
My group uses the precompiled Debian binary, and I use ELCode to format my log reports. (I've found it to be the easiest way to generate inline images)
Yesterday, I submitted an entry that renders correctly on the elog itself, but the email report that was sent to my collaborators was quite confusing, |
|
Using Reply option, posted by Jason S on Tue Jul 12 16:18:46 2016
|
Forgive me I'm not incredibly Elog savy yet.
A little backround about this log book - I have our log set up as individual user names. The log book is designed for entrys to be
made when a process shutdown needs to be bypassed. The operator will create an entry and submit it. Then a supervisor will come in after |
|
Re: Using Reply option, posted by Andreas Luedeke on Tue Jul 12 19:39:04 2016
|
Preset on reply Author = $long_name
Cheers, Andreas
Jason |
|
Re: Using Reply option, posted by Jason S on Tue Jul 12 20:53:03 2016
|
Works Great. Thanks Andreas
Andreas Luedeke wrote:
Preset on reply Author |
|
Multiple outcomes to a conditional attribute, posted by Sofian Jafar on Tue Jul 12 08:06:36 2016
|
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron |
|
Re: Multiple outcomes to a conditional attribute, posted by Andreas Luedeke on Tue Jul 12 08:31:37 2016
|
Hi Sofian,
it should work like this:
Options Type = Fault{1}, Test{2}, Report{3} |
|
Re: Multiple outcomes to a conditional attribute, posted by Sofian Jafar on Tue Jul 12 09:15:35 2016
|
Thanks Andreas,
Works great.
I tried reading the documentation on this but I was not able to deduce this solution. |
|
Re: Multiple outcomes to a conditional attribute, posted by Stefan Ritt on Tue Jul 12 08:37:42 2016
|
What about this:
Options Type = Fault{1}, Test{2}, Report{3}
{1} Options Fault Status = Open{a}, Fixed{b} |
|
More than 100 attributes , posted by JD on Wed Jun 29 16:07:32 2016
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options"
line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual. |
|
Re: More than 100 attributes , posted by Stefan Ritt on Wed Jun 29 16:58:15 2016
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically |
|
Re: More than 100 attributes , posted by JD on Thu Jun 30 14:00:43 2016
|
Thank you Stefan, I think then I will leave it at the default value. I need a stable Systen
Stefan
Ritt wrote:
The limit is in the variable |
|
Unable to set a custom logbook dir on Debian 8 from the repository package, posted by S. Caiazza on Tue May 31 20:03:53 2016
|
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel |
|
Re: Unable to set a custom logbook dir on Debian 8 from the repository package, posted by Stefan Ritt on Mon Jun 27 16:06:55 2016
|
The debian version of elog is pretty old with quite a number of bugs fixed in meantime. Unfortunatlely the debig packase has not bee updated by the maintainers.
So better download the current version from bitbucket and compile elogd yourself.
S. |