> In version 2.0.4 of eLog I was having some problems with saving my > configuration file once I edited it on the web using the config. command. > I keep getting the message "Cannot open file %s: elogd.cfg". I made sure > the file was in the right directory. I dont know if I am doing something > wrong or if its a bug? The error display is certainly wrong. I fixed that and you can download the updated version at http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c As for the error, you should check the file permissions. If you run the daemon under a user which has no write access to the directory or file, you would get the described error.
> Where can I get more information about the config and themes file. I > downloaded the latest version (2.0.4) and the config file docs seem out of > date. I would like to get the icons working as well as getting the email to > work. The demo page at the elog home site shows both but I cannot find ant > references to the icons. Oops, I forgot the "IOptions" statement to documentation. Please see the updated version at http://midas.psi.ch/elog/config.html look for "IOptions". For the Email notification see the whole section "Email notification" near the bottom of the page.
Where can I get more information about the config and themes file. I downloaded the latest version (2.0.4) and the config file docs seem out of date. I would like to get the icons working as well as getting the email to work. The demo page at the elog home site shows both but I cannot find ant references to the icons.
Comiling elogd 2.0.4 under Solaris obviously fails with gcc -o elog elog.c -lsocket -lnsl gcc -o elogd elogd.c -lsocket -lnsl elogd.c: In function `ss_file_find': elogd.c:1372: `alphasort' undeclared (first use in this function) elogd.c:1372: (Each undeclared identifier is reported only once elogd.c:1372: for each function it appears in.) make: *** [elogd] Error 1 because alphasort is an ucb'ism which does not exist under SYSV ... not very portable :-(
With elog it is possible to submit messages to a password protected logbook without specifying the -u option. I.e. NO PASSWORD is necessary to submit a message. I assume it is related to the problem of expiring password-cookies while entering the message using a web browser.
In version 2.0.4 of eLog I was having some problems with saving my configuration file once I edited it on the web using the config. command. I keep getting the message "Cannot open file %s: elogd.cfg". I made sure the file was in the right directory. I dont know if I am doing something wrong or if its a bug? Mo.
> When the option 'Reverse sort = 1' is used then the first entry > is not displayed (ID=1) when threaded mode is requested. > > Probably you can see the problem using this link and switching > on reverse sort. > > http://midas.psi.ch/elogdemo/Linux/last20?mode=threaded Has been fixed in 2.0.4, have a look at http://midas.psi.ch/elogdemo/Linux/last20?mode=threaded&reverse=1
> If a message is submitted via the elog command then the reply string '> ' is only inserted in the first line if a reply is made. > This message was submitted with the following commandline: > elog -v -h midas.psi.ch -p 80 -s elogdemo -l Forum -a "Icon=icon4.gif" - a "Author=Heiko Scheit" -a "Author Email=h.scheit@mpi-hd.mpg.de" - a "Subject=elog submit problem" "...Message-text..." > Please press the reply button to see the problem. Has been fixed in 2.0.4 (as you can see from this entry). Please make sure not to submit too long lines via "elog". For browser submissions, the line length is limited to 78 characters, but not for "elog" submissions.