Craig Foster wrote: <snip> > Actually, make that e-smith-messagewall-0.0.2 > > * Tue Jul 08 2003 Craig Foster <[EMAIL PROTECTED]> > - Fixed anti-virus databases not reloading after updating > - Changed syslog category to filter to special messagewall log > - Gussied up the runlevel script to use tests & colour (woot!) >
Try again, e-smith-messagewall-0.0.3
* Wed Jul 09 2003 Craig Foster <[EMAIL PROTECTED]>
- fixed missing directory for PID file.
- fixed /var/service/smtpfront-qmail/run not expanded.
- tests are proven to be unreliable. Bug report noted.
Maybe someone could nudge me in the right direction, regarding the false
OK?
The snippet of start (/etc/rc.d/init.d/messagewall) code is thus :
=====================================
RETVAL=0
startmw() {
echo -n $"Starting MessageWall: "
# Change "local1.info" to the syslog level you want.
/usr/bin/messagewall 2>&1 | /usr/bin/logger -t Messagewall \
-p local1.info &
RETVAL=$?
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/messagewall
[ $RETVAL -eq 0 ] && echo_success
[ $RETVAL -ne 0 ] && echo_failure
echo
return $RETVAL
}
======================================
As you can see, there is no logging facility other than STDOUT
redirected to logger.
I think that since logger starts OK, RETVAL gets the OK (=0). Have
anyone come across any other way to detect running startups?
I'm thinking the old `ps ax | grep "/usr/bin/messagewall"` might be the
way to go....
It'll need to be detected properly, if I hope to move to daemontools
and/or chroot.
All usual beta software warnings apply...
Regards,
Craig F.
smime.p7s
Description: S/MIME cryptographic signature
