| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67258
|
Tue May 1 17:03:37 2012 |
 | Per Eriksson | pelle@sm4xiu.eu | Info | Linux | Any | Re: Compiling Elog for QNAP NAS x86 |
| Per Eriksson wrote: |
|
Hi All,
I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?
Regards,
Per
|
I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)
Per |
|
67257
|
Tue May 1 11:38:05 2012 |
 | Per Eriksson | pelle@sm4xiu.eu | Request | Linux | Any | Compiling Elog for QNAP NAS x86 |
Hi All,
I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?
Regards,
Per |
|
67256
|
Tue May 1 09:20:00 2012 |
 | Christopher Lee | chris@chrisandclaire.org | Bug report | Linux | 2435 | Re: Forgot Password |
| Stefan Ritt wrote: |
|
| Christopher Lee wrote: |
|
We seem to have a problem with retrieving user passwords using the forgot password system
|
Thanks for reporting that bug. With the help of your config file I finally could reproduce and fix it. The fix is contained in SVN revision 2462.
|
Thanks mate.. Glad to know it wasn't just me going insane? I'll keep an eye out for the new file |
|
67255
|
Mon Apr 30 17:05:28 2012 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2435 | Re: Forgot Password |
| Christopher Lee wrote: |
|
We seem to have a problem with retrieving user passwords using the forgot password system
|
Thanks for reporting that bug. With the help of your config file I finally could reproduce and fix it. The fix is contained in SVN revision 2462. |
|
67254
|
Fri Apr 27 00:29:56 2012 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.9.1 | Re: obfuscate password in verbose logging |
> I'd suggest that the "-v" option hide passwords. If they need to be revealed for debugging
As a work around, I've changed the elogd startup script to do:
/usr/local/sbin/elogd -v -c /usr/local/elog/elogd.cfg 2>&1 | perl -ne '$|=1; if ( $_ =~ /name="upassword"/
) {<>; <>;} else { print "$_";}' > /var/log/elog 2>&1 &
That simply throws away lines that match the pattern:
name="upassword"
and the following 2 lines (the last of which contains the password). |
|
67253
|
Thu Apr 26 23:57:04 2012 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.9.1 | obfuscate password in verbose logging |
I'm trying to debug an issue with elogd (2.9.1) and was reminded that using the "-v" option exposes
user passwords. This wasn't a huge problem for us in the past, but we're now using kerberos authentication,
meaning that the exposed username/password applies to lots of sensitive systems within our university.
I'd suggest that the "-v" option hide passwords. If they need to be revealed for debugging
purposes, make that a separate (and very well documented) option. Maybe something like:
"--really-include-passwords-as-clear-text-in-log-output". :) |
|
67252
|
Wed Apr 18 21:53:26 2012 |
| A. Tuttle | ATuttle@UW.edu | Question | Linux | 2.9.1-2435 | Re: author field in reply |
Look in https://midas.psi.ch/elog/config.html
--
Fun things to set are:
Preset on first reply <attribute> = <string>
and
Preset on reply <attribute> = <string> |
|
67251
|
Tue Apr 17 21:59:43 2012 |
| Rex Tayloe | rtayloe@indiana.edu | Question | Linux | V2.9.0-243 | Re: create "front page" for a logbook |
| Stefan Ritt wrote: |
|
| Rex Tayloe wrote: |
|
Is there a way to create a "front page" or "table of contents" for a logbook?
While chronological entries are good and what elog was designed for, I find myself wanting a page to summarize important things
and/or link to important files that are somewhere in that logbook. And, I would like to use the features of the elog editor to do (not just point
to another www page that points to the various elog entries). For example, in an analysis logbook, you would like to have one page that
may summarize latest on analysis and point to best/latest plot/drawing of something and not have to re-search for it every time.
I think that start page with cmd to go to entry 1 (how do I do that?) may work. Then I just keep editing entry 1 to point to latest info or
entries. Will this work? Will I run into a size limitiation if I attach too many files to that? Is there a better way?
One could imaging using a wiki to do this, however, I never seem to get to updating our wikis... maybe I should just figure how to
get elog to do it.
Thanks.
|
Well, if you never get to update your wiki, you will you get to update your summary page? As you know there is no free lunch.
For my analysis logbooks, I do it such that I create an arbitrary entry in the logbook, where I put references to other entries. Using the syntax "elog:<id>" this is very simple like here: elog:67222. Then I put a link to that special page in my browser bookmarks. This puts me one mouse click away from accessing this page. You can link to other elog pages but also to page attachments this way, so no need to put too many attachments into a single page, although there is no limit on that.
Best regards,
Stefan
|
Thanks for suggestion... it gave me idea for slightly different way to do it. The method you suggest doesnt work that well to share in group (everyone would have to add that link in their bookmarks).. So I added this in config file:
Title image = <img border=0 height=25 src="bulb.png" alt="Summary/TOC entry">
Title image URL = <http:link to my specific elog page/entry num>
That replaces elog help icon with a link to TOC entry which can be any entry number. One could make a custom icon and perhaps play around with adding more than one link (?).
Another thing that could do same thing and maybe more consistent with elog philiosophy would be to add a command that goes to a specific link or entry.... but this current solution works... |