| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66034
|
Wed Nov 5 11:52:12 2008 |
 | T. Ribbrock | emgaron+elog@ribbrock.org | Info | Linux | 2.7.5 | Re: Installation problems |
> > 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> > out that line).
> >
> > 3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
> > to "echo ").
>
> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain.
I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old Debian
one and working my way up till 2.7.5). Maybe you could add the Debian /etc/init.d/elog script to the "contrib"
directory, with a suitable note in the README or something like that? That script has not changed in a long time and
is still functional - and doing so would make it easier for people who would like to install elog on a Debian (or
Debian-based, e.g. Ubuntu) system. I'll attach the script.
Regards,
Thomas |
| Attachment 1: elog
|
#!/bin/sh
# Init script for ELOG.
# Copyright © 2003, 2005 Recai Oktaş <roktas@omu.edu.tr>
#
# Licensed under the GNU General Public License, version 2.
# See the file `http://www.gnu.org/copyleft/gpl.txt'.
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/elogd
NAME=elogd
DESC="ELOG daemon"
test -f $DAEMON || exit 0
set -e
# Admin should be able to lock some options.
if [ -f /etc/default/elog ]; then
. /etc/default/elog
fi
# To be in the safe side, the followings should be always defined.
PIDFILE=${PIDFILE:-/var/run/$NAME.pid}
CONFFILE=${CONFFILE:-/etc/elog.conf}
# Add the options to argument list only if defined previously. Since
# some options may also be present in the conffile, we couldn't preset
# those options which would otherwise overwrite the settings in the
# conffile. Also note that, all have reasonable compiled-in defaults.
ARGS="${PIDFILE+"-f $PIDFILE"} \
${CONFFILE+"-c $CONFFILE"} \
${LOGBOOKDIR+"-d $LOGBOOKDIR"} \
${RESOURCEDIR+"-s $RESOURCEDIR"} \
${PORT+"-p $PORT"} \
${HOST+"-n $HOST"} \
${VERBOSE+"-v"}"
# Always run as a daemon.
ARGS=`echo $ARGS -D`
case "$1" in
start)
echo -n "Starting $DESC: "
start-stop-daemon --start --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $ARGS 2>&1
sleep 1
if [ -f "$PIDFILE" ] && ps h `cat "$PIDFILE"` >/dev/null; then
echo "$NAME."
else
echo "$NAME failed to start; check syslog for diagnostics."
exit 1
fi
;;
stop)
echo -n "Stopping $DESC: $NAME"
start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \
--exec $DAEMON -- $ARGS 2>&1
echo "."
;;
reload)
# Do nothing since ELOG daemon responds to
# the changes in conffile directly.
;;
restart|force-reload)
$0 stop
sleep 1
$0 start
if [ "$?" != "0" ]; then
exit 1
fi
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac
exit 0
# vim:ai:sts=8:sw=8:
|
|
66037
|
Mon Nov 10 13:05:21 2008 |
 | Yoshio Imai | | Info | Linux | 2.7.5 | elog init script |
Notice that the following is not true when editing the config file outside of the administrator's "Config" page:
reload)
# Do nothing since ELOG daemon responds to
# the changes in conffile directly.
;;
In our installation, the sysadmin has therefore added the following section for the reload) part of the init script:
reload)
if [ -f $PIDFILE ]; then
echo -n "$DESC to reread config file ... "
kill -HUP `cat "$PIDFILE"`
echo "done"
else
echo "No $PIDFILE found!"
fi
;;
|
|
66041
|
Tue Nov 11 16:45:04 2008 |
 | Kester Habermann | kester.habermann@gmail.com | Bug report | Other | 2.7.5 | elogd dies after receiving second SIGHUP |
elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
This was observed on Solaris 10 (SPARC).
The documentation states that elogd should re-read configuration after receiving SIGHUP. |
|
66043
|
Thu Nov 13 13:23:32 2008 |
 | Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Bug report | Linux | 2.7.5 | Special characters in attribute names |
Hi
Thanks for elog - it's a brilliant piece of software. I'd looked all over for open source software to log/manage change requests before discovering elog; it's so flexible that I've been able to do everything I need with it.
However, I think that I've just discovered my first undocumented 'feature'. Attribute names containing punctuation characters (e.g. / and :) cause "Redirection limit for this URL exceeded" errors in Firefox 3.0.2 and corrupt the URL if they're used in a Quick Filter. I often use '/' in attribute names for brevity, e.g. "Old/New Versions" but hadn't used one in a Quick Filter before.
keep up the good work.
regards
Steve
|
|
66044
|
Thu Nov 13 13:25:25 2008 |
| Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Request | Linux | 2.7.5 | Sorting Museremail |
Hi
I've just upgraded to 2.7.5 mainly because I wanted to have Museremail sorted. We use this to list contacts on an RFC form and it's much easier to find the ones you want when they are in a predictable sequence. As an extension to this it would be great if they could be sorted by the last part of their real name - typical user, give him a sweetie and he wants jam on it!
cheers
Steve |
|
66047
|
Mon Nov 17 10:08:01 2008 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.5 | Re: Sorting Museremail |
| Steve Williamson wrote: |
|
Hi
I've just upgraded to 2.7.5 mainly because I wanted to have Museremail sorted. We use this to list contacts on an RFC form and it's much easier to find the ones you want when they are in a predictable sequence. As an extension to this it would be great if they could be sorted by the last part of their real name - typical user, give him a sweetie and he wants jam on it!
cheers
Steve
|
That's a bit hard since different groups enter their names differently. While for a human it's easy to figure out what the family name is (usually), this must not be true for a computer. So I would propose that you enter the real names in the sequence family name, given name like
Ritt, Stefan
Doe, John
then sorting will work as you like. |
|
66048
|
Mon Nov 17 10:18:52 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5 | Re: Special characters in attribute names |
| Steve Williamson wrote: |
|
Hi
Thanks for elog - it's a brilliant piece of software. I'd looked all over for open source software to log/manage change requests before discovering elog; it's so flexible that I've been able to do everything I need with it.
However, I think that I've just discovered my first undocumented 'feature'. Attribute names containing punctuation characters (e.g. / and :) cause "Redirection limit for this URL exceeded" errors in Firefox 3.0.2 and corrupt the URL if they're used in a Quick Filter. I often use '/' in attribute names for brevity, e.g. "Old/New Versions" but hadn't used one in a Quick Filter before.
|
Quick answer: Don't use '/' in attribute names ;-) but I guess you were kind of afraid to get this answer.
Somehow longer answer: I tried to reproduce your problem with following configuration:
[demo]
Attributes = Author, Type, Subject, Old/New
Options Old/New = Old, New
Quick filter = Type, Old/New
But I was not successful. Everything worked fine using ELOG V2.7.5-2137. Can you please check with the above configuration and tell me exactly when the redirection problem occurs? Is it during filtering on already on creating a new entry?
|
|
66050
|
Mon Nov 17 10:27:23 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Other | 2.7.5 | Re: elogd dies after receiving second SIGHUP |
> elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
> This was observed on Solaris 10 (SPARC).
> The documentation states that elogd should re-read configuration after receiving SIGHUP.
I tried to reproduce this but without success. I could send many SIGHUPs without the daemon terminating. Maybe
you modified the configuration file in between and elogd barked out because of some wrong configuration? Try to
start the daemon interactively and see what exactly happens if you send several SIGHUPs. |