| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68096
|
Tue Aug 18 14:23:29 2015 |
 | Daniel Sajdyk | daniel.sajdyk@gmail.com | Question | Windows | ELOG V3.1.0-3c6 | Re: "Resolve host names" does not resolve host names | I'm sorry... it was my mistake. I put Resolve host names in logbook config instead global.
Regards Daniel.
| Stefan Ritt wrote: |
|
In elog I simplu use the function gethostbyaddr() to resolve the host name. If this does not work, the underlying OS does not know the hostname either. Probably you can test this with "nslookup a.b.c.d", to see any further error message.
| Daniel Sajdyk wrote: |
|
Hello
I use Resolve host names = 1 in my config file, but I still get IP instead domain name.
I use elog in internal network with my own DNS.
Any sugesstions ?
Regards
Daniel.
|
|
|
|
68095
|
Mon Aug 17 16:30:17 2015 |
| John Krautkramer | john.krautkramer@micrel.com | Question | Linux | 3.1.1 | Re: IE 11 - Text Edit Toolbar Not Working | The issue was IE Compatibility Mode. There were no websites in the list, but the "Display intranet sites in Compatibility View" was checked. Removing this fixed it.
Thanks for the help!
John
| Stefan Ritt wrote: |
|
Also make sure you don't have "Compatibility Mode" turned on in IE11.
See here for example: http://winaero.com/blog/how-to-enable-compatibility-view-in-internet-explorer-11-ie11/
| Andreas Luedeke wrote: |
|
This reply has been written with IE 11 using the embedded HTML editor of ELOG. Therefore it is obviously not a problem of ELOG 3.1.1 with IE 11.
It could be a problem with your ELOG installation or it could be a problem with you IE 11 configuration. Can you use the HTML editor of this forum with IE11? Did you install ELOG 3.1.1 on top of an existing ELOG installation?
There was a recent post in the forum about IE11 and the HTML editor in the Forum. Did you read it?
Cheers, Andreas
| John Krautkramer wrote: |
|
Hi,
I've been exploring elog. I find when using IE 11, the text editor formatting buttons don't work with HTML encoding selected. The entire toolbar is grayed out. It appears to work fine with Chrome. Any ideas or direction to look? elog v3.1.1 is running on RedHat EL5. I've tried the rpm installation, and source code compilation and installation with no change.
Any input would be greatly apriciated!
John
|
|
|
|
|
68094
|
Mon Aug 17 11:52:54 2015 |
| Philip Leung | philip.leung@cern.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | Noted. Thank you for your time
| Stefan Ritt wrote: |
|
No, no and again: no.
| Philip Leung wrote: |
|
Would there be a simple way to redirect all URLs BUT the ones which trigger searches?
| Stefan Ritt wrote: |
|
For any other filter you need "&<attribute>=", which of course requires the knowlede of all attributes. There is no other "standard" flag in the URL indicating a search.
| Philip Leung wrote: |
|
This only applies to searches which specify that they are searching through the message text though. It would not work for things like quick filter
| Stefan Ritt wrote: |
|
Look for "&subtext=" in the URL
| Philip Leung wrote: |
|
Is there no good way of differentiating search operations from others by URL?
| Philip Leung wrote: |
|
Thanks for the quick response!
It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.
The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.
| Stefan Ritt wrote: |
|
I guess the underlying problem is the long time these requests take and block other users.
I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.
| Philip Leung wrote: |
|
Hello all,
I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.
Does anybody have any suggestions?
Regards,
Philip
|
|
|
|
|
|
|
|
|
|
|
68093
|
Mon Aug 17 11:36:49 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | No, no and again: no.
| Philip Leung wrote: |
|
Would there be a simple way to redirect all URLs BUT the ones which trigger searches?
| Stefan Ritt wrote: |
|
For any other filter you need "&<attribute>=", which of course requires the knowlede of all attributes. There is no other "standard" flag in the URL indicating a search.
| Philip Leung wrote: |
|
This only applies to searches which specify that they are searching through the message text though. It would not work for things like quick filter
| Stefan Ritt wrote: |
|
Look for "&subtext=" in the URL
| Philip Leung wrote: |
|
Is there no good way of differentiating search operations from others by URL?
| Philip Leung wrote: |
|
Thanks for the quick response!
It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.
The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.
| Stefan Ritt wrote: |
|
I guess the underlying problem is the long time these requests take and block other users.
I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.
| Philip Leung wrote: |
|
Hello all,
I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.
Does anybody have any suggestions?
Regards,
Philip
|
|
|
|
|
|
|
|
|
|
68092
|
Mon Aug 17 11:28:08 2015 |
| Philip Leung | philip.leung@cern.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | Would there be a simple way to redirect all URLs BUT the ones which trigger searches?
| Stefan Ritt wrote: |
|
For any other filter you need "&<attribute>=", which of course requires the knowlede of all attributes. There is no other "standard" flag in the URL indicating a search.
| Philip Leung wrote: |
|
This only applies to searches which specify that they are searching through the message text though. It would not work for things like quick filter
| Stefan Ritt wrote: |
|
Look for "&subtext=" in the URL
| Philip Leung wrote: |
|
Is there no good way of differentiating search operations from others by URL?
| Philip Leung wrote: |
|
Thanks for the quick response!
It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.
The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.
| Stefan Ritt wrote: |
|
I guess the underlying problem is the long time these requests take and block other users.
I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.
| Philip Leung wrote: |
|
Hello all,
I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.
Does anybody have any suggestions?
Regards,
Philip
|
|
|
|
|
|
|
|
|
68091
|
Mon Aug 17 11:26:22 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | For any other filter you need "&<attribute>=", which of course requires the knowlede of all attributes. There is no other "standard" flag in the URL indicating a search.
| Philip Leung wrote: |
|
This only applies to searches which specify that they are searching through the message text though. It would not work for things like quick filter
| Stefan Ritt wrote: |
|
Look for "&subtext=" in the URL
| Philip Leung wrote: |
|
Is there no good way of differentiating search operations from others by URL?
| Philip Leung wrote: |
|
Thanks for the quick response!
It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.
The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.
| Stefan Ritt wrote: |
|
I guess the underlying problem is the long time these requests take and block other users.
I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.
| Philip Leung wrote: |
|
Hello all,
I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.
Does anybody have any suggestions?
Regards,
Philip
|
|
|
|
|
|
|
|
68090
|
Mon Aug 17 11:17:37 2015 |
| Philip Leung | philip.leung@cern.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | This only applies to searches which specify that they are searching through the message text though. It would not work for things like quick filter
| Stefan Ritt wrote: |
|
Look for "&subtext=" in the URL
| Philip Leung wrote: |
|
Is there no good way of differentiating search operations from others by URL?
| Philip Leung wrote: |
|
Thanks for the quick response!
It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.
The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.
| Stefan Ritt wrote: |
|
I guess the underlying problem is the long time these requests take and block other users.
I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.
| Philip Leung wrote: |
|
Hello all,
I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.
Does anybody have any suggestions?
Regards,
Philip
|
|
|
|
|
|
|
68089
|
Mon Aug 17 10:41:22 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | Look for "&subtext=" in the URL
| Philip Leung wrote: |
|
Is there no good way of differentiating search operations from others by URL?
| Philip Leung wrote: |
|
Thanks for the quick response!
It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.
The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.
| Stefan Ritt wrote: |
|
I guess the underlying problem is the long time these requests take and block other users.
I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.
| Philip Leung wrote: |
|
Hello all,
I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.
Does anybody have any suggestions?
Regards,
Philip
|
|
|
|
|
|