ID |
Date![down down](down.png) |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
453
|
Wed Nov 19 09:06:11 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 12/7/2003 | Re: elog.exe | > impossible to create the moptions with
>
> -a Type#0="%D1%"
> -a Itel#0="%zItel%"
>
> the variable are set to
> set D1=Tel
> set zItel=Tel.gif
>
> other standard option work fine
Sure it works. But in your elogd.cfg, you have ROptions, not MOptions! I
changed this to
...
IOptions Itel = Tel.gif, TelDirect.gif, Fax.gif, Gsm.gif, Tel2.gif,
TelHome.gif,TelFax.gif,TelHelp.gif
MOptions Type = Tel,TelDirect,Fax,Gsm,Tel2,Home,Combine,TelHelp
...
Then I added a batch file elog_submit.bat with following contents:
elog -h 'my site elo' -p 83 -l 'my logbook' -a Phone=%1 -a Contact="%2 %3" -a
Type#0="%TYPE% -a Cat="%4" -a Itel#0="%ITEL%" %5 %6 %7
Then I made a
set TYPE=Tel
set ITEL=Tel.gif
and a
elog_submit 123 a b CAT Test Message
ans all worked fine. Please change your ROptions to MOptions and try again. |
452
|
Tue Nov 18 23:19:57 2003 |
| Justin Dieters | enderak@yahoo.com | Comment | Linux | 2.3.9 | Update request for Admin Guide | Heya, I've been using elog for a year or so, with a proxy through Apache,
but recently I've ran into some trouble with my Apache config, where
spammers were using my incorrectly configured proxy to send spam.
I have
some requests for the Administrator's Guide: "Running elogd under Apache".
I'm hoping a few little notes will save others the trouble I've gone
through. Neither of these are any fault of elog's or Apache's, but of my own
ignorance. (I am using elog 2.3.9, and Apache 2.something, if that matters)
1) When doing "ProxyPass ..." when setting up elog under Apache, do NOT put
"ProxyRequests On". This is not needed, if it is enabled and not set up
correctly, it allows spammers to send spam via Apache's proxy. More
information on this is here: http://www.apacheweek.com/issues/03-07-25,
about halfway down the page, under "Spammers use open Apache proxies"
Even though it doesn't mention ProxyRequests in the guide, I think there
should be a little side note mentioning that "ProxyRequests On" is NOT
needed, because I put it in, thinking it was - I am probably not the only one.
2) I have found that mod_proxy_http.c must be loaded in addition to
mod_proxy.c and mod_alias.c for the proxy to work, otherwise I get a 403
error. I think this should be mentioned as well. |
451
|
Wed Nov 12 12:34:02 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | Linux | 2.3.9 | Re: speed is very slow if logbook contains many entries | This is a very nice measurement you made and helps me a lot. I will
incorporte your suggestions into the next version. Under Windows however,
there is no -HUP signal, so that won't work for them. But what I can easily
do is to check for new configuration/language file once every access, not
once every loc() or getcfg(). I till think about.
Thanks again,
Stefan |
450
|
Wed Nov 12 12:25:44 2003 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug fix | Linux | 2.3.9 | speed is very slow if logbook contains many entries | This is not really a bug, but elogd was getting really slow with our
logbook. It took about 4 1/2 seconds just to get the default page in
threaded mode with 15 entries. The logbook has in total about 2000
entries, though.
After playing around with the compiler option '-gp' and gprof the
problem was found: loc() is called about 18000 times per logbook
access! (Attached you can find the gprof output. There might be
other places where to save time: e.g. getcfg().) The function loc()
calls stat every time to check if the language file was updated and
this takes a long time especially over NFS.
The quick solution for me was to just replace loc() with 'char
*loc(char *orig) {return orig;}'. Therefore, I cannot use the
localization that I used anymore, which is not a big problem at the
moment. After that the time to download the default page was only
0.16 s; almost a factor of 30 faster!
I would suggest to only read the language file (AND also the config
file!) once upon startup. After changing things one has to restart
elogd, which is not so nice, but the long delay is not acceptable.
Another option not to restart elogd is to make elogd respond to a
signal (e.g. kill -HUP) to reread the config and language files. |
449
|
Wed Nov 12 07:52:45 2003 |
| Etienne Van Caillie | etienne.vancaillie@mba.be | Bug report | Windows | 12/7/2003 | elog.exe | impossible to create the moptions with
-a Type#0="%D1%"
-a Itel#0="%zItel%"
the variable are set to
set D1=Tel
set zItel=Tel.gif
other standard option work fine
does anybody has good experience with elog.exe command ?
elog -h 'my site elo' -p 83 -l 'my logbook' -a Phone="%2" -a Contact="%3 %
4" -a Type#0="%D1%" -a Cat="%5" -a Itel#0="%zItel%" "%6 %7 %8 %9"
----------------------------- here are the config in elog
[titiPHONE]
Comment = PhoneList
Find menu text = menu/titiphone_top.html
Data dir = prive_Etienne/PhoneList
Guest Menu commands = Help
Find Guest Menu Commands = Help
Attributes = Phone, Itel, Dossier, Ext_direct, Societe, Contact, Cat,Type,
Prive, Email, Adress, City, Relation, By
Quick filter = Itel,Type,Dossier,Date,Prive
Roptions Prive = no,CD,EC,MD,NB,TR,TV,AH,NW,JW,Manon
IOptions Itel = Tel.gif, TelDirect.gif, Fax.gif, Gsm.gif, Tel2.gif,
TelHome.gif,TelFax.gif,TelHelp.gif
ROptions Type = Tel,TelDirect,Fax,Gsm,Tel2,Home,Combine,TelHelp
Preset Itel = Tel.gif
Preset Type = Tel
Preset Prive = no
Preset Email =
Display mode = Summary
Thread Icon = Itel
Thread display = $Phone,$Contact,$Dossier,$Societe($Type/$prive) |
448
|
Tue Nov 11 13:49:50 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.3.9 | Re: Elogd.exe Crashes When There are too Many Replies to Replies... | I found a stack overflow if there are too many replies. This has been fixed in
the current CVS verson of elogd.c and will be incorporated into the next release. |
447
|
Tue Oct 28 22:40:28 2003 |
| G | levineg@med.govt.nz | Comment | Other | elog2.3.9 | Re: FreeBSD Install | Thanks for that mate, compiled elog on FreeBSD 5.1 myself no problems just like
you said, great!
>
> FYI- the default "make" on FreeBSD is BSD, not GNU.
>
> The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
> package) and type "gmake". That's all it took for me to build a freshly
> downloaded copy on 5.1 not 5 minutes ago. |
446
|
Sun Oct 26 18:32:17 2003 |
| Dave Truesdell | davet@ttfn.com | Comment | Other | elog2.3.9 | Re: FreeBSD Install | > I got elog 2.3.9 running on FreeBSD 5.1 successfully,
> I compiled elog on a redhat box and then just copied over all the files to
> the FreeBSD box and ELOG just ran with no issues.
> It's been running under heavy use for at least a month now.
FYI- the default "make" on FreeBSD is BSD, not GNU.
The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
package) and type "gmake". That's all it took for me to build a freshly
downloaded copy on 5.1 not 5 minutes ago. |
|