Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 436 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  68025   Mon Jun 15 22:00:40 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.9.2Re: Limited access to an attribute

No.

Michael Cianci wrote:

Is there a way to limit access to an attribute "Reviewed by" to only supervisors?

Thank you for your help

Mike

 

  68543   Tue Jan 10 11:13:02 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.2Re: Limit number of characters for "login user" parameter string ?

There is a limit of 100 options per line, so you probably run against that. This is defined in elogd.h with MAX_N_LIST and MAX_N_ATTR. You can try to increase these and recompile, but at some point you will hit the stack size limit of your operating system and elogd will crash.

Christine Quicot wrote:

Hello all,

I use ELOG for about 30 users, and I've listed their email adresses in the "login user" parameter, using the LDAP authentication.
As I had problems with the users from the end of the list (they couldn't log in the logbooks) I guessed that there is a max length for the string "login user" (or other parameter?). it seems to be a 1000 character limit.
How can I parameter this limit to another value? Is this value used for other parameters?

Thanks for your answer.

 

  66746   Fri Mar 12 08:57:07 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.8.2282Re: Limit elog e-mail to only people involved with an entry

Paul Paquette wrote:

Can I limit an elog entry mails to only go to my e-mail, my supervisor and the person who is entering the elog entry.  I have the Elog server on Windows XP Pro running version 2.7.8.2282.

That should be possible with the following configuration options:

Suppress email to users = 1
Email all = <your e-mail>, <your supervisor e-mail>, $user_email 
  69723   Mon Jan 22 12:15:26 2024 Reply Stefan Rittstefan.ritt@psi.chQuestionAllV3.1.3-7933898Re: Let the user decide which columns should be displayed

There is a general display option "List display", but that applies for all users. For the download, you can load the CSV file into a spreadsheet program and then delete some columns.

Stefan

Sarah Kuckuk wrote:

Hello

I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).

Thanks a lot!

 

  67534   Tue Jun 4 17:09:44 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.9.2.2455Re: Latest windows version vs 2.9.2.2455

UlfO wrote:

 

What is the differences between E-log windows version 2.9.2-2455 like we run and E-log windows version 2.9.2.-2475 ?

I cant find a changelog for this.

Best regards
/UlfO

 

 https://savannah02.psi.ch/viewvc/meg_elog/trunk/src/elogd.c?view=log

  67535   Tue Jun 4 17:14:25 2013 Reply UlfOulf.olsson@dynamate.seQuestionWindows2.9.2.2455Re: Latest windows version vs 2.9.2.2455

Stefan Ritt wrote:

UlfO wrote:

 

What is the differences between E-log windows version 2.9.2-2455 like we run and E-log windows version 2.9.2.-2475 ?

I cant find a changelog for this.

Best regards
/UlfO

 

 https://savannah02.psi.ch/viewvc/meg_elog/trunk/src/elogd.c?view=log

 OK!

Thank you very much

/UlfO

 

 

  68947   Mon Apr 29 13:12:56 2019 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.2Re: Last default = <n>

Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.

So what you need is "Last default = 31" instead of 28 and it should work.

Stefan

Alan Grant wrote:

According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.

A couple other side questions which are related:

The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.

Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!

 

  68948   Mon Apr 29 17:48:13 2019 Reply Alan Grantagrant@winnipeg.caQuestionWindows3.1.2Re: Last default = <n>

I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default the display to Month, and also only search within the last month of entries.

Stefan Ritt wrote:

Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date", then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months", "Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last default = <n>" option you can only choose one of these seven options. Then this option is selected by default and the filter is applied accordingly. This lets you still change the date filter to a longer time period for example, but then with the penalty of longer search times.

So what you need is "Last default = 31" instead of 28 and it should work.

Stefan

Alan Grant wrote:

According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries, however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding, or implementing it wrong? We must restrict searches through QF to reduce load.

A couple other side questions which are related:

The doc on this setting says: "Last default = <n>
Some logbooks are very big ans searching through all entries with quick filter can be time consuming. This option sets a default value for the Date quick filter, so that by default only the <n> days are displayed." ...... I'm assuming that by saying "only the <n> days are displayed" that it has actually only searched <n> days ................ vs seaching ALL the logbooks but only displaying <n> days. Please confirm.

Also, why wouldn't the "28" days spec display in the Select Period box beside the Quick Filters? Otherwise it appears to me to be a separate and conflicting item. Best regards!

 

 

ELOG V3.1.5-3fb85fa6