> > Just compiled 1.410 and have run into an issue that *may* have been
> > introduced in 1.393.
> > 
> > Config file directives such as "Welcome title" could be very long strings. 
> > After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> > counted the actual chars, I suspect that the truncation happens at 1024
> > characters.  The procedure 'getcfg' has a declared passed paramater "int
> > vsize". 
> 
> Actually before 1.393 you got a buffer overflow if any string in the
> configuration file was longer than 500 chars, so it's a miracle that your elogd
> did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
> such crashes. To satisfy your need for a long Welcome title, I increased the
> string size for that particular case to 10000 chars. Hope this is enough.

Hmmm, it is a wonder.  Our welcome text was not significantly longer (about 20
chars longer) so perhaps . . . ?

Thanks, will recompile and report back.

I have a question about ELOG. Let's say after the user finishes his shift 
and passess on to the next user on duty. A staff member would want to look 
through the entries and vet them. The staff could lock the entries to 
maintain integrity of the information. How can that be done with ELOG? Can 
you enlighten me. Thank u.

One possibility is to use the option "Restrict edit time = <hours>". This way
an entry can only be edited let's say 8 hours after it has been created.

Another way is to maintain two logbooks, a "scratch" logbook and an "archive"
logbook. Users would put their entries into the scratch logbook, the staff
would examine it and move them to the archive logbook, where all users only
have read access to. To move entries between logbooks, you have to put the
"Move to" command in the configuration file like:

Menu commands = Back, New, Edit, Delete, Reply, Find, Move to, Config, Help

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!

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

> > I have a problem here which the ELOG service get terminated unexpectedly
> > on the Windows Server.
> > Is there any way to debug this problem ?
> 
> One can start the elogd server manually. So stop the service, and start 
> 
> c:\program files\elogd\elogd.exe -v
> 
> The "-v" flag shows all network traffic between the server and the browser. So
> maybe the last conversation before the crash can tell us something. Make a
> screendump of it and send it to me.

Hi 
It says not enough memory ..
May i know what is the min config ? i am running on a server with 512mb of ram.

Below is the screen dump , last action , i am doing a move .
regards


GET /IFSOCC%20Archive/?Priority=_all_&cmd=Move+to&destm=IFSOCC+Current&s0=2&s1=1
&nsel=2 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%20Archive/?select=1
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461; YComp 5.
0.0.0)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: SMSESSION=gwcUsAfDyITnesMpbzOdnbiETbAhZ1hysT2HnwE7WfO6jIHkENkdIQ+CAIgsw6
Q5mcqulHlb/0oMZFmquKY/2EEVRKqZ/lVAhiAfjYw7zN3ET1D4xULgAzNGwMp2bZjBAVrlnyWr65ffCc
9OpoiyMeOQVbGmp62TAxTRCoRBcp6r/h0QZzyVQiMt7BOU5mvq1t7WzJuEzlGoNoes7R0iKImJkIfPIu
l0IETa6Jy/n+BdZ+dYsk0lpkZD+snvc9I/kvDTOo9OOYjhs40+ZYkT++/c77ngivzjO5/0KyMnD7KbZF
ZbkyMaNmKYc8y4tnwLk652E1K++D64tVdV/5i+C6F1LktT6wPDDFrCxpVtzNawW7XAb+U38LBUsS6KbZ
XOYOLnYDrB3DUz40Xxzcz/w5k0AH55SlxqWu3r+3qx5X1qB+juyiEXiLcWfNRH2AWmGtAGYyrXbQa2V+
MgRDW8Gf/h4Gp1i8HtQt+5FYa9lWrTkwH/SDpkTVgvdqqoxjHHBAVuv4sqDHSrYlkbFuvR3hnZSZANaz
V1GOT6J5xhwmQvBDl2MeJgUOYVEr1qXmhXDw3Qkw0Q34JnaGUHp61mvZr8WyagqrZIldQTgUEKHcqlT1
GkRESynnF5GxUBKpOvxsR3EtNZUSQL1yeqSavAnphTgsuefSn2FMVGaPpDPbgzEFoLDbZlAhwT6DOGMO
guHDS2ooxyHLDKAS/Oywzdvrq+yml1ruPrxVcxe+i698tbLlkcUR2d170OYbxKr57W6harI0MnhmkTeC
Fby+2vsO+ysiCP/bDJ5LcjmUlGQ/eoaFOdwcY+utasbMwfa1BQlNmG1cnie9+Y2q9u+fX8L8Ucd6bxAf
A/bvw3X5FOAuIptdqpgrm+Ol4B6fjFyD9SSdZQF6ysnN1Loo71YnmA5aQPzlOkcdnG; urem=0; unm=
ifsocc; upwd=aWZzb2Nj


xrealloc: not enough memory

> 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