is there any way to get a larger text box to type in when making a new post?
the default box is rather small and you have to scroll up and down when
making a new post or editing an existing one.

once the post is submitted, the display goes to a larger box, but the text
only takes up the left side of the page. seems the only way to get it to go
all the way to the right is to make everything html and submit it that way.

can the normal text look like the html does without submitting it as html?

> is there any way to get a larger text box to type in when making a new post?
> the default box is rather small and you have to scroll up and down when
> making a new post or editing an existing one.

Message width = <number of characters>
Message height = <number of lines>
 
> can the normal text look like the html does without submitting it as html?

No. 

> > is there any way to get a larger text box to type in when making a new post?
> > the default box is rather small and you have to scroll up and down when
> > making a new post or editing an existing one.
> 
> Message width = <number of characters>
> Message height = <number of lines>
>  
> > can the normal text look like the html does without submitting it as html?
> 
> No. 

thanks stefan. it looks like it was right in front of my face the whole time (on
the elogd.cfg syntax page). but, somehow i missed it.

Since updating to version 2.5.8 we have been having problems with the elogd 
service crashing whenever anyone attempts to log out. We are using stunnel 
4.09 on a Win 2k system.

When someone tries to log out of e-log from their desktop the machine 
hosting the service throws an error popup wanting to report to Microsoft. 
The error signature has the following information:

szAppName: elogd.exe
szAppVer: 0.0.0.0
szModName: elogd.exe
szMidVer: 0.0.0.0
offset: 0003586a

Clicking to get the technical information it wants to send it shows these 
two file names:

C:\DocumentsandSettings\krobinde\LOCALS~1\temp\WER6F.tmp.dir00
\elogd.exe.mdmp
C:\DocumentsandSettings\krobinde\LOCALS~1\temp\WER6F.tmp.dir00\appcompat.txt

Let me know if there is any further information you need.

It's hard to tell the problem from what you report. Have you tried the latest
release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
some problems with the password file in 2.5.8 versions prior to patch level 6.

> It's hard to tell the problem from what you report. Have you tried the latest
> release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
> some problems with the password file in 2.5.8 versions prior to patch level 6.

Yes, I am up to date with the latest version (2.5.8-6).

What other information can I provide that might assist in diagnosing this?

> What other information can I provide that might assist in diagnosing this?

Please send me your elogd.cfg configuration file.

> > What other information can I provide that might assist in diagnosing this?
> 
> Please send me your elogd.cfg configuration file.

Stefan - I am having the exact same problem as outlined here. I sent you an
email with a somewhat complicated config file. Attached to this message is a
much simpler one. 

With this file, if you remove the B5 server (remove it from top group a2, and
remove the [b5] entry) the crash does not happen. If the B5 server (or any
additional server) is in the file, then the problem occurs.

For me, there are 3 places where the crash happens:
- on logout
- when an invalid username/password is used to login
- when you login to A1, then try to go to A2

This is happening on elog v2.5.9-1 (built May 2, 2005, 12:17:18 revision 1.642)

I have tried on windows 2000 and 2003 servers, and it seems to happen on both of
them.

Matt

Another quick update on this, it looks like the bug was introduced in version
2.5.8-2 built Mar 30 2005, 11:04:33, revision 1.611

version 2.5.8-1 built Mar 21 2005, 17:28:54, revision 1.592 does not exhibit the
behavior.


Matt

> Since updating to version 2.5.8 we have been having problems with the elogd 
> service crashing whenever anyone attempts to log out. We are using stunnel 
> 4.09 on a Win 2k system.

This problem has finally been identified and fixed. Please download the newest
version 2.5.9-2 which contains this fix.

> > Since updating to version 2.5.8 we have been having problems with the elogd 
> > service crashing whenever anyone attempts to log out. We are using stunnel 
> > 4.09 on a Win 2k system.
> 
> This problem has finally been identified and fixed. Please download the newest
> version 2.5.9-2 which contains this fix.

I will get right on this. Thank you for your efforts!

What is the recommended version of gcc to use with elog 2.5.9?  I searched
the discussion database but found nothing pertaining to this. 

Thanks  

> What is the recommended version of gcc to use with elog 2.5.9?  I searched
> the discussion database but found nothing pertaining to this. 

Well, the same code compiles on gcc and on Visual C++ under Windows, so
hopefully there is no dependence on the gcc version (;-)

I use gcc 3.2.3 on Scientific Linux 3.03.

> > What is the recommended version of gcc to use with elog 2.5.9?  I searched
> > the discussion database but found nothing pertaining to this. 
> 
> Well, the same code compiles on gcc and on Visual C++ under Windows, so
> hopefully there is no dependence on the gcc version (;-)
> 
> I use gcc 3.2.3 on Scientific Linux 3.03.

I ask because I get a dependency that I did not have before with 2.5.3. 
Compiling with my same 'ole gcc 2.95.2 I see that I now need mxml.h and
strlcpy.h.  Trying to compile under gcc 3.4 results in all kinds of errors.

> I ask because I get a dependency that I did not have before with 2.5.3. 
> Compiling with my same 'ole gcc 2.95.2 I see that I now need mxml.h and
> strlcpy.h.  Trying to compile under gcc 3.4 results in all kinds of errors.

mxml.h and strlcpy.h are part of the elog tar ball. When untar'ed, they get copied
into a separate directory:

...
-rwxr-xr-x ritt/lke      15090 2005-05-09 13:09:54 elog-2.5.9/eloglang.japanese
-rwxr-xr-x ritt/lke      17587 2005-05-09 13:09:54 elog-2.5.9/eloglang.spanish
drwxr-xr-x ritt/lke          0 2005-05-09 13:09:54 mxml/
-rwxr-xr-x ritt/lke      45577 2005-05-09 13:09:54 mxml/mxml.c
-rwxr-xr-x ritt/lke       2198 2005-05-09 13:09:54 mxml/strlcpy.c
-rwxr-xr-x ritt/lke       4359 2005-05-09 13:09:54 mxml/mxml.h
-rwxr-xr-x ritt/lke        567 2005-05-09 13:09:54 mxml/strlcpy.h

I have right now no access to 3.4. Once I get it, I will address the errors
occuring there.

> > I ask because I get a dependency that I did not have before with 2.5.3. 
> > Compiling with my same 'ole gcc 2.95.2 I see that I now need mxml.h and
> > strlcpy.h.  Trying to compile under gcc 3.4 results in all kinds of errors.
> 
> mxml.h and strlcpy.h are part of the elog tar ball. When untar'ed, they get copied
> into a separate directory:
> 
> ...
> -rwxr-xr-x ritt/lke      15090 2005-05-09 13:09:54 elog-2.5.9/eloglang.japanese
> -rwxr-xr-x ritt/lke      17587 2005-05-09 13:09:54 elog-2.5.9/eloglang.spanish
> drwxr-xr-x ritt/lke          0 2005-05-09 13:09:54 mxml/
> -rwxr-xr-x ritt/lke      45577 2005-05-09 13:09:54 mxml/mxml.c
> -rwxr-xr-x ritt/lke       2198 2005-05-09 13:09:54 mxml/strlcpy.c
> -rwxr-xr-x ritt/lke       4359 2005-05-09 13:09:54 mxml/mxml.h
> -rwxr-xr-x ritt/lke        567 2005-05-09 13:09:54 mxml/strlcpy.h
> 
> I have right now no access to 3.4. Once I get it, I will address the errors
> occuring there.

Ah, now I need to figure out how to pickup the new includes.  
BTW, personally I wouldn't take my word regarding the 3.4 errors -- I was simply
trying an alternative version and it is likely that the way ours is configured is the
problem.

Thanks!

> > > I ask because I get a dependency that I did not have before with 2.5.3. 
> > > Compiling with my same 'ole gcc 2.95.2 I see that I now need mxml.h and
> > > strlcpy.h.  Trying to compile under gcc 3.4 results in all kinds of errors.
> > 
> > mxml.h and strlcpy.h are part of the elog tar ball. When untar'ed, they get copied
> > into a separate directory:
> > 
> > ...
> > -rwxr-xr-x ritt/lke      15090 2005-05-09 13:09:54 elog-2.5.9/eloglang.japanese
> > -rwxr-xr-x ritt/lke      17587 2005-05-09 13:09:54 elog-2.5.9/eloglang.spanish
> > drwxr-xr-x ritt/lke          0 2005-05-09 13:09:54 mxml/
> > -rwxr-xr-x ritt/lke      45577 2005-05-09 13:09:54 mxml/mxml.c
> > -rwxr-xr-x ritt/lke       2198 2005-05-09 13:09:54 mxml/strlcpy.c
> > -rwxr-xr-x ritt/lke       4359 2005-05-09 13:09:54 mxml/mxml.h
> > -rwxr-xr-x ritt/lke        567 2005-05-09 13:09:54 mxml/strlcpy.h
> > 
> > I have right now no access to 3.4. Once I get it, I will address the errors
> > occuring there.
> 
> Ah, now I need to figure out how to pickup the new includes.  
> BTW, personally I wouldn't take my word regarding the 3.4 errors -- I was simply
> trying an alternative version and it is likely that the way ours is configured is the
> problem.
> 
> Thanks!


Ok, now I see the issue - the tar extract created the mxml directory in the root (not
under the created directory elog-2.5.9).  Is there a reason why these includes are not
placed in the src dir like the regex.h/.c include?

> > > > I ask because I get a dependency that I did not have before with 2.5.3. 
> > > > Compiling with my same 'ole gcc 2.95.2 I see that I now need mxml.h and
> > > > strlcpy.h.  Trying to compile under gcc 3.4 results in all kinds of errors.
> > > 
> > > mxml.h and strlcpy.h are part of the elog tar ball. When untar'ed, they get copied
> > > into a separate directory:
> > > 
> > > ...
> > > -rwxr-xr-x ritt/lke      15090 2005-05-09 13:09:54 elog-2.5.9/eloglang.japanese
> > > -rwxr-xr-x ritt/lke      17587 2005-05-09 13:09:54 elog-2.5.9/eloglang.spanish
> > > drwxr-xr-x ritt/lke          0 2005-05-09 13:09:54 mxml/
> > > -rwxr-xr-x ritt/lke      45577 2005-05-09 13:09:54 mxml/mxml.c
> > > -rwxr-xr-x ritt/lke       2198 2005-05-09 13:09:54 mxml/strlcpy.c
> > > -rwxr-xr-x ritt/lke       4359 2005-05-09 13:09:54 mxml/mxml.h
> > > -rwxr-xr-x ritt/lke        567 2005-05-09 13:09:54 mxml/strlcpy.h
> > > 
> > > I have right now no access to 3.4. Once I get it, I will address the errors
> > > occuring there.
> > 
> > Ah, now I need to figure out how to pickup the new includes.  
> > BTW, personally I wouldn't take my word regarding the 3.4 errors -- I was simply
> > trying an alternative version and it is likely that the way ours is configured is the
> > problem.
> > 
> > Thanks!
> 
> 
> Ok, now I see the issue - the tar extract created the mxml directory in the root (not
> under the created directory elog-2.5.9).  Is there a reason why these includes are not
> placed in the src dir like the regex.h/.c include?


Ack, ok, I moved the includes into src and tried re-compiling -- and received several
"undefined symbol" errors from the linker.  Clearly the libraries cannot be moved into src?

> Ok, now I see the issue - the tar extract created the mxml directory in the root (not
> under the created directory elog-2.5.9).  Is there a reason why these includes are not
> placed in the src dir like the regex.h/.c include?

Yes. I use these files in several other projects as well, and want to maintain only a
single copy. So I have

elogd-x.x.x/
elogd-x.x.x/src/
....
mxml/
mxml/strlcpy.h
mxml/strlcpy.c
mxml/mxml.c
mxml/mxml.c
...
other-project-x.x.x/
other-project-x.x.x/

So both elogd and "other-project" can use strlcpy.c and mxml.c. If I would copy it to
elogd-x.x.x/src and fix a bug there, "other-project" would use a separate copy and not
profit from the bug fix. So I would have to mainain verious copies of the same file, which
make things complicated. I compile everything also under windows, so I cannot use soft
links. If there is a better way of how to do it, please let me know.

[ritt@pc5082 /tmp]$ tar -xzvf elog-2.5.9-2.tar.gz
elog-2.5.9/
elog-2.5.9/doc/
elog-2.5.9/doc/adminguide.html
...
mxml/
mxml/mxml.c
mxml/strlcpy.c
mxml/mxml.h
mxml/strlcpy.h
[ritt@pc5082 /tmp]$ cd elog-2.5.9
[ritt@pc5082 elog-2.5.9]$ make
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elog src/elog.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o regex.o src/regex.c
... skipping warnings ...
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o mxml.o ../mxml/mxml.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o strlcpy.o ../mxml/strlcpy.c
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -I../mxml -o elogd src/elogd.c regex.o
mxml.o strlcpy.o
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elconv src/elconv.c
[ritt@pc5082 elog-2.5.9]$

--------------
No undefined functions here. I guess you have an old Makefile? Just use the complete tar
package from the last version.

> [ritt@pc5082 /tmp]$ tar -xzvf elog-2.5.9-2.tar.gz
> elog-2.5.9/
> elog-2.5.9/doc/
> elog-2.5.9/doc/adminguide.html
> ...
> mxml/
> mxml/mxml.c
> mxml/strlcpy.c
> mxml/mxml.h
> mxml/strlcpy.h
> [ritt@pc5082 /tmp]$ cd elog-2.5.9
> [ritt@pc5082 elog-2.5.9]$ make
> gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elog src/elog.c
> gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o regex.o src/regex.c
> ... skipping warnings ...
> gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o mxml.o ../mxml/mxml.c
> gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -c -o strlcpy.o ../mxml/strlcpy.c
> gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -I../mxml -o elogd src/elogd.c regex.o
> mxml.o strlcpy.o
> gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -o elconv src/elconv.c
> [ritt@pc5082 elog-2.5.9]$
> 
> --------------
> No undefined functions here. I guess you have an old Makefile? Just use the complete tar
> package from the last version.

Ok, now I have it.  Old Makefile because I had to perform some deletions to make "make" work
right under Solaris.  Basically, I took out the ifdef structures - "make" was blowing up on
these.  Everything now compiles perfectly -- don't change anything.  Thanks for that last pointer.

Steve

Just upgraded from stable running 2.5.2-2 to 2.5.9-2 in case of the usable
Duplicate function. After the problem discribed below i made a new, clean
installation again and played araound with the demo logbook, copying my
testlogbook (part of a real used and under 2.5.2-2 working logbook) into the
demo cfg file. 

ia figured out two serious problems:

1. If I copy the following section to the global into the demo lgbook,
elogd.exe crashes emediatly ewhile starting as a prozess:

[global]
Language = German
Theme = default
logbook tabs = 1
main tab = INHALT
welcome title = <b><big>Ulrich Rolf Trüssel</big></b>
Adressverwaltung
(Geschäft & Privat)
Mensch-Tier
Coaching&trade;&nbsp;&nbsp;-&nbsp;&nbsp;Mensch-Hund
Coaching&trade;
Interessengemeinschaft Familienhund&reg; - Regionalgruppe
Zentralschweiz
Lorenz Tierschule
port = 8080
Theme = default
Message Width = 100
Message Height = 25
Filtered browsing = 1
Suppress default = 2
Suppress Email on Edit = 0
Email Format = 0
Filtered browsing = 1
HTML default = 3
Reverse sort = 1

2. problem (the ting) that made me playing with teh demo cfg:
There are totally 8 logbooks running, but just one has this strange problem
of not giving a link to to the datasets in full and summary mode. I cutted
down all the stuff back to this only lines:

[Adresse2]
Attributes = Kundensegment, Duzis, Hauptadresse, Selektion, Sperre, Adresse,
Unterlagenversand, Empf. gegeben, Gruppe, Mitglied, URT, IGFH, Letzte
Anmeldung, IGFH Gruppe, IGFH JB, Anrede, Titel, Briefanrede, Vorname, Name,
Firma, Abteilung, Adresse Zusatz, Strasse, Landeskennung, PLZ, Ortschaft,
Postfach, Postfach PLZ, Postfach Ort, Telefon Geschäft, Telefon Privat,
Telefax, Telefon Mobil, EMail, HomePage, Funktion, Beruf, Geburtstag, Name
Hund, Rasse, Sex, Wurfdatum, Anmeldung, Impfbüchlein, Welpenkurs,
Erziehungskurs, Hundesport, Bestätigung, OCCH LN, Andere Kurse, Weitere
Hunde/Tiere, Referenzen, KlientIn/KundIn
List Display = Name, Vorname

and got still the same problem. if i create a new logbook it will works,
also ut works under 2.5.2-2 but not longer under 2.5.3 up (even not
2.5.9-2). any idea? mening this may be a VERY basic logbook... trued with
list display etc. around, nothinh happen. Need to go back to 2.5.2-2 where
this wasn't a problem? 

thanjs for any idea of this to problems...

Hi,

I would like to have the author email addresses listed only for users which
have logged in, but not for guest users. In the elogd.cfg file I have:

Attributes = Author, Author Email, Category, Subject
Guest Display = Author, Category, Subject, Text

But these attributes

  ID Date Author Author Email Category Subject Text

are shown also when visting the logbook as a guest. For the guests I would
like to show only these attributes

  ID Date Author Category Subject Text

Any ideas what I am doing wrong or why this does not work?

Johan

> I would like to have the author email addresses listed only for users which
> have logged in, but not for guest users. In the elogd.cfg file I have:
> 
> Attributes = Author, Author Email, Category, Subject
> Guest Display = Author, Category, Subject, Text
> 
> But these attributes
> 
>   ID Date Author Author Email Category Subject Text
> 
> are shown also when visting the logbook as a guest. For the guests I would
> like to show only these attributes
> 
>   ID Date Author Category Subject Text
> 
> Any ideas what I am doing wrong or why this does not work?

Guest List Display = Author, Category, Subject, Text
      ^^^^

- Stefan

> > I would like to have the author email addresses listed only for users which
> > have logged in, but not for guest users. In the elogd.cfg file I have:
> > 
> > Attributes = Author, Author Email, Category, Subject
> > Guest Display = Author, Category, Subject, Text
> > 
> > But these attributes
> > 
> >   ID Date Author Author Email Category Subject Text
> > 
> > are shown also when visting the logbook as a guest. For the guests I would
> > like to show only these attributes
> > 
> >   ID Date Author Category Subject Text
> > 
> > Any ideas what I am doing wrong or why this does not work?
> 
> Guest List Display = Author, Category, Subject, Text
>       ^^^^
> 
> - Stefan

Hi Stefan,

Thanks for the prompt answer and sorry for not reading the docs carefully enough.
The "Guest List Display" is of course what I should use. It works perfectly. And
thanks for the fantastic and very useful ELOG package!

Johan