Newly installed elog gives this response when I try to submit a new record:

New entry cannot be written to directory "./logbooks/Linux/" 
Please check that it exists and elogd has write access

I started the daemon.  I've not yet assigned passwords -- just checking
things out.  How can I create this access to my own directory?

I'm running ELOG on a seperate Windows Servers.

When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"

If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG.

Can anyone tell me why I get this error?

==============================

Here is the command & output:

c:\Program Files (x86)\ELOG>elogd -m

Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical

Retrieving entries from "http://166.22.64.201/System Log"...

Error sending local entry: Error transmitting message

I'm running ELOG on a seperate Windows Servers.

When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"

If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG.

Can anyone tell me why I get this error?

==============================

Here is the command & output:

c:\Program Files (x86)\ELOG>elogd -m

Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical

Retrieving entries from "http://166.22.64.201/System Log"...

Error sending local entry: Error transmitting message

> I got elog 2.3.9 running on FreeBSD 5.1 successfully,
> I compiled elog on a redhat box and then just copied over all the files to 
> the FreeBSD box and ELOG just ran with no issues.
> It's been running under heavy use for at least a month now.

FYI- the default "make" on FreeBSD is BSD, not GNU.

The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
package) and type "gmake".  That's all it took for me to build a freshly
downloaded copy on 5.1 not 5 minutes ago.

Hello,

   Thank you for such a great piece of software!

   When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know there
is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text' field?

Thank you again,
   - Dan

That would be a lot of effort for very little gain. I appreciate your detailed response. 

Thank you,
   - Dan

> > Hello,
> > 
> >    Thank you for such a great piece of software!
> > 
> >    When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know 
> there
> > is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text' 
> field?
> > 
> > Thank you again,
> >    - Dan
> 
> Decoding HTML (or ELCode which translates to HTML) in the summary field is difficult, since the text is 
> truncated. 
> Assume you have some code like
> 
> Text
> <b>Text
>   <i>Text
> ----- cut here
> </i>
> </b>
> 
> Sot he bold <b> and italics <i> tags are opened, but closed after the cutting line. In that case the whole page 
> might render wrongly, because everything after the summary text will be displayed in bold and italics. To fix this I 
> would have to scan the HTML code and close all open tags "by hand". But since there are very many possibilities, 
> especially if one used multi-column tables, this is almost impossible without writing my own HTML parser which is 
> beyond the scope of elog. So the only clean solution I have found so far is to strip off all HTML formatting and 
> just showing plain text there.