Auto-refresh ELog display, posted by Alan Stone on Thu Aug 24 15:52:54 2006
|
We have multiple LCDs at a console, and usually one is dedicated to displaying a browser
with the local ELog. Meanwhile, others are making entries from another machine. If
no one clicks on refresh, the ELog display becomes stale. Is there a method to have
the ELog reload every X minutes?
Thanks, Alan |
|
Re: Date format in Threaded display, posted by deletoille on Thu Oct 19 12:26:16 2006
|
| Stefan Ritt wrote: | That fix for Steve Jones was slightly different, it had to do with substitutions in threaded display. I fixed yours now in revision 1734, so give it a try.
Salut,
Stefan |
Hello,
I’ve tried on the last available release (revision 1732) and I have the same problem.
You said in you previous message that: “I fixed yours now in revision 1734, so give it a try.”
Could you tell me when this one will be available?
Thanks in advance |
|
Attributes according to users, posted by ather khan on Sat Nov 18 11:19:14 2006
|
Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.
thanks,
Ather |
|
Hardcoded Path in Makefile, posted by Martin Killenberg on Tue Feb 20 18:41:31 2007
|
I tried to compile ELOG on Scientific Linux Cern 4.4 and found that make quits because uname is not located in /usr/bin (like it is hardcoded in the makefile) but in /bin.
Later I found that this is only the case in the svn version, in the "latest.tar.gz" from 2007/02/20 the path is /bin.
Why do you have the absolute path in the Makefile? uname should be in the default path on any system. (The same applies to "rm")
I also was confused that you only provide one rpm Package (except for debian) without mentioning for which distribution. You try to avoid dependencies, but the elogd is linked against the basic libraries libc and ld-linux, which might vary. |
|
Addition of a "Restrict edit attribute" option?, posted by Justin Ellison on Tue Mar 13 17:27:49 2007
|
It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
Sound plausible?
Justin |
|
Upgraded from 2.6.1 to 2.6.5, but cannot login now & top.html is not displayed, posted by Alan Stone on Mon Apr 30 20:52:51 2007
|
We followed the simple download instructions. Our existing logbook entries
are still visible. Nothing was lost or touched in our /usr/local/elog directory.
Is there some step we missed?
Alan |
|
how to supress checkboxes of all logbooks at registration?, posted by Mark Bergman on Thu May 31 23:33:28 2007
|
Is there a way to suppress the listing of all logbooks on the New User Registration page? We've got 100 logbooks (one for each server, cluster node, or major software package). The long list makes it difficult for users to find the bottom of the registration page, and no user needs to subscribe for automatic e-mail notification for every logbook.
Thanks,
Mark |
|
config settings to ensure replies to author, thread contributors, admin?, posted by Mark Bergman on Thu May 31 23:46:31 2007
|
I'm having some difficulty configuring elog to ensure that the original author of an entry, any contributors to the thread, and a desginated administrator get e-mail notification for any change to the thread.
Here's a subset of the current elogd.cfg:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status, CC E-mail To
Display Email recipients = 1
Email All = $CC E-mail To
Email All = mark.bergman@uphs.upenn.edu
Email Format = 47
Suppress default = 0
Type CC E-mail To = museremail
The "Suppress default = 0" setting is used because many people mistakenly subscribe for automatic e-mail notification of all our logbooks when they self-register. I was hoping that the "Email All" directives would override the suppression of default mail.
This configuration works partially...in that if a user specifically selects addresses in the "CC E-mail To" field, those people do get mail.
The documentation states that there can be multiple "Email All" directives, so I thought they would be additive--causing the admin address and the author to always get mail.
Is there a setting to ensure that the original author of the thread is always notified upon any change?
Thanks,
Mark |