| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66965
|
Fri Dec 3 13:56:20 2010 |
 | Philipp W. | philipp.weinzierl@supranet.li | Question | Windows | 280-5 | How can Elog start automatically on Windows Server 2008 on startup ? | Hi all,
i have a question... How can i manage it that elog starts automatically on windows startup ? I always need to type "elogd -p 85" in the console that it starts ...
Can anyone help me ? =)
Thanks
SenoX |
|
68078
|
Wed Aug 12 16:59:30 2015 |
| Philip Leung | philip.leung@cern.ch | Question | Linux | Windows | 3.1.1 | Isolating search urls | 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 |
|
Draft
|
Thu Aug 13 10:05:22 2015 |
 | Philip Leung | philip.leung@cern.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | Thanks for the quick response!
The idea is to run multiple instances of elog where
| 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
|
|
|
|
68083
|
Thu Aug 13 10:06:23 2015 |
| Philip Leung | philip.leung@cern.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | 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
|
|
|
|
68088
|
Mon Aug 17 10:32:51 2015 |
| Philip Leung | philip.leung@cern.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | 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
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|