ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67457
|
Mon Feb 25 19:12:47 2013 |
| Francois Cukier | Monsieurdindon@gmail.com | Question | Windows | 2.9.2 | Search result background color |
Is it possible to change the "yellow" background color when running a search ? (I looked in the css, there is nothing...)
Couldn't find any syntax for elogd.cfg
Thanks for your help :) |
69189
|
Sun Aug 2 18:45:18 2020 |
| Illam Pakkirisamy | illam@senseeker.com | Question | Windows | ELOG V3.1.4-a04 | Search feature in ELOG |
Hi,
Is there a search feature in ELOG. Basically, we have the topics broken up by categories but within the categories we would like to search by a key word based on the subject to get to a specific topic.
Thanks.
Illam |
2154
|
Mon Mar 5 14:41:20 2007 |
| An Thai | thaithan@gmx.de | Question | Windows | 2.6.4.1801 | Search all logbooks as default |
Hello all,
do you know how I can default set the option "Search all logbooks" in the Find page selected/checked?
Best regards,
An |
67141
|
Tue Nov 1 14:04:50 2011 |
| Carl Shirey | carl.shirey@pwr.utc.com | Question | Linux | 2.7.2-3 | Search Option |
Is there a way to setup a search, to search several log books but not all the logs books at one time?
Thanks
Carl |
65961
|
Thu Sep 4 20:49:59 2008 |
| Alan Stone | alstone@fnal.gov | Request | Linux | V2.7.1-200 | Search Find Selected or List of Logbooks instead of all Logbooks. |
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 |
87
|
Tue Jul 30 17:33:24 2002 |
| mo | msheikh25@hotmail.com | Question | | | 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.
Thanks,
Mo |
68210
|
Mon Dec 14 04:42:04 2015 |
| Dawang | raymund.dawang@gmail.com | Request | Windows | Latest | Sample of actual elog Config with URL in SSL |
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 |
2021
|
Thu Oct 26 21:54:40 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | Other | 2.6.2-1714 | SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8) |
Stefan Ritt wrote: |
Steve Jones wrote: | There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but the the non-daemn mode also sets to nobody and works fine. |
The elogd program opens the port (which might be below 1024 and thus needs privileges), then either become daemon or not, then changes to the user and group specified in elogd.cfg. So this behaviour should be the same on both cases.
Steve Jones wrote: | I just compiled SVN1723 and tried the generic elogd.cfg -- of course *that works!*. Something in my complex config that causes elog to barf when it is attempting to fork the daemon process. |
That's a good starting point. Take your config file, strip one option after the other, and see which is the offending one. This helps us tracking down the problem.
Steve Jones wrote: | I have no idea what "/var/run/syslog_door" is. |
I have not either. But one thing which is different in the daemon mode that all output is redirected to the syslog facility via the function call redirect_to_syslog();. This routine was not written by myself so I don't know 100% what it's doing, just under Linux it works fine. Try to outcomment this function and try again. |
Steve Jones wrote: |
Ok, I've narrowed down the problem to a single attribute. I edited elogd_fancy.cfg as it ships with SVN1723 and found a real bug and an issue:
BUG: In the initial comment section of elogd_fancy.cfg the line # This [global] section contains settings common to all logbooks is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting with a comment char;
ISSUE: The option Logbook dir = causes an enormous amount of problems, and this may be limited to elog installs that exist in NFS space (as opposed to local disk). If the default is left alone elogd appears to work fine; Try and override and the fun begins. The previous attached traces show that once going into daemon mode none of the logbook dirs can be found nor indexed. The workaround is to use the default "logbooks" dir. Perhaps the routine that creates the default (if not found) should be the same as the one that creates the override (?).
I reproduced this behavior using the elogd_fancy.cfg that ships.
|
|