Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 611 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6456 Entries 
Goto page Previous  1, 2, 3 ... 610, 611, 612 ... 805, 806, 807   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subject
  1646   Fri Feb 3 12:38:57 2006 Question Willem KosterW.Koster@rc.rug.nlQuestionOther2.6.1sort after find
When I do a find (like Field1 = XXX )
and then try to sort the results I get the entire list again (but sorted) instead of the sorted results.
But when I fabricate a url manually like

http://elog.com/Forum/?mode=summary&npp=990&Field1=XXX&sort=field2

I do get the search-results nicely sorted.

Obviously I would like to be able to sort the result of a find-query.

Is this a bug or a feature request ?
  1645   Fri Feb 3 11:54:22 2006 Disagree Willem KosterW.Koster@rc.rug.nlBug reportOther2.6.1[261] problem with month selection
I have several date-fields defined in my logboek. But when I click the icon and select another month the pop-up 
window get's filled  with the contants of the logboek instead of the date-selection.

Date format = %Y%m%d
  1644   Thu Feb 2 03:19:44 2006 Question Angus Auangus_au@promina.com.auQuestionOther2.6.1compiling elog 2.6.1 on solaris platform
I came across problem in compiling elog 2.6.1 on solaris platform.

The messages "

# make
gcc -o elog src/elog.c -lutil -lsocket -lnsl
ld: fatal: library -lutil: not found
ld: fatal: File processing errors. No output written to elog
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target `elog'

It seems to me that library libutil does not exist on solaris platform.

Is there any fix ? I can compile elog 2.6.0 successfully on solaris.
  1643   Mon Jan 30 16:26:08 2006 Warning T. Ribbrockemgaron@gmx.netBug reportLinux2.6.1-1637Numbered lists get closed by </ul>
I just ran into the following problem (and was able to reproduce it in the "demo" logbook on this site):

  • Create a new entry
  • Create a numbered list:
    [LIST=1]
[*] 1st entry
[*] 2nd entry
[/LIST]
  • In the resulting HTML code, the closing statement of that list translates to </ul> instead of </ol>, causing the list to remain open and all following text to be intented by the list indentation. This gets worse when several such lists are used in one document. I'll include an example below.

Numbered list follows:

  1. one
  2. two
  3. three

This text is indented, as the list was not closed properly.

  1. four
  2. five
  3. six

And now we have double indention...
  1642   Mon Jan 30 12:27:08 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: Running ELOG under Apache

Dimitrios Tsirigkas wrote:
Sorry if this has been asked elsewhere and I'm missing it. I want to stop users from accessing my elog by loading the URL: http://mycomputerURL:8080 and only make it accessible through http://mycomputerURL/elog. The end goal would be to use Apache to control access. I followed the instructions under "Running elogd under Apache" in the admin guide, but what that did was simply to redirect browsers trying to load ttp://mycomputerURL/elog to http://mycomputerURL:8080.


If you want to have user-level access control, you need to do that with the config option
Password file = ...

Then, if you have the
URL = http://mycomputerURL/elog

statement in your config file, you get redirected from elogd after each login automatically to that URL. If you physically want to block the 8080 port, you have to do that on the operating system level, like with iptables or ipchains.
  1641   Mon Jan 30 11:41:18 2006 Question Dimitrios Tsirigkasdimitrios.tsirigkas@cern.chQuestionLinux2.6.1Running ELOG under Apache
Hi,

Sorry if this has been asked elsewhere and I'm missing it. I want to stop users from accessing my elog by loading the URL: http://mycomputerURL:8080 and only make it accessible through http://mycomputerURL/elog. The end goal would be to use Apache to control access. I followed the instructions under "Running elogd under Apache" in the admin guide, but what that did was simply to redirect browsers trying to load ttp://mycomputerURL/elog to http://mycomputerURL:8080.

Thanks,
Dimitris
  1640   Mon Jan 30 10:21:41 2006 Reply Dimitrios Tsirigkasdimitrios.tsirigkas@cern.chBug reportLinux2.6.0Re: ELOG v2.6.0 (Linux) crashes while using " Forgot password?"

Dimitrios Tsirigkas wrote:
A fix is always for all versions, since I have a common code base. Have you tried Version 2.6.1?


Yep, 2.6.1 works fine. Thanks,
Dimitris
  1639   Sat Jan 28 12:54:03 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1 CVSRe: Running elog as ordinnary user

G. Vandemoortele wrote:
Started via root (# /usr/sbin/elogd -c /home/gv/.elog/elogd.cfg -x), it works,
but via "gv" ($ /usr/sbin/elogd -c /home/gv/.elog/elogd.cfg -x), it doesn't.


I tried with your config file, and it works fine (see attached screendump). So I have no clue right now why it is not working in your case.
Attachment 1: screendump.png
screendump.png
Goto page Previous  1, 2, 3 ... 610, 611, 612 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6