This problem has been fixed in version 2.5.4-6

Thi

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/

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/

To subscribe to a logbook, enter following URL into your RSS reader:

http://<your-elog-host.domain>/<logbook>/elog.rdf

From the newest Mozilla Firefox browser, you can also click on the RSS box at
the lower right corner of the browser (see attachment).

> > 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.

Here is the screen dump after we perform a deletion .
Another my the other thread , i show another dump when a move is perform

regards

GET /IFSOCC+Current/1?cmd=Delete&nextmsg=0&confirm=Yes 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+Current/1?cmd=Delete
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: urem=0; unm=ifsocc; upwd=dHBmc3Bk; SMSESSION=uvdhD3MUFAkDID0huNAnYhdoJxb
R74QgLwDYms+cAciPxtHlh0AIjpAqlgu6zcCeRzGLP3h7N/quulR8Z3KTWG0GQ7TQ9hdggdHTre8aoUW
YbAdTKbkWCJS/mDrfZbspmu/SiA0l4z1UEF7VAq79h78/ErlnUZPmQdbSacqYhD2Np3zqfy1GyMUtqGu
W2IW+iy5M4e7d6cIt9wkr5VmezTkmfzf8lE3RiYhE/bkjL7xBkDefFY/6tBcS28zoqBW1LhqZVnkq9FS
l5MS0vKiTDmiWusHkaD9iRaq1Gmk0lhzzvoQQ8n9ZD3ICzWAqEifRvMoqEWs1AkRA7ghEI6ONg27ffI+
F32gqXZqY7Je3I7tZOl2e4br2biwqRaQo8Rc2wztY4XxOaxdQVcbbzy1pcz9yRU6c+UTPaTNVj91o/mD
Cv+lojTVB6i6AVEqa7rgSObxGmcvYsmEIzFUqVwhgTkAYlCLMLp7Fy1HzWVj5u14bYhq53kGJaqa+SKE
FejtwlUWj7cgTkNLubCAStWUyAYwNeqDyVaYFz6HapDiXrpRNtn0cydS2zcJ1kfynloBWBp1f1vbW3U6
bCZEp6GQOUXSyWuGyP/k/umB9JrfBkstCoiou3pIWNG1Sf7Ni0+vLyaZFIt5YEDdkb3TXIZlIUjAFOsk
t3KVnfdtomNoE6cvsFIG9kJxCr6b7TIJAS+RxGQUYmHCK6R1oIUx9ZL8qXnjvDY2dGjyZg5aCYUx8smh
3DOO7WykAqEiPcNt7I1K4kwX1E+Eu5d/Y5X+qEZ553H4wNnlA/nXod374ksQ2AFqK9HVomVIi9AJg9sO
6ygrsRDArVPMjnzKatCb8yNTnor4dphH18XoANpvbvkmIUSRh+gwHNznLGE1blbfiOrxhXNVBVmfl1iU
Yts2NTkEQu4xwnooDA7YZ


xrealloc: not enough memory

> > 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.

Here is the screen dump after we perform a deletion .
Another my the other thread , i show another dump when a move is perform

regards

GET /IFSOCC+Current/1?cmd=Delete&nextmsg=0&confirm=Yes 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+Current/1?cmd=Delete
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: urem=0; unm=ifsocc; upwd=dHBmc3Bk; SMSESSION=uvdhD3MUFAkDID0huNAnYhdoJxb
R74QgLwDYms+cAciPxtHlh0AIjpAqlgu6zcCeRzGLP3h7N/quulR8Z3KTWG0GQ7TQ9hdggdHTre8aoUW
YbAdTKbkWCJS/mDrfZbspmu/SiA0l4z1UEF7VAq79h78/ErlnUZPmQdbSacqYhD2Np3zqfy1GyMUtqGu
W2IW+iy5M4e7d6cIt9wkr5VmezTkmfzf8lE3RiYhE/bkjL7xBkDefFY/6tBcS28zoqBW1LhqZVnkq9FS
l5MS0vKiTDmiWusHkaD9iRaq1Gmk0lhzzvoQQ8n9ZD3ICzWAqEifRvMoqEWs1AkRA7ghEI6ONg27ffI+
F32gqXZqY7Je3I7tZOl2e4br2biwqRaQo8Rc2wztY4XxOaxdQVcbbzy1pcz9yRU6c+UTPaTNVj91o/mD
Cv+lojTVB6i6AVEqa7rgSObxGmcvYsmEIzFUqVwhgTkAYlCLMLp7Fy1HzWVj5u14bYhq53kGJaqa+SKE
FejtwlUWj7cgTkNLubCAStWUyAYwNeqDyVaYFz6HapDiXrpRNtn0cydS2zcJ1kfynloBWBp1f1vbW3U6
bCZEp6GQOUXSyWuGyP/k/umB9JrfBkstCoiou3pIWNG1Sf7Ni0+vLyaZFIt5YEDdkb3TXIZlIUjAFOsk
t3KVnfdtomNoE6cvsFIG9kJxCr6b7TIJAS+RxGQUYmHCK6R1oIUx9ZL8qXnjvDY2dGjyZg5aCYUx8smh
3DOO7WykAqEiPcNt7I1K4kwX1E+Eu5d/Y5X+qEZ553H4wNnlA/nXod374ksQ2AFqK9HVomVIi9AJg9sO
6ygrsRDArVPMjnzKatCb8yNTnor4dphH18XoANpvbvkmIUSRh+gwHNznLGE1blbfiOrxhXNVBVmfl1iU
Yts2NTkEQu4xwnooDA7YZ


xrealloc: not enough memory

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.

Ok,