Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon8.gif   cannot start elog, posted by harley on Thu May 27 22:35:49 2010 
    icon2.gif   Re: cannot start elog, posted by Stefan Ritt on Tue Jun 1 13:17:18 2010 
Message ID: 66833     Entry time: Tue Jun 1 13:17:18 2010     In reply to: 66832
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Mac OSX  ELOG Version: 2.7.8 
Subject: Re: cannot start elog 

harley wrote:

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

I'm not understanding why elogd cannot be found.  The same message occurs when I try to test the installation with elogd -p 8080 from the sbin directory where elogd is installed.
 
I'm using the same Makefile and elogd.cfg files that work on the old system.  My elogd and elogd.cfg files appear to be in the correct directories indicated in the Makefile:
 
#############################################################

#
# Directories for installation, modify if needed
#

ifndef PREFIX
PREFIX     = ~vulcanstaff/ELOG-Workspace
endif

ifndef MANDIR
MANDIR     = $(ROOT)$(PREFIX)/man
endif

ELOGDIR    = $(ROOT)$(PREFIX)/elog
DESTDIR    = $(ROOT)$(PREFIX)/bin
SDESTDIR   = $(ROOT)$(PREFIX)/sbin
RCDIR      = $(ROOT)$(PREFIX)/etc/rc.d/init.d

# flag for SSL support
USE_SSL    = 1

# flag for crypt() support
USE_CRYPT  =

#############################################################
 
Again, this works on the old system.  Perhaps I've looked at it for too long, but I can't figure out what's going on.  Assistance is greatly appreciated.
 
-harley

 

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

 

ELOG V3.1.5-fe60aaf