Re: Truncation of the displayed text in Summary view of the list of entries, posted by Olivier Callot on Wed Mar 14 15:08:17 2012
|
| Stefan Ritt wrote: |
|
| Olivier Callot wrote: |
|
In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.
|
That's a feature 
In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose.
|
Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway. |
Re: Truncation of the displayed text in Summary view of the list of entries, posted by Stefan Ritt on Wed Mar 14 16:04:04 2012
|
| Olivier Callot wrote: |
|
| Stefan Ritt wrote: |
|
| Olivier Callot wrote: |
|
In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.
|
That's a feature
In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose.
|
Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway.
|
Ok, I fixed that in revision 2442. |
segfault on empty, non-writable passwd file, posted by Achim Dreyer on Mon Mar 26 13:44:23 2012
|
Segfault when password file is empty and not writable a segmentation fault is generated when a new user tries to register:
root# > passwd
root# chown root.root passwd
root# chmod 644 passwd
root# grep -i usr elogd.cfg
root#
kernel: [515323.672377] elogd[31048]: segfault at 78 ip 00000000004ba780 sp 00007fff03cd2078 error 4 in elogd[400000+dc000]
I cannot reproduce this error when running within gdb.
|
create "front page" for a logbook, posted by Rex Tayloe on Thu Mar 29 17:30:28 2012
|
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. |
|
Re: create "front page" for a logbook, posted by Stefan Ritt on Thu Mar 29 23:43:30 2012
|
| 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 |
|
Re: segfault on empty, non-writable passwd file, posted by Stefan Ritt on Tue Apr 10 15:35:07 2012
|
| Achim Dreyer wrote: |
|
Segfault when password file is empty and not writable a segmentation fault is generated when a new user tries to register:
root# > passwd
root# chown root.root passwd
root# chmod 644 passwd
root# grep -i usr elogd.cfg
root#
kernel: [515323.672377] elogd[31048]: segfault at 78 ip 00000000004ba780 sp 00007fff03cd2078 error 4 in elogd[400000+dc000]
I cannot reproduce this error when running within gdb.
|
Thanks for reporting that bug. I fixed it in SVN revision 2448. |
Kerberos authentication, posted by Thomas Kleeb on Wed Apr 11 13:09:56 2012 
|
Hello to @all
First please let me say that I'm a complete green-horn when it comes to linux
I'm running elog on a linux virtual server and would like to use kerberos authentication. If I set 'Authentication = Kerberos' in the elogd.cfg file I get,
If I set 'Authentication = Kerberos, File' it works fine. I hope this is just some error on my part.
thanks,
Tom |
|
Re: Kerberos authentication, posted by Stefan Ritt on Wed Apr 11 13:17:48 2012
|
| Thomas Kleeb wrote: |
|
Hello to @all
First please let me say that I'm a complete green-horn when it comes to linux
I'm running elog on a linux virtual server and would like to use kerberos authentication. If I set 'Authentication = Kerberos' in the elogd.cfg file I get,
If I set 'Authentication = Kerberos, File' it works fine. I hope this is just some error on my part.
thanks,
Tom
|
Is Kerberos set up correctly on your PC? What is the Kerberos Realm? Does the command "kinit <your user name>" work correctly? If not, you have to install and configure Kerberos correctly. Make sure to have USE_KRB5 turned on in your Makefile. |