| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1745
|
Fri Mar 3 18:02:59 2006 |
 | Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1 | Allow $attributes in "Comment = " option |
| Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
|
1747
|
Sat Mar 4 06:04:53 2006 |
 | Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1 | Re: Top Groups and logbook directorys |
| Steve Jones wrote: | I am re-working our elog setup and am seriously looking at using the "Top Group" feature. What I like best is the ability to create [global] configurations for a group (or type) of logbook when I host multiple types on the same server. I also like being able to specify a different password file, etc.
A limitation that I run into is I would really like the actual directory names used for storing the logbooks for the different types to be identical - which isn't possible when all logbooks (regardless of context) exist at the same directory level. For example, I might have:
3 physical locations: ABC, DEF, GHI
For each location I want to maintain two *groups* of logbooks - CircuitTests and BoardTests. What I would like to end up with is:
- CircuitTests
----ABC
----DEF
----GHI
- BoardTests
----ABC
----DEF
----GHI
Under current elog this is not possble as far as I know. Since each logbook is a physical directory, each logbook requires a unique name. The concept of a named [global] area fills the bill for all things but it would be nifty if one could do:
[global circuittests]
Logbook dir = circuittestlogbooks
[global boardtests]
Logbook dir = boardtestlogbooks
I suppose the poorman's way of doing this is for each logbook to do the following:
[ABC]
Subdir = boardtestlogbooks/ABC
[DEF]
Subdir = boardtestlogbooks/DEF
[GHI]
Subdir = boardtestlogbooks/GHI
or something like that, but I was hopic for something a little more integrated - like creating the hierarchical stuff via the GUI. Anyway, this probably sounds like a major overhaul, which definitely wouldn't be worth it unless I have completely missed something glaringly obvious.
Thanks! |
| Steve Jones wrote: | | Perhaps it is best to ignore this -- I went for a workaround that I like. I am running into a few quirky things with Top Group but it is likely due to the fact that I have never used it. |
|
|
1749
|
Mon Mar 6 13:06:59 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | 2.6.1 | Re: Find in multiple logbooks returns wrong pages |
This problem has been fixed in SVN revision 1671. |
|
1750
|
Mon Mar 6 13:40:40 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.6.1 | Re: Allow $attributes in "Comment = " option |
| Steve Jones wrote: | | Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
The "Comment =" option for logbooks gives a general comment, like Discussion forum about ELOG for this forum. Since this comment is global, it does not make sense to have $attribute substitution. |
|
1754
|
Mon Mar 6 17:43:11 2006 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1 | Re: Allow $attributes in "Comment = " option |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
The "Comment =" option for logbooks gives a general comment, like Discussion forum about ELOG for this forum. Since this comment is global, it does not make sense to have $attribute substitution. |
| Quote: | | Ok, just a thought. Thanks |
|
|
1761
|
Tue Mar 7 21:41:28 2006 |
| Haitao Yu | htyu@phys.columbia.edu | Question | Linux | 2.6.1 | large attachment seems to hang elogd? |
Hello,
I am trying to attach somewhat large file (4-15MB files tested) with my messages but it seems to hang the elogd server for a really long time (30-100minutes). The file upload was done pretty soon (within a few seconds), then the elogd process seems to be busy doing something, using around 50MB of memory and 95% of CPU time, and stop respond to the requests. I can read the logbook with another copy of elogd running on another port, and I can see (and download) the uploaded file. I am wondering what could cause the problem --- and could it be related to the problem of not setting up the SMTP server right? Thanks for any suggestion!
Haitao
P.S. I read in some old message that if we want to upload very large files, we have to change the WEB_BUFFER_SIZE in elogd.c, however this parameter is no longer in v2.6.1. Is there something similiar I have to change? |
|
1767
|
Thu Mar 9 21:10:18 2006 |
| Edmundo T Rodriguez | edrodrig@chpnet.org | Question | Linux | 2.6.1 | Problem submitting entries in ELOG after migrating from Windows to Linux |
I was able to install ELOG v2.61. in a Compaq ProLiant DL360 running with SUSE Linux v10
The migration/implementation went quiet well ...
ELOG v2.6.1 application came up find!.
I can login with No problems.
I can see previous logs entries, sort, etc.
But, I can NOT create any new-log (new entries) in any logbook. I get this message:
-----------------------------------------------------------------------------------
New entry cannot be written to directory
"/eLOGv261/logbooks/Administration/"
Please check that it exists and elogd has write access and disk is not full
Please use your browser's back button to go back
-----------------------------------------------------------------------------------
The previous logbooks where in ...
\Program Files\ELOG\logbooks\Administration
\MainFrame
\Unix
\OpenVMS
\RDBMS
New logbooks are in the following place ...
/eLOGv261/logbooks/Administration
/MainFrame
/Unix
/OpenVMS
/RDBMS
How can it read old log entries and I NOT create new ones?
I am sure I missing something. Can I know what?
Also, It will be good to have an entry in the ELOG web-site
explaining any migration steps from Window to Linux and reverse!
Please, help.
Thank you! |
|
1768
|
Fri Mar 10 06:12:55 2006 |
| Steve Jones | steve.jones@freescale.com | Question | Linux | 2.6.1 | Re: Problem submitting entries in ELOG after migrating from Windows to Linux |
| Edmundo T Rodriguez wrote: | I was able to install ELOG v2.61. in a Compaq ProLiant DL360 running with SUSE Linux v10
The migration/implementation went quiet well ...
ELOG v2.6.1 application came up find!.
I can login with No problems.
I can see previous logs entries, sort, etc.
But, I can NOT create any new-log (new entries) in any logbook. I get this message:
-----------------------------------------------------------------------------------
New entry cannot be written to directory
"/eLOGv261/logbooks/Administration/"
Please check that it exists and elogd has write access and disk is not full
Please use your browser's back button to go back
-----------------------------------------------------------------------------------
The previous logbooks where in ...
\Program Files\ELOG\logbooks\Administration
\MainFrame
\Unix
\OpenVMS
\RDBMS
New logbooks are in the following place ...
/eLOGv261/logbooks/Administration
/MainFrame
/Unix
/OpenVMS
/RDBMS
How can it read old log entries and I NOT create new ones?
I am sure I missing something. Can I know what?
Also, It will be good to have an entry in the ELOG web-site
explaining any migration steps from Window to Linux and reverse!
Please, help.
Thank you! |
| Steve Jones wrote: | The first place to look is at the permissions set on the existing directories and .log files plus the Owner and Group. (Not knowing how the files got from Windows to Linux is a little problematic but the translation of permissions is not straightforward.) Compare the settings with how you have eLog starting up on your linux box. Typically, when run as a daemon, it starts as ROOT then becomes the USER/GROUP that you specify in the .cfg file. It is likely that you will find a permission mismatch. As to why you can read but not write, with a permission mask of 744 and .log files owned by root but elogd running as nobody, you would be able to read the logs but not change them. Sounds like the permissions are similar on the directories as well. Perhaps you could post the info back here.
|
|