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]

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 ...

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

Is there anyway to restrict access so that a user can only see the log entries they post or only replies to their log entry?  I know it is possible to restrict editing to only posts they submitted, but I have a need to not even allow them to see other posts except for what they submitted and I am wondering if this is possible currently, or if this is planned, or could be planned for a future version?

Thanks,

Allen

> > 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

  Received invalid response from elogd server at http://example.org:8080/Discussion/

--- elogd.c     (revision 2294)
+++ elogd.c     (working copy)
@@ -15704,7 +15704,7 @@
          fgets(pwd, sizeof(pwd), stdin);
          while (pwd[strlen(pwd) - 1] == '\n' || pwd[strlen(pwd) - 1] == '\r')
             pwd[strlen(pwd) - 1] = 0;
-      } else if (status != 200 && status != 302) {
+      } else if (status != 200 && status != 302 && status != 404) {
          xfree(buffer);
          *strchr(str, '?') = 0;

Guest menu commands = List, Last 10, Find, Login, Help
Guest List Menu commands = List, Last 10, Find, Login, Help