head	1.2;
access;
symbols;
locks; strict;
comment	@# @;


1.2
date	2001.09.04.02.19.23;	author woodchip;	state dead;
branches;
next	1.1;

1.1
date	2001.07.11.06.45.34;	author jerry;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Wow. Didnt notice this *very* cool logger before.. I think I just
found my next logging daemon. Has regexp support and stuff. Im
glad I got to take a look at this.. neato.  :>~

Note that I removed the "-s" option from the initscript, this
stuff is better left up to the admin of the box. Synchronous
mode could be detrimental to performance on a loaded machine..
I think we'd agree that the distribution need not dictate
policy. We *should* provide a solid init *system*.. which
is all the competent admin needs. ;) I honestly feel that
users are just better off pointed to the docs, rather have
having a configured system decided upon for them.
@
text
@#!/bin/sh
#RCUPDATE:1 2 3 4 5:19:This line is required for script management

. /etc/rc.d/config/functions

SERVICE=metalog
opts="start stop restart"

EXE=/usr/sbin/metalog

start() {
    ebegin "Starting $SERVICE..."
    start-stop-daemon --start --quiet --exec $EXE -- -B -s
    eend $? "Started $SERVICE." "Error Starting $SERVICE."
}

stop() {
    ebegin "Stopping $SERVICE..."
    start-stop-daemon --stop --quiet --exec $EXE
    eend $? "Stopped $SERVICE." "Error Stopping $SERVICE."
}

restart() {
    stop
    start
}

doservice ${@@}
@


1.1
log
@Initial import of metalog into the portage tree.

This is for people who want something a little more robust than the
traditional syslogd/klogd gluelog/multilog combos.
@
text
@@

