Re: 2.6.0-bata5, posted by Stefan Ritt on Wed Dec 21 20:39:52 2005
|
| Carl Shirey wrote: | Do you have 2.6.0-bata5 for linux as setup for RPM install. I was able to locate the version for windows but not for linux.
Thanks for your help. |
There is a 2.6.0 out by now. |
|
Re: Proxy question, posted by Stefan Ritt on Wed Dec 21 20:59:26 2005
|
> I'm trying to run elog 2.6.0-beta4 under Apache 2.0. I follow the directions, and everything works fine, so my
> elog runs as
>
> http://grattalab3.stanford.edu/elog/
>
> running under port 8082, with the following lines in my httpd.conf file
>
> Redirect permanent /elog http://grattalab3.stanford.edu/elog
> ProxyPass /elog/ http://grattalab3.stanford.edu:8082/
>
> This machine has an alias, which is http://exo-elog.stanford.edu. My question is, how can I run elog so that
> when someone types in this name, it brings up my elog? I know that I can make a VirtualHost entry and put a
> redirect at the document root of that virtual host, but that seems clumsy. Can I just modify ProxyPass or add a
> Redirect statement somehow?
To my knowledge you need a VirtualHost entry, plus a "URL = http://exo-elog.stanford.edu" entry in elogd.cfg |
Posting without logging in!, posted by Dimitrios Tsirigkas on Thu Feb 9 14:15:54 2006
|
Hi all! This is an HTTP POST request submitted from the command line using curl, and providing no authentication information. If I can post as myself using this command, then shouldn't something be done about this? Cheers, Dimitris |
|
Re: Posting without logging in!, posted by Stefan Ritt on Fri Feb 10 11:41:38 2006
|
| Dimitris wrote: | | Hi all! This is an HTTP POST request submitted from the command line using curl, and providing no authentication information. If I can post as myself using this command, then shouldn't something be done about this? |
Yes indeed. I fixed that in SVN revision 1655. I upgraded this server so you can try again if it works. |
|
Re: Posting without logging in!, posted by Dimitrios Tsirigkas on Fri Feb 10 16:16:11 2006
|
| Stefan Ritt wrote: |
Yes indeed. I fixed that in SVN revision 1655. I upgraded this server so you can try again if it works. |
Just tried it, it's fixed 
Dimitris |
|
Re: MOptions problem ?, posted by Alex H on Tue Feb 28 09:56:55 2006
|
Hi Holger,
> Which ELOG version do you use?
I'am using the version V2.6.1-1653 of Elog
> From which logbook are the screenshots? (I assume it's Liste - right?)
Right :)!
I've just seen that Stefan has build a V2.6.1-1663 version of ELOG.
I try to install this new version and gave you answer as soon as possible :)! |
[SOLVED] Re: MOptions problem ?, posted by Alex H on Tue Feb 28 12:08:42 2006 
|
Yop,
I think I found the solution! I was in fact a conditions conflict!
See the attached picture for easiest comprehension.
My list box type's conditions (FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}) conflict with my Equipment's conditions. It seems that the condition ID must be unique across the whole elogd.cfg.
So I have replaced my "Options Type = FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}"
by : "Options Type = FWL1{101}, FWL2{102}, FWL4{103}, VPN1{104}, VPN2{105}, CLIVPN-PROC"
and it works well ! |
|
[SOLVED] Re: MOptions problem ?, posted by Stefan Ritt on Wed Mar 1 07:48:11 2006
|
| Alex H wrote: | | It seems that the condition ID must be unique across the whole elogd.cfg. |
Right. Here is a quote from the Manual:
| ELOG Manual wrote: | | The only requiremnt is that conditions are unique, meaning that a condition in one option list cannot be used in another list. |
So just read the manual  |