Hosts Allow and Password File, posted by Jeremy Perkins on Wed Jun 21 18:36:06 2006
|
| I'm trying to set up an elog that uses a password file using the "Password file = /blah" directive as well as the "Hosts allow = myhost.mydomain" directive. I used the -v command and watched the messages and elogd is recognizing that I am connecting from an allowed host but the login page is still appearing. Is there a way to use both of these? |
Host ELOG on Raspberry Pi for small lab, posted by Michel Döhring on Thu Mar 20 10:25:59 2025
|
Dear all,
is there an instruction document how to exacly host the ELOG on a server for example a raspberry pi?
Wishes,
M |
Hilight code, posted by Daniel Sajdyk on Tue Sep 6 13:29:03 2016
|
Hello :)
Is there any way to highlight code (for example php, SQL) in logs entries?
Best Regards
Daniel Sajdyk |
|
Highlight code?, posted by Daniel Sajdyk on Tue Sep 6 13:35:05 2016
|
Hello :)
Is there any way to highlight code (for example php, SQL) in elogs entries?
Best Regards
Daniel Sajdyk |
|
Hiding attributes in Detail view?, posted by Justin Ellison on Fri Mar 2 16:39:22 2007
|
First off, thanks so much for this product. It works excellent for us as a server activity log. I have a question, which depending on the answer, might be a feature request 
As I mentioned, we use elog as a serverlog. Sometimes, but not always, we will have a Bugzilla bug # that is associated with the log entry. We then take that bug #, and build a link to our bugzilla server displaying the bug. Here's the relevant config entries:
Attributes = Author, Classification, Subject, Bug Number, Environment, Server, Bugzilla
...
#Make the list table narrow enough to fit in the browser
List display = ID, Date, Author, Subject, Server, Bugzilla
...
#We take in a Bug Number from the user, then calculate a Bugzilla link from that
Change Bugzilla = <a href="http://bugz:4545/bugzilla/show_bug.cgi?id=$Bug Number">$Bug Number</a>
List Change Bugzilla = <a href="http://bugz:4545/bugzilla/show_bug.cgi?id=$Bug Number">$Bug Number</a>
Hidden Attributes = Bugzilla
So, on new entry, the user has the option to enter a Bug Number. Bugzilla is not displayed because it is derived. In list view, Bug Number is not displayed, but Bugzilla is, providing a handy link to the bug on a different server.
The only thing that isn't working as I'd like is when someone views a log entry. Both Bug Number and Bugzilla show up in the attributes. This isn't a huge deal, it's just showing redundant data.
Is there a way to hide Bug Number on the view page? |
|
Hiding Logbook tabs, posted by Alan Grant on Thu Mar 28 21:55:14 2019
|
I know you can restrict access to logbooks on per user basis but can anyone tell me if it is possible to HIDE certain logbook tabs/groups on per user basis (ie, so they would just see logbooks they are authorized to see)? |
|
Hiding Comments on the Logbook Selection Page, posted by Adam Blandford on Tue Mar 3 11:30:01 2009
|
Hi
I was just wondering if there was a way that the comments for a logbook could be set to be invisible on the Selection page but then displayed once a user has logged in to a particular logbook?
This is required for security purposes. I want a common login page which shows all logbooks, where the logbook names only have meaning for people who know them but then once logged in the comment provides additional information about that logbook.
Thanks
Adam |
|
Hide/Un-hide Commands based on Attribute Option value, posted by Barend on Wed Jan 2 14:04:41 2013
|
Hi Stefan,
Happy New Year!
I ran several searches thru the forum but I could not detect a suitable entry on the following:
Is it possible to hide/un-hide the Commands, like "Edit", "Reply", "Duplicate", from the Menu based upon an Option of an Attribute?
E.g. Attributes = Status, .. | Options Status = Open, Closed
When Status = "Open"; the Menu Commands "Edit", "Reply" and "Duplicate" are available.
When Status = "Closed"; the Menu Commands "Edit", "Reply" and "Duplicate" are hidden/not available.
-or-
Can this only be accomplished using 2 Logbooks (Open / Closed) and move an entry from "Open" to "Closed" where the Logbook "Closed" is not using the Commands "Edit", "Reply", "Duplicate".
Kind regards,
Barend |
|