Re: Suggestion additional ElCodes, posted by Stefan Ritt on Tue Jan 24 22:52:48 2006
|
[quote="T. Ribbrock"]However, there are two things I'm missing:
[LIST]
[*] [I]Headings[/I]
|
Re: Access to global configuration in v2.6.1, posted by Stefan Ritt on Wed Jan 25 08:24:28 2006 
|
> Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both
with the
> existing cfg file and with the new cfg.
|
|
Re: Access to global configuration in v2.6.1, posted by Stefan Ritt on Wed Jan 25 12:10:46 2006
|
> or maybe browser cookies.
That rings a bell. If you change user permissions (like password file/no password file/rename logbooks) you might be
|
|
Re: ELOG v2.6.0 (Linux) crashes while using " Forgot password?", posted by Stefan Ritt on Thu Jan 26 15:07:11 2006
|
[quote="Dimitrios Tsirigkas"]Is there going to be a fix for that version as well?[/quote]
A fix is always for all versions, since I have a common code base. Have you tried Version 2.6.1? |
|
Re: Quicklink does not work for one field, posted by Stefan Ritt on Fri Jan 27 13:52:34 2006
|
[quote="mark james"]OK. But where do I get this from? The "latest version of 19 Jan is still 1622.[/quote]
If you can compile it yourself, you get it from Subversion (see [URL=/afs/pi.infn.it/group/mug/docs/talks/review_feb06/]here[/URL]). Otherwise you have |
|
Re: Running elog as ordinnary user, posted by Stefan Ritt on Fri Jan 27 23:18:07 2006
|
[quote="G. Vandemoortele"]I've configured elog with some commands running a shell :
Preset R-Date = $shell(/usr/bin/date +"%Y/%m/%d %H:%S")
|
|
Re: Running elog as ordinnary user, posted by Stefan Ritt on Sat Jan 28 12:54:03 2006
|
[quote="G. Vandemoortele"]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.[/quote]
|
|
Re: Running ELOG under Apache, posted by Stefan Ritt on Mon Jan 30 12:27:08 2006
|
[quote="Dimitrios Tsirigkas"]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 |