Hi,

I have been using ELOG for a while and I love it.  It is a default installation on Debian Lenny and ELOG 2.7.8.  I am having problems with the deamon script, I can stop the service by doing /etc/init.d/elog stop but I can't started.  When I do /etc/init.d/elog start I get this error: "Starting ELOG daemon: elogdCannot open "elogd.cfg": No such file or directory"

Somewhere there is a bad path to the elogd.cfg which is in "/usr/local/elog"

I would appreciate any help I can get.

Thank you.

Here is the scrip:

[code]

#!/bin/sh
# Init script for ELOG.
# Recai Oktas <roktas@omu.edu.tr>

PATH=/sbin:/bin:/usr/sbin:/usr/local/bin
DAEMON=/usr/local/sbin/elogd
NAME=elogd
DESC="ELOG daemon"

# Always run as daemon.
ARGS="-D"

# Admin might change some command line options without touching this script.
if [ -f /etc/default/elog ]; then
        . /etc/default/elog
fi

test -f $DAEMON || exit 0

set -e

case "$1" in
        start)
                echo -n "Starting $DESC: $NAME"
                start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
                        --exec $DAEMON -- $ARGS >/dev/null
                echo "."
                ;;
        stop)
                echo -n "Stopping $DESC: $NAME"
                start-stop-daemon --oknodo --stop --quiet --pidfile /var/run/$NAME.pid \
                        --exec $DAEMON -- $ARGS >/dev/null
                echo "."
                ;;
        reload)
                # Do nothing since ELOG daemon responds to
                # the changes in conffile directly.
                ;;
        restart|force-reload)
                echo -n "Restarting $DESC: $NAME"
                start-stop-daemon --stop --quiet --pidfile \
                        /var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
                sleep 1
                start-stop-daemon --start --quiet --pidfile \
                        /var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
                echo "."
                ;;
        *)
                N=/etc/init.d/$NAME
                echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
                exit 1
                ;;
esac

exit 0

[/code]

Unfortunately the Debian distribution was not done by me, so I only can guess:

• Is the executable existing under /usr/local/sbin/elogd ?
• In the start) section, I cannot find any reference to /usr/local/elog, so you maybe need something like
  ARGS="-D -c /usr/local/elog/elogd.cfg"
   

I have v2.7.7 of elog running on a OSX system running 10.6 I configured and installed about a year ago.  It's a wonderful thing to have.

I acquired another system running 10.6 to dedicate to the elog app.  I downloaded 2.7.8  and performed the following steps:

extract tarball in the desired directory

run

tar -xzvf elog-x.x.x.tar

switch to the new elog-x.x.x directory edit Makefile and elogd.cfg files as needed

to create executables

run

make

to create directories & files

run

make install

When I try to execute elog as a daemon:

elogd -c ~vulcanstaff/ELOG-Workspace/elog/elogd.cfg -D

I get the following message:

-bash: elogd: command not found

Some Linux systems don't have the current directory (".") in the search path, so you have to start it with

./elogd -c ....

or explicitly with

/usr/sbin/elogd -c ...

If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"

Note the attachment to this post.

----

Makefile has the line:

# flag for SSL support
USE_SSL    = 1

However setting USE_SSL = 0 does not prevent the openssl libraries from being used.  Same issue with USE_CRYPT.
 You have to comment them out.

Lines 76-85 of Makefile should be replaced with this:

ifdef USE_SSL
ifneq ($(USE_SSL), 0)
CFLAGS += -DHAVE_SSL
LIBS += -lssl
endif
endif

ifdef USE_CRYPT
ifneq ($(USE_CRYPT), 0)
CFLAGS += -DHAVE_CRYPT
LIBS += -lcrypt
endif
endif

Thanks,
amartin

> If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
> the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"

Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext. 
For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers 
followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however 
0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can 
easily remove the interpretation of the date, it would break the synchronization functionality and I would have to 
find some other method to pass the file date/time, which would be quite some work. So if it's not too important for 
you, I would like to keep it as it is.

> Makefile has the line:
> 
> # flag for SSL support
> USE_SSL    = 1
> 
> However setting USE_SSL = 0 does not prevent the openssl libraries from being used.  Same issue with USE_CRYPT.
>  You have to comment them out.
> 
> Lines 76-85 of Makefile should be replaced with this:
> 
> ifdef USE_SSL
> ifneq ($(USE_SSL), 0)
> CFLAGS += -DHAVE_SSL
> LIBS += -lssl
> endif
> endif
> 
> ifdef USE_CRYPT
> ifneq ($(USE_CRYPT), 0)
> CFLAGS += -DHAVE_CRYPT
> LIBS += -lcrypt
> endif
> endif

The original idea was that one outcomments the whole line, like

#USE_SSL = 1

which always worked, but I agree that your solution is more general, so I changed the official Makefile. Thanks for 
that.

> > If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
> > the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"
> 
> Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext. 
> For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers 
> followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however 
> 0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can 
> easily remove the interpretation of the date, it would break the synchronization functionality and I would have to 
> find some other method to pass the file date/time, which would be quite some work. So if it's not too important for 
> you, I would like to keep it as it is.
> 

Thank you for your response.  

I can certainly use another filename, but I'm curious why elog doesn't convert the filename "000000_000000_file.txt" to
"YYMMDD_HHMMSS_000000_000000_file.txt" when it gets uploaded.  All other files are automatically prepended with this
string.  Manually renaming the file and then editing the elog entry via text editor seems to fix the file.

thanks,
amartin

Is there a way to require a certain attribute on reply, but not on an original entry?  In some cases info. for these fields only exists on reply.

No. There is only "Preset on reply ..." and "Remove on reply...". You could for example require that attribute, preset it for new entries with some dummy value, and remove that value with "Remove on reply...". Maybe that works. 

Is there a way to merge existing entries from several logbooks into a single logbook? 

Only manually: Add "Move to" to you set of commands via "Menu commands = ...", then select one or more entries, and move them to your target logbook.  

 Got it! Thanks...

My elog server is hosted behind a firewall and I use a VPN client to connect to the network on which it is hosted.  When I'm logged into the VPN emails from elog display fine, but when I'm not connected to the VPN emails display in plain text because the email client is unable to load "default.css" since it's behind a firewall.

Is there a way to include the style information in the HTML email rather than in a separate file that's hosted on the elog server? 

That's a good idea. I will consider that for a future version. 

hello

i've tried to change the color of a cell with "cell style"

it doesn't works

by removiving "cell" in the line ,just to get "style" the color of all cell of the row change (so it works for that...)

regards

As written here: https://midas.psi.ch/elogs/Forum/66807 you need to upgrade to version 2.7.8-5 of ELOG to get this functionality. 

 You're right my verssion was the previous one

Hi,

is it possible to have as DEFAULT the font Size larger ?

Thanks

Sara

This is controlled by the FCKEditor  which is just a plug-in to ELOG. Maybe you find some information on their website: http://ckeditor.com/