When creating/updating entries in elog, excluding the main text field are 
there any limits on the size of the other fields?

many thanks

Paul

> When creating/updating entries in elog, excluding the main text field are 
> there any limits on the size of the other fields?

Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
currently set to 1500 characters. You can try to increase this and recompile,
but at some point you will produce a stack overflow and elogd will crash. So
the current length is a compromise.

- Stefan

> > When creating/updating entries in elog, excluding the main text field are 
> > there any limits on the size of the other fields?
> 
> Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> currently set to 1500 characters. You can try to increase this and recompile,
> but at some point you will produce a stack overflow and elogd will crash. So
> the current length is a compromise.
> 
> - Stefan

Thanks. Thats useful to know.

Paul

The reason for the earlier question is that we are trying to use Elog to store 
data in a form we'd need to store more 1500 characters in more than one field.

Is it possible to get around this problem by having more then one main text field 
per record?

thanks

Paul

> > > When creating/updating entries in elog, excluding the main text field are 
> > > there any limits on the size of the other fields?
> > 
> > Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> > currently set to 1500 characters. You can try to increase this and recompile,
> > but at some point you will produce a stack overflow and elogd will crash. So
> > the current length is a compromise.
> > 
> > - Stefan
> 
> Thanks. Thats useful to know.
> 
> Paul

> Is it possible to get around this problem by having more then one main text field 
> per record?

No, not at the moment. You can increase the 1500 characters by recompiling elogd, but
at some point you will hit the stack limit and elogd will crash. I plan a major
redesign with completely dynamic memory allocation, thus permitting any number of
characters on any attribute. But this will take a couple of months or so.

If I want to go to the latest CVS release, what files do I have to compile
along with the elogd.c file?  Also, do I need to use any special gcc flags
for the compilation?  Thanks.

> If I want to go to the latest CVS release, what files do I have to compile
> along with the elogd.c file?  Also, do I need to use any special gcc flags
> for the compilation?  Thanks.

You need elogd.c, mxml.c and regex.c, the Makefile you can get from CVS as well 

http://midas.psi.ch/cgi-bin/cvsweb/elog/Makefile

> > If I want to go to the latest CVS release, what files do I have to compile
> > along with the elogd.c file?  Also, do I need to use any special gcc flags
> > for the compilation?  Thanks.
> 
> You need elogd.c, mxml.c and regex.c, the Makefile you can get from CVS as well 
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/Makefile

Worked like a charm.  Thanks again.

using:
Display mode = threaded
List display = Subject, Type, Author, Date

in the config file (omitting "ID" then) rise the bug

ie, an unneeded "," is displayed after the "supposed to be printed" ID

> using:
> Display mode = threaded
> List display = Subject, Type, Author, Date
> 
> in the config file (omitting "ID" then) rise the bug
> 
> ie, an unneeded "," is displayed after the "supposed to be printed" ID

Fixed in CVS revision 1.574

Is there any way to include the text of a log message in the CSV export? 
Anyway to include a pointer to the attachment?

> Is there any way to include the text of a log message in the CSV export? 
> Anyway to include a pointer to the attachment?

The text of a log message is usually several lines long. To my knowledge, CSV
only allows single line values, that's why I excluded the text field from the
CSV export. This is different in the XML export, which supports multi-line
values. If you teach me however how multi-line values can be represented in
CSV format, I could easily add that.

As for the attachment, do you just need a name, or a URL back to the logbook?
Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
or in HTML form like <a href="http:/...">attachment</a> ?

> > Is there any way to include the text of a log message in the CSV export? 
> > Anyway to include a pointer to the attachment?
> 
> The text of a log message is usually several lines long. To my knowledge, CSV
> only allows single line values, that's why I excluded the text field from the
> CSV export. This is different in the XML export, which supports multi-line
> values. If you teach me however how multi-line values can be represented in
> CSV format, I could easily add that.
> 
> As for the attachment, do you just need a name, or a URL back to the logbook?
> Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
> or in HTML form like <a href="http:/...">attachment</a> ?

I will attempt to use an active x script in a DTS package on SQL Server to parse
the xml and load it into the database. I can see where CSV has it's limitations.

I searched and found some problems people were having compiling it on Solaris.
However I didn't see anything else.

If your using it, was it hard to get it installed and working?

I've got it running for two years now on a Sun Netra box running Solaris 9

> I searched and found some problems people were having compiling it on Solaris.
> However I didn't see anything else.

I just used the compile instructions as shown in the elog admin manual

Here the Makefile I used

#
# Simple makefile for elogd
#
# S. Ritt, May 12th 2000
# install/clean section by Th. Bullinger, Apr. 26th, 2002
#
# add "-DHAVE_CRYPT" and "-lcrypt" to use crypt() function
#

CC = gcc
LIBS =
CFLAGS = -L/usr/lib/ -ldl -lresolv -lm -ldl -lnsl -lsocket
#CFLAGS = -g -O
EXECS = elog elogd elconv
DESTDIR = /usr/local/bin
SDESTDIR = /usr/local/sbin
MANDIR = /usr/local/man

INSTALL = /usr/bin/install
RM = /bin/rm

ifeq ($(OSTYPE),solaris)
CC = gcc
#LIBS = -lsocket -lnsl
#CFLAGS =
INSTALL = /usr/ucb/install
RM = /usr/bin/rm
endif

ifeq ($(OSTYPE),darwin)
CC = cc
endif

all: $(EXECS)

%: src/%.c
        $(CC) $(CFLAGS) -o $@ $< $(LIBS)

install: $(EXECS)
        $(INSTALL) -m 0755 -o bin -g bin elog elconv $(DESTDIR)
        $(INSTALL) -m 0755 -o bin -g bin elogd $(SDESTDIR)
        $(INSTALL) -m 0644 man/elog.1 man/elconv.1 $(MANDIR)/man1/
        $(INSTALL) -m 0644 man/elogd.8 $(MANDIR)/man8/

clean:
        -$(RM) *~ $(EXECS)


> If your using it, was it hard to get it installed and working?

Not at all.
Just read the manual and it just works.
If you are having problems just read this "forum" the get the answers.

If you have a space in a logbook name and you enable password list, then 
the "List" menu option forces you to the login page each time.
The URL says "aaa+bbb", but when you do not have passwords enabled, the 
URL is "aaa bbb"

> If you have a space in a logbook name and you enable password list, then 
> the "List" menu option forces you to the login page each time.
> The URL says "aaa+bbb", but when you do not have passwords enabled, the 
> URL is "aaa bbb"

Thanks for reporting this. I fixed it in the current CVS version.

There is a problem with the 'Show Attributes' option
causing the 'Format ...' options to be ignored.

See attachment for patch.

> There is a problem with the 'Show Attributes' option
> causing the 'Format ...' options to be ignored.
> 
> See attachment for patch.

Thanks a lot. I applied your patch and committed the changes to CVS.

Hi

We have setup a elog server and would like to import a bunch of emails as
elog entries. Is there some way we can do this ? Since there are hundreds of
emails, it is not possible to post them individually as new elog entries.

Many thanks,
Anand.

Have a look at http://midas.psi.ch/elogs/Contributions/10