ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65962
|
Fri Sep 5 10:21:45 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | V2.7.1-200 | Re: Search Find Selected or List of Logbooks instead of all Logbooks. |
Alan Stone wrote: |
I am using the CMS ELog remotely as a monitoring tool. Information is compartementalized into dozens of containers. I can create a find query URL, say last day, which then reloads every X minutes in Firefox. When new ELog entries are made, then appear in the refresh and catch my attention. But, my interests are somewhere between a single logbook and all logbooks. If I choose all CMS logbooks for example for one day, I usually end up with > 200 entries.
In short, I would like the ability to:
1) Select from the list of available logbooks when doing a search
2) Have more canned choices from smaller time frames, such as 1 hour or at least one shift (8 hours).
I do not see how to do this in the current elogd.cfg syntax instructions.
Thanks, Alan
|
First of all have you considered using the built in RSS feed? With an RSS reader new entries are shown in a local notification box similar to new email. Some people like it.
1) This is not directly possible, but there is a trick: Define a URL to each logbook and put it into the Bookmarks Toolbar of Firefox. If you have many logbooks, this will however clutter up your toolbar. Then I recommend to make a subfolder in the toolbar and put them into it. Now firefox has the neat feature that if you click with the right mouse button on the folder, it offers you "Open All in Tabs". If you select this, you get a tab for each logbook in fireforx, and you can browse through each logbook individually.
2) This function was there long time ago (since I needed it myself) but somehow vanished. I added it back in revision 2126. You can now craft an URL like
https://midas.psi.ch/elogs/Forum/past-8
to show the last 8 hours. |
88
|
Tue Jul 30 17:54:53 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | | | Re: Scroll box for attributes | > Hello,
> If you have the text box turned off so you only enter attributes, is it
> possible to have a couple of attributes that have small scroll through text
> boxs of a couple of lines rather than just one line? Like not as big as
> the regular text box but something small to be able to post a couple of
> lines in and if it gets bigger then you scroll down. For instance if you
> are posting a problem and a solution just have one small text box for the
> problem and one for the solution.
Having multi-line attributes would be pretty difficult since it would break
the way the database works (one attribute at a line). So for now, you have to
use the text box and the reply functionality to deal with problems and fixes
(like for this entry). |
68211
|
Wed Dec 16 09:56:09 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
68373
|
Thu Aug 4 16:40:14 2016 |
| Chris Smyth | chris.smyth@comcast.net | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote: |
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
68374
|
Thu Aug 4 21:53:37 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
|
how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote: |
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
68375
|
Tue Aug 9 04:23:07 2016 |
| Chris Smyth | chris.smyth@comcast.net | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
Andreas Luedeke wrote: |
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
|
how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote: |
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
68377
|
Tue Aug 9 14:01:04 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | You need to download the source file package of ELOG and compile it. If you don't know what a Makefile is, then it is likely futile for you to attempt to compile ELOG.
Or in other words: you cannot use SSL.
Chris Smyth wrote: |
By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
Andreas Luedeke wrote: |
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
|
how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote: |
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
|
68378
|
Tue Aug 9 14:08:20 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | You've already named your solution: drop the very old ELOG version and download the new one. Obviously it was compiled with USE_SSL and you can use it right away.
Since you probably don't even have the source files of the old version, you'll have no chance to make it work with that. Just use ELOG 3.1.0.
Chris Smyth wrote: |
By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
Andreas Luedeke wrote: |
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
|
how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote: |
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
|
|