stunnel problems with new version, posted by damon nettles on Mon Nov 15 20:50:01 2004
|
i am trying to implement ssl features on our logbooks. however, it seems
that stunnel has drastically changed their program and the usual startup
procedures listed on the elog page don't work.
so, what is the new method for getting elog set up with stunnel? |
Re: stunnel problems with new version, posted by Stefan Ritt on Mon Nov 15 21:25:34 2004
|
> i am trying to implement ssl features on our logbooks. however, it seems
> that stunnel has drastically changed their program and the usual startup
> procedures listed on the elog page don't work.
> so, what is the new method for getting elog set up with stunnel?
stunnel is kind of a deprecated feature. Better use the SSL proxy of Apache,
as written in the elog admin guide. If someone else figures out how to use the
more revent stunnel, I'm willing to update the documentation. |
Re: stunnel problems with new version, posted by damon nettles on Mon Nov 15 21:59:56 2004
|
> > i am trying to implement ssl features on our logbooks. however, it seems
> > that stunnel has drastically changed their program and the usual startup
> > procedures listed on the elog page don't work.
> > so, what is the new method for getting elog set up with stunnel?
>
> stunnel is kind of a deprecated feature. Better use the SSL proxy of Apache,
> as written in the elog admin guide. If someone else figures out how to use the
> more revent stunnel, I'm willing to update the documentation.
okay. that's good to know. i'll try using the apache method instead. but, there is
something wrong with the "secure" link to an example on the elog administrator's
guide. |
$message id gives wrong value - Gernman traslalation of Back, posted by Ulrich Trüssel on Fri Nov 5 16:59:30 2004
|
1.
I do not know if this is a problen of the 2.5.5 (11/03/04) version or of
other versions as well:
I'm using the $message id parameter in a substitution:
Subst KlientIn/KundIn = $Vorname $Name; P: $Telefon Privat; G: $Telefon
Geschäft; N: $Telefon Mobil; $Landeskennung-$PLZ $Ortschaft [<a
href="http://localhost:8080/$logbook/$message id">$logbook:$mesage id</a>]
the "$message id" will not be replaced by the msg id, the string "$message
id" will be dispalyed and used. Other substitutions as $logbook etc. are
working.
Is this a bug or did i missunderstood the manual?
2.
Since Version 2.5.5: If ELOG is running under German, the "Zurück" Bottom is
named "Back". Any Idee where I can change this back? ;-)
2.5.4-6 was corretly translated. |
Re: $message id gives wrong value - Gernman traslalation of Back, posted by Stefan Ritt on Fri Nov 5 17:45:47 2004
|
> the "$message id" will not be replaced by the msg id, the string "$message
> id" will be dispalyed and used. Other substitutions as $logbook etc. are
> working.
>
> Is this a bug or did i missunderstood the manual?
Well, the manual does not state that "$message id" should work for "Subst
<attribute>" option (;-)
The reason is that the message ID is available only *after* a new entry has been
written to the database, and the "Subst" command is evaluated *before* an entry
is submitted. "$message id" only works for "Thread display", "RSS Title", "Subst
on reply", "Subst on edit" and "Display". You should use
Display KlientIn/KundIn = $Vorname $Name; P: $Telefon Privat; G: $Telefon
Geschaft; N: $Telefon Mobil; $Landeskennung-$PLZ $Ortschaft [<a
href="http://localhost:8080/$logbook/$message id">$logbook:$message id</a>]
Please note that you wrote "mesage id", correct is however "message id" (two
"s"), so there is also a typo.
> Since Version 2.5.5: If ELOG is running under German, the "Zurück" Bottom is
> named "Back". Any Idee where I can change this back? ;-)
The link "Back" has been replaced upon request by "List" which is more
appropriate. So if you changed your menu with "Menu commands = ...", please
replace "Back" by "List" there. |
Re: $message id gives wrong value - Gernman traslalation of Back, posted by Ulrich Trüssel on Fri Nov 5 21:37:56 2004
|
1. thats now clear with the £message id and the work-around is ok for my
needs
2. the "bacl" link is clear and tranlated to "Liste". But I mean the back
button
in the entry and the edit mode (see picture)... ;-)
> > the "$message id" will not be replaced by the msg id, the
string "$message
> > id" will be dispalyed and used. Other substitutions as $logbook etc.
are
> > working.
> >
> > Is this a bug or did i missunderstood the manual?
>
> Well, the manual does not state that "$message id" should work for "Subst
> <attribute>" option (;-)
>
> The reason is that the message ID is available only *after* a new entry
has been
> written to the database, and the "Subst" command is evaluated *before*
an entry
> is submitted. "$message id" only works for "Thread display", "RSS
Title", "Subst
> on reply", "Subst on edit" and "Display". You should use
>
> Display KlientIn/KundIn = $Vorname $Name; P: $Telefon Privat; G: $Telefon
> Geschaft; N: $Telefon Mobil; $Landeskennung-$PLZ $Ortschaft [<a
> href="http://localhost:8080/$logbook/$message id">$logbook:$message
id</a>]
>
> Please note that you wrote "mesage id", correct is however "message id"
(two
> "s"), so there is also a typo.
>
> > Since Version 2.5.5: If ELOG is running under German, the "Zurück"
Bottom is
> > named "Back". Any Idee where I can change this back? ;-)
>
> The link "Back" has been replaced upon request by "List" which is more
> appropriate. So if you changed your menu with "Menu commands = ...",
please
> replace "Back" by "List" there. |
Re: $message id gives wrong value - Gernman traslalation of Back, posted by Stefan Ritt on Sat Nov 6 11:29:52 2004
|
> 2. the "bacl" link is clear and tranlated to "Liste". But I mean the back
> button
> in the entry and the edit mode (see picture)... ;-)
Well, if you try with the demo logbook, the "Back" button is translated
correctly, so I don't know whats wong in your case. Can you check that your
eloglang.german file is intact? |
Re: $message id gives wrong value - Gernman traslalation of Back, posted by Ulrich Trüssel on Sun Nov 7 09:49:13 2004
|
installed elog 2.5.5 agin, same effekt with "back" / "zurück". checked the
language file eloglang.german witch seem ok for me and the translations are
well done. removed then in eloglang.germen the traslation for back and checked
this: still back was viewed. reinserted the translation "Zurück" (just this
word!)and checked again: everithing looks fine, no longer back, correctly
Zurück on the button.
absolutly no idea why and whats the difference was! bus it works...
thank's stefan! :-)
> > 2. the "back" link is clear and tranlated to "Liste". But I mean the back
> > button
> > in the entry and the edit mode (see picture)... ;-)
>
> Well, if you try with the demo logbook, the "Back" button is translated
> correctly, so I don't know whats wong in your case. Can you check that your
> eloglang.german file is intact? |
Can the elog client submit an entry with a html body?, posted by Kristinn B. Gylfason on Tue Nov 2 02:51:09 2004
|
I'm running a Debian package of elog with verision number 2.5.4+r1480-1.
The revision of the elog client in this package is 1.21.
I'm using the elog client to send entries generated by a script to my
logbook. I want to format the body text of the entry using HTML, to include
links and images. When I submit the entry with the elog client it is
submited as text and not HTML.
The man page for the elog client does not mention any commandline options to
specify the formating of the entry and I have not found any info in this
forum on the issue.
Is it possible to submit an entry with a html body using the elog client? |
Re: Can the elog client submit an entry with a html body?, posted by Stefan Ritt on Tue Nov 2 17:47:43 2004
|
> Is it possible to submit an entry with a html body using the elog client?
I added a "-H" flag for that. New version of elog.c under CVS and in the next
release. |
Re: Can the elog client submit an entry with a html body?, posted by Kristinn B. Gylfason on Tue Nov 2 18:15:09 2004
|
> > Is it possible to submit an entry with a html body using the elog client?
>
> I added a "-H" flag for that. New version of elog.c under CVS and in the next
> release.
Great! Thanks.
Kristinn |
, posted by on Thu Aug 19 16:20:16 2004
|
Here are some things for your wish list:
1) elogd should report quota or disk-full problem: In case a logbook
entry cannot be saved (quota or disk full) then a message like
'Could not save last entry. Please contact administrator.' should
be displayed. Currently nothing happens. Only the submitted
entries 'vanish'.
2) default page view per user, i.e. the 'Back' link goes to
?mode=Full,summary,... depending on the user that is logged in.
Some users complained that 'Back' is not really back. Maybe
consider renaming 'Back' to 'Default View' or something.
3) (related to 1) the 'Back' link should go back to the last used mode
(full, summary, threaded,...) and not to the default mode
4) mark messages as unread/read on a per user basis: The
implementation of this might be quite involved but it would be
rather useful. One way would be to add a default attribute 'Seen
by' to each entry, which lists the login names of the users. Or
files LOGIN_NAME.has_seen can be created which contain the entry
IDs of the viewed entries for each user.
5) alignment of attribute table (using <td colspan=2> for multi line
stuff): see elog:669 :)
You can count my vote for:
- Use "and" and "or" operands in queries
|
, posted by on Fri Oct 29 20:14:17 2004
|
> 1) elogd should report quota or disk-full problem: In case a logbook
> entry cannot be saved (quota or disk full) then a message like
> 'Could not save last entry. Please contact administrator.' should
> be displayed. Currently nothing happens. Only the submitted
> entries 'vanish'.
That has been fixed in meantime.
> 4) mark messages as unread/read on a per user basis: The
> implementation of this might be quite involved but it would be
> rather useful. One way would be to add a default attribute 'Seen
> by' to each entry, which lists the login names of the users. Or
> files LOGIN_NAME.has_seen can be created which contain the entry
> IDs of the viewed entries for each user.
There is an elegant way to achieve this already now: Use an RSS reader (like
SharpReader for Windows or Straw from Linux) and subscribe to a logbook. Then don't
read the entries directly in the logbook, but read them in your RSS reader. Once you
read them, they become automatically marked read.
> 5) alignment of attribute table (using <td colspan=2> for multi line
> stuff): see elog:669 :)
Has been fixed as well.
> - Use "and" and "or" operands in queries
Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write
<str1>|<str2>
and for a "<str1> AND <str2>" one can write
<str1>.*<str2>|<str2>.*<str1>
Looks a bit complicated, but maybe some day we will get some code which rewrites
"AND" and "OR" as regular expressions. |
Re: some things for your wishlist, posted by Heiko Scheit on Sun Oct 31 20:09:31 2004
|
> > - Use "and" and "or" operands in queries
>
> Elog supports now regular expressions. So for a "<str1> OR <str2>" one can write
>
> <str1>|<str2>
>
> and for a "<str1> AND <str2>" one can write
>
> <str1>.*<str2>|<str2>.*<str1>
>
> Looks a bit complicated, but maybe some day we will get some code which rewrites
> "AND" and "OR" as regular expressions.
It seems that the quick filter searches are now (2.5.4-6) case sensitive.
Could you add an option to specify this in the config file? Or does it
exist already? |
Re: , posted by Stefan Ritt on Mon Nov 1 13:49:12 2004
|
> 2) default page view per user, i.e. the 'Back' link goes to
> ?mode=Full,summary,... depending on the user that is logged in.
> Some users complained that 'Back' is not really back. Maybe
> consider renaming 'Back' to 'Default View' or something.
I replaced the "back" link with a "list" link, hope that this makes now more sense. |
Compile of Elog , posted by Martin R. Picchio on Mon Nov 1 03:08:34 2004
|
If I make changes to the elog source, How do I re-compile it and not
distrupt the program?????? |
Re: Compile of Elog , posted by Stefan Ritt on Mon Nov 1 13:45:47 2004
|
> If I make changes to the elog source, How do I re-compile it and not
> distrupt the program??????
You first have to stop the running elogd server, then replace the executable,
then restart the server. |
, posted by on Mon Oct 25 23:16:39 2004
|
I implemented experimentally RSS feeds into Elog. Before releasing this new
addition, I would like to collect some experience with it. This forum now
supports RSS feeds, for which you can subscribe with a RSS feed reader like
Mozilla Firefox. Please give it a try and send me any feedback.
For an introduction to RSS feeds, please see
http://www.webreference.com/authoring/languages/xml/rss/intro/ |
Re: Announcement of RSS feeds, posted by Marc Neiger on Thu Nov 11 01:04:01 2004
|
Great, but what's the corresponding URL for the RSS feed itself
> I implemented experimentally RSS feeds into Elog. Before releasing this new
> addition, I would like to collect some experience with it. This forum now
> supports RSS feeds, for which you can subscribe with a RSS feed reader like
> Mozilla Firefox. Please give it a try and send me any feedback.
>
> For an introduction to RSS feeds, please see
>
> http://www.webreference.com/authoring/languages/xml/rss/intro/ |
Elog Service Terminated, posted by Geo Geo on Fri Oct 15 07:59:35 2004
|
Hi
I have a problem here which the ELOG service get terminated unexpectedly
on the Windows Server.
Is there any way to debug this problem ?
I am using the latest version of Elog and i tried the 2.5.3 version too
have this problem
Thanks! |
Re: Elog Service Terminated, posted by Geo Geo on Sat Oct 16 20:32:54 2004
|
> Hi
> I have a problem here which the ELOG service get terminated unexpectedly
> on the Windows Server.
> Is there any way to debug this problem ?
>
> I am using the latest version of Elog and i tried the 2.5.3 version too
> have this problem
>
> Thanks!
I have found the reason when will it terminate ,
When a user is not found on the server will hang in version 2.5.3 and in
version 2.5.4 it will terminate by itself as show below.
--------------logs
GET /?redir=&uname=ifcosad&upassword=jklasjd HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/vnd.ms-
powerpoint, application/vnd.ms-excel, application/msword, application/x-
shockwav
e-flash, */*
Referer: http://sinccbap2kp38.sq.com.sg:8877/
Accept-Language: en-gb
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; YComp 5.0.2.6)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: urem=0
D:\Program Files\ELOG>
-----------end of log
here is the logs . And in version 2.5.4 , when i tried to move some entries
to another db and i get a xrelloc error
GET /IFSOCC+Archive/?
Priority=_all_&cmd=Move+to&destm=IFSOCC+Current&s0=1&s1=2&s
2=3&s3=4&nsel=4 HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/vnd.ms-
powerpoint, application/vnd.ms-excel, application/msword, application/x-
shockwav
e-flash, */*
Referer: http://sinccbap2kp38.sq.com.sg:8877/IFSOCC+Archive/?select=1
Accept-Language: en-gb
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; YComp 5.0.2.6)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: urem=0; unm=ifsocc; upwd=aWZzb2Nj
xrealloc: not enough memory
Thanks !
Geo |
, posted by on Mon Oct 11 22:57:58 2004
|
Hello to all,
i'm running ELOG on FreeBSD 5.2.
We've noticed an issue where e-mail notification from ELOG seem to
have their arrival time in the future, looks like it's about 13 hours ahead.
E-mail gateway to which ELOG posts its e-mail shows this e-mail transaction:
--------------------------------------------
Received: from elogunixbox.somewhere.net ([x.x.x.x]) by
mailunixbox.somewhere.net with SMTP id <143408>; Mon, 11 Oct 2004 12:22:43
+1300
To: crypt0@somewhere.net
From: elogposter@somewhere.net
Subject: New ELOG entry
X-Mailer: Elog, Version 2.5.3
X-Elog-URL: http://elog.somewhere.net/somelogbook/47
X-Elog-submit-type: web|elog
Date: Mon, 11 Oct 2004 12:26:28 -3736512
--------------------------------------------
The last line in that log seems to have some strange time zone offset
(-3736512)
Usually you'd see a GMT+13 (New Zealand time zone on summer time).
Here's ELOG's own logs of that same e-mail delivery:
--------------------------------------------
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Mailer:
Elog, Version 2.5.3
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Elog-URL:
http://elog.somewhere.net/somelogbook/47
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Elog-
submit-type: web|elog
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} Date: Mon,
11 Oct 2004 12:26:28 -3736512
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} Content-
Type: TEXT/PLAIN; charset=US-ASCII
--------------------------------------------
I noticed that there was a post talking about ELOG on MacOSx having some
time issues, but nothing mentioning FreeBSD..
Any ideas?
Thanks to all in advance.
GL. |
, posted by on Wed Oct 13 20:48:52 2004
|
> Date: Mon, 11 Oct 2004 12:26:28 -3736512
The timezone offset (-3736512) is obtained from the "timezone" variable, which
is initialized with the tzset() function inside elogd. See "man tzset" for
details. It looks like if the timezone on your FreeBSD box is not correctly
defined.
Try to compile and execute following C program:
#include <stdio.h>
#include <time.h>
main()
{
tzset();
printf("timezone: %d\n", timezone);
}
This should print something like "timezone: -3600". If not, you might consider
defining the "TZ" environment variable. Maybe some FreeBSD expert knows some
details about this. |
Re: ELOG e-mail notifications - their arrival time is wrong, posted by G on Sun Oct 17 22:47:39 2004
|
Ok, i compiled the code below and ran it,
it prints out:
timezone: 134513644
but in BASH shell if i type DATE, then this is the output:
Mon Oct 18 09:44:00 NZDT 2004
so it does know about NZ time...
Anyone got ideas?
Thanks all.
G.
> > Date: Mon, 11 Oct 2004 12:26:28 -3736512
>
> The timezone offset (-3736512) is obtained from the "timezone" variable, which
> is initialized with the tzset() function inside elogd. See "man tzset" for
> details. It looks like if the timezone on your FreeBSD box is not correctly
> defined.
>
> Try to compile and execute following C program:
>
> #include <stdio.h>
> #include <time.h>
>
> main()
> {
> tzset();
> printf("timezone: %d\n", timezone);
> }
>
> This should print something like "timezone: -3600". If not, you might consider
> defining the "TZ" environment variable. Maybe some FreeBSD expert knows some
> details about this. |