Hi,

I have an elogd server serves many logbooks.  May I know what is a good way to export or achive one its logbooks?  Thank you.

Jacky

I'm trying to set up a python rss parser to read the output from my collaboration's elog, however the elog is password protected and I cannot figure out how to have a python scrip get past the login screen.  Is there something obvious I'm missing that will allow a parser to submit a username and password? If that's too python-specific of a question for this audience, then what is the exact security method elog uses, so I can get information on that?  I've read through the documentation and either I don't know what I'm reading (likely) or I'm not looking in the right spot.

I'm trying to set up a python rss parser to read the output from my collaboration's elog, however the elog is password protected and I cannot figure out how to have a python scrip get past the login screen.  Is there something obvious I'm missing that will allow a parser to submit a username and password? If that's too python-specific of a question for this audience, then what is the exact security method elog uses, so I can get information on that?  I've read through the documentation and either I don't know what I'm reading (likely) or I'm not looking in the right spot.

Hi.

I have ELOG V2.8.0-2313 installed on a SLC 5.5 release and all works fine, Users can register them-self and I see for each of them in the passwd file:

<name>test</name>

<password>***something***</password>

....

after a '/etc/rc.d/init.d/elogd restart' the logins don't work anymore (they did before the restart)

and the passwd file changed:

<name>test</name>

<password encoding="SHA256">***something else***</password>

....

Any idea what goes wrong?

Cheers, Jack

Hi,

I have two logbooks based on the same data directory through "Subdir" option and when I add new entry in one logbook, then that entry is not visible in other logbook.

I suppose it is a bug in el_submit function, where I think the new message should be added to message index of every logbook based on the same data directory as the one, where the message was physically created. 

There is a piece of code, which I think should do this automatically

/* if other logbook has same index, update pointers */

but it seems the other logbooks does not have the same index. 

I'm new to elog and the sources are also new to me, so my guess to the ground of the problem may be wrong.

Let me know is this bug possible to fix in near future.

Best regards,

Jacek

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.