Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 213 of 796  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6363 Entries 
Goto page Previous  1, 2, 3 ... 212, 213, 214 ... 794, 795, 796   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  68614   Thu Apr 27 22:21:03 2017 Question Alan Grantagrant@winnipeg.caQuestionWindows3.1.2Limiting search data

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

  68615   Fri Apr 28 08:15:56 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.2Re: Limiting search data

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

  68616   Fri Apr 28 11:59:30 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.2Re: Limiting search data

I think I understand the question (although I have no answer):

When someone uses the "Find" page search, then there is an option to limit the search to e.g. the last year. If you search for a non existing string, it'll only search entries from the past year.

If people are instead using the quickfilter to search for the same non existing string, then all entries of all past years are searched for the string.

In both cases the result page will be empty, so "Entries per page" does not change anything. But in the second case the search might need an order of magnitude longer.

Stefan Ritt wrote:

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

 

  68617   Fri Apr 28 12:33:55 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.2Re: Limiting search data

Ok, got it. Will put it on the to-do list.

Andreas Luedeke wrote:

I think I understand the question (although I have no answer):

When someone uses the "Find" page search, then there is an option to limit the search to e.g. the last year. If you search for a non existing string, it'll only search entries from the past year.

If people are instead using the quickfilter to search for the same non existing string, then all entries of all past years are searched for the string.

In both cases the result page will be empty, so "Entries per page" does not change anything. But in the second case the search might need an order of magnitude longer.

Stefan Ritt wrote:

I don't get your point. If you go on the list page of this forum, you see -- all entries -- in the period quick filter, but you only see one page of entries, which is rather quick. This can be changed wiht "Entries per page", which defaults to 20. Do you have a different set-up?

Alan Grant wrote:

I'm aware there is the "Show Last Default" setting for the Find page but is there (or can there PLEASE be) a similar setting for the Period filter on the List page? Our users routinely use the Quick Filters instead and it bogs down the system because we have lots of logbooks. Many thanks.

 

 

 

  68630   Mon Jun 19 07:48:49 2017 Question Niklas Hoglundniklas@hoglund.pp.seQuestionWindows3.1.3Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?

Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?

Example:

toc()

< h1>test
< h2>test1
< h1>test2
< h2>test3
< h1>test4
< h2>test5

Results in:

1. test
1.1 test1
2. test2
2.1 test3
3. test4
3.1 test5

...the text...
  68631   Mon Jun 19 08:33:07 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.3Re: Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?

This is not possible.

Stefan

Niklas Hoglund wrote:

Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?

Example:

toc()

< h1>test
< h2>test1
< h1>test2
< h2>test3
< h1>test4
< h2>test5

Results in:

1. test
1.1 test1
2. test2
2.1 test3
3. test4
3.1 test5

...the text...

 

  68632   Tue Jun 20 14:32:29 2017 Disagree Niklas Hoglundniklas@hoglund.pp.seBug reportWindows3.1.3my elogd crashes when editing the configuration
Hi, 
my elogd crashes sometimes when I click on the "Change config" button. What info should I collect more than below/attached?

In windows EventViewer I see this printouts:

###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" /> 
  <EventID Qualifiers="0">1001</EventID> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:25:30.000000000Z" /> 
  <EventRecordID>28059</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>108889037262</Data> 
  <Data>1</Data> 
  <Data>APPCRASH</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data /> 
  <Data /> 
  <Data>C:\Users\hognik\AppData\Local\Temp\WER9155.tmp.WERInternalMetadata.xml</Data> 
 
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_08bd38b0</Data>

  <Data /> 
  <Data>0</Data> 
  <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data>0</Data> 
  <Data>94c2d6a18797708666faf33a7273855a</Data> 
  </EventData>
  </Event>
###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:24:47.000000000Z" /> 
  <EventRecordID>28058</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data>1568</Data> 
  <Data>01d2e9c028b88983</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" /> 
  <EventID Qualifiers="0">1001</EventID> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:24:07.000000000Z" /> 
  <EventRecordID>28057</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>108889037262</Data> 
  <Data>1</Data> 
  <Data>APPCRASH</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data /> 
  <Data /> 
  <Data>C:\Users\hognik\AppData\Local\Temp\WERBE94.tmp.WERInternalMetadata.xml
C:\Users\hognik\AppData\Local\Temp\WERCA4D.tmp.appcompat.txt triagedump.dmp
C:\Users\hognik\AppData\Local\Temp\WERCB77.tmp.WERDataCollectionFailure.txt</Data> 
 
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_0a4ff4e6</Data>

  <Data /> 
  <Data>0</Data> 
  <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data>4104</Data> 
  <Data>94c2d6a18797708666faf33a7273855a</Data> 
  </EventData>
  </Event>

###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:23:53.000000000Z" /> 
  <EventRecordID>28056</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data>2338</Data> 
  <Data>01d2e9baf6174f0f</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>
###
Attachment 1: WindowsCrashFiles.zip
  Draft   Thu Jun 22 20:55:36 2017 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows3.1.3Re: my elogd crashes when editing the configuration
Might be some bad data in your elogd.cfg file. Have a look at that file with a text editor to see if there's anything wrong. Start with a pristine config file from the 

> Hi, 
> my elogd crashes sometimes when I click on the "Change config" button. What info should I collect more than below/attached?
> 
> In windows EventViewer I see this printouts:
> 
> ###
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
>   <Provider Name="Windows Error Reporting" /> 
>   <EventID Qualifiers="0">1001</EventID> 
>   <Level>4</Level> 
>   <Task>0</Task> 
>   <Keywords>0x80000000000000</Keywords> 
>   <TimeCreated SystemTime="2017-06-20T12:25:30.000000000Z" /> 
>   <EventRecordID>28059</EventRecordID> 
>   <Channel>Application</Channel> 
>   <Computer>NIKLAS</Computer> 
>   <Security /> 
>   </System>
> - <EventData>
>   <Data>108889037262</Data> 
>   <Data>1</Data> 
>   <Data>APPCRASH</Data> 
>   <Data>Not available</Data> 
>   <Data>0</Data> 
>   <Data>elogd.exe</Data> 
>   <Data>0.0.0.0</Data> 
>   <Data>58f9c864</Data> 
>   <Data>elogd.exe</Data> 
>   <Data>0.0.0.0</Data> 
>   <Data>58f9c864</Data> 
>   <Data>c0000005</Data> 
>   <Data>00064eea</Data> 
>   <Data /> 
>   <Data /> 
>   <Data>C:\Users\hognik\AppData\Local\Temp\WER9155.tmp.WERInternalMetadata.xml</Data> 
>  
> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_08bd38b0</Data>
> 
>   <Data /> 
>   <Data>0</Data> 
>   <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data> 
>   <Data>0</Data> 
>   <Data>94c2d6a18797708666faf33a7273855a</Data> 
>   </EventData>
>   </Event>
> ###
> 
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
>   <Provider Name="Application Error" /> 
>   <EventID Qualifiers="0">1000</EventID> 
>   <Level>2</Level> 
>   <Task>100</Task> 
>   <Keywords>0x80000000000000</Keywords> 
>   <TimeCreated SystemTime="2017-06-20T12:24:47.000000000Z" /> 
>   <EventRecordID>28058</EventRecordID> 
>   <Channel>Application</Channel> 
>   <Computer>NIKLAS</Computer> 
>   <Security /> 
>   </System>
> - <EventData>
>   <Data>elogd.exe</Data> 
>   <Data>0.0.0.0</Data> 
>   <Data>58f9c864</Data> 
>   <Data>elogd.exe</Data> 
>   <Data>0.0.0.0</Data> 
>   <Data>58f9c864</Data> 
>   <Data>c0000005</Data> 
>   <Data>00064eea</Data> 
>   <Data>1568</Data> 
>   <Data>01d2e9c028b88983</Data> 
>   <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
>   <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
>   <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data> 
>   <Data /> 
>   <Data /> 
>   </EventData>
>   </Event>
> 
> ###
> 
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
>   <Provider Name="Windows Error Reporting" /> 
>   <EventID Qualifiers="0">1001</EventID> 
>   <Level>4</Level> 
>   <Task>0</Task> 
>   <Keywords>0x80000000000000</Keywords> 
>   <TimeCreated SystemTime="2017-06-20T12:24:07.000000000Z" /> 
>   <EventRecordID>28057</EventRecordID> 
>   <Channel>Application</Channel> 
>   <Computer>NIKLAS</Computer> 
>   <Security /> 
>   </System>
> - <EventData>
>   <Data>108889037262</Data> 
>   <Data>1</Data> 
>   <Data>APPCRASH</Data> 
>   <Data>Not available</Data> 
>   <Data>0</Data> 
>   <Data>elogd.exe</Data> 
>   <Data>0.0.0.0</Data> 
>   <Data>58f9c864</Data> 
>   <Data>elogd.exe</Data> 
>   <Data>0.0.0.0</Data> 
>   <Data>58f9c864</Data> 
>   <Data>c0000005</Data> 
>   <Data>00064eea</Data> 
>   <Data /> 
>   <Data /> 
>   <Data>C:\Users\hognik\AppData\Local\Temp\WERBE94.tmp.WERInternalMetadata.xml
> C:\Users\hognik\AppData\Local\Temp\WERCA4D.tmp.appcompat.txt triagedump.dmp
> C:\Users\hognik\AppData\Local\Temp\WERCB77.tmp.WERDataCollectionFailure.txt</Data> 
>  
> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_0a4ff4e6</Data>
> 
>   <Data /> 
>   <Data>0</Data> 
>   <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data> 
>   <Data>4104</Data> 
>   <Data>94c2d6a18797708666faf33a7273855a</Data> 
>   </EventData>
>   </Event>
> 
> ###
> 
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
>   <Provider Name="Application Error" /> 
>   <EventID Qualifiers="0">1000</EventID> 
>   <Level>2</Level> 
>   <Task>100</Task> 
>   <Keywords>0x80000000000000</Keywords> 
>   <TimeCreated SystemTime="2017-06-20T12:23:53.000000000Z" /> 
>   <EventRecordID>28056</EventRecordID> 
>   <Channel>Application</Channel> 
>   <Computer>NIKLAS</Computer> 
>   <Security /> 
>   </System>
> - <EventData>
>   <Data>elogd.exe</Data> 
>   <Data>0.0.0.0</Data> 
>   <Data>58f9c864</Data> 
>   <Data>elogd.exe</Data> 
>   <Data>0.0.0.0</Data> 
>   <Data>58f9c864</Data> 
>   <Data>c0000005</Data> 
>   <Data>00064eea</Data> 
>   <Data>2338</Data> 
>   <Data>01d2e9baf6174f0f</Data> 
>   <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
>   <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
>   <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data> 
>   <Data /> 
>   <Data /> 
>   </EventData>
>   </Event>
> ###
Goto page Previous  1, 2, 3 ... 212, 213, 214 ... 794, 795, 796   Next  
ELOG V3.1.5-2eba886