| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2082
|
Sat Nov 18 11:19:14 2006 |
 | ather khan | ather.khan@cpjeddah.com | Question | | | Attributes according to users |
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 |
|
2143
|
Tue Feb 20 18:41:31 2007 |
| Martin Killenberg | martin.killenberg@web.de | Comment | Linux | 2.6.4 | Hardcoded Path in Makefile |
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. |
|
2162
|
Tue Mar 13 17:27:49 2007 |
| Justin Ellison | justin@techadvise.com | Request | | Current | Addition of a "Restrict edit attribute" option? |
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 |
|
2225
|
Mon Apr 30 20:52:51 2007 |
| Alan Stone | alstone@fnal.gov | Question | Linux | 2.6.5-1857 | Upgraded from 2.6.1 to 2.6.5, but cannot login now & top.html is not displayed |
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 |
|
2236
|
Thu May 31 23:33:28 2007 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | V2.6.5-186 | how to supress checkboxes of all logbooks at registration? |
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 |
|
2237
|
Thu May 31 23:46:31 2007 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | V2.6.5 | config settings to ensure replies to author, thread contributors, admin? |
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 |
|
65632
|
Thu Oct 25 12:04:02 2007 |
| Peter Rienstra | peter.rienstra@gmail.com | Bug report | Other | 2.6.5:1946 | Date attribute in Quick filter |
Stefan,
I downloaded the latest source (ELOG V2.6.5-1946) to solve another problem. But now I get:
Error: "Attribute "Date" for quick filter not found", see attachment.
In the configfile I have: Quick filter = Date
A bug?
(It works fine, so it's not really a big problem.) |
|
65634
|
Thu Oct 25 23:36:28 2007 |
| Alan Stone | alstone@fnal.gov | Bug report | Linux | 2.6.5-1844 | Email notification: "Use Email From = " always set to admin |
My current syntax is:
; Email notification
Suppress Email to users = 0
Omit Email To = 1
Use Email Subject = $system: $subject
#Use Email From = Author Email
Email Report General = hn-cms-dataopslog@cern.ch, cms-dataops@fnal.gov
I had to comment out the 'Use Email From' option because all forwarded
entries to the CMS HyperNews or Fermilab ListServer appeared to originate
from me (alstone@fnal.gov), even though other users were logged in and
saving the entries to the logbook. After commenting out this line, the
entries were properly credited when forwarded, although the
There are two admins defined in the [global] section, and "alstone" is
not the first name in the "Admin user" list.
Is this a bug, or have I used this option incorrectly?
Alan |