[leaf-commits] src/bering-uclibc4/source/bbntpd buildtool.cfg, NONE, 1.1 buildtool.mk, NONE, 1.1 ntpd, NONE, 1.1 ntpd.default, NONE, 1.1

KP Kirchd?rfer <[email protected]> Sat, 04 Dec 2010 16:14:49 +0000
Newsgroups gmane.linux.leaf.cvs
Message-ID <[email protected]>
Update of /cvsroot/leaf/src/bering-uclibc4/source/bbntpd
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv18089

Added Files:
	buildtool.cfg buildtool.mk ntpd ntpd.default 
Log Message:
busybox ntpd configuration files


--- NEW FILE: ntpd.default ---
# This file controls the activity of ntpd

# ntpd control (yes means start daemon).
NTPDRUN=no

# ntpd options 
# -l activates server mode
# -p peer (can be more than one)
NTPDOPTS='-l -p 0.pool.ntp.org -p 1.pool.ntp.org'

--- NEW FILE: buildtool.mk ---
include $(MASTERMAKEFILE)

BBNTPD_DIR=bbntpd
BBNTPD_BUILD_DIR=$(BT_BUILD_DIR)/bbntpd

$(BBNTPD_DIR)/.source:
	mkdir -p $(BBNTPD_DIR)
	touch $(BBNTPD_DIR)/.source
	
$(BBNTPD_DIR)/.build: $(BBNTPD_DIR)/.source  
	mkdir -p $(BBNTPD_BUILD_DIR)
	mkdir -p $(BBNTPD_BUILD_DIR)/etc/init.d
	mkdir -p $(BBNTPD_BUILD_DIR)/etc/default
	-mkdir -p $(BT_STAGING_DIR)/etc/init.d
	-mkdir -p $(BT_STAGING_DIR)/etc/default
	
	cp -a ntpd $(BBNTPD_BUILD_DIR)/etc/init.d/ntpd
	cp -a ntpd.default $(BBNTPD_BUILD_DIR)/etc/default/ntpd
	cp -a $(BBNTPD_BUILD_DIR)/* $(BT_STAGING_DIR)/bin
	cp -a $(BBNTPD_BUILD_DIR)/etc/init.d/* $(BT_STAGING_DIR)/etc/init.d/
	cp -a $(BBNTPD_BUILD_DIR)/etc/default/* $(BT_STAGING_DIR)/etc/default/
	touch $(BBNTPD_DIR)/.build

source: $(BBNTPD_DIR)/.source

build: $(BBNTPD_DIR)/.build

clean:  
	-rm $(BBNTPD_DIR)/.build
	-rm -r $(BBNTPD_BUILD_DIR)

srcclean:
	rm -rf $(BBNTPD_DIR)	

--- NEW FILE: buildtool.cfg ---
<File buildtool.mk>
	Server = cvs4-sourceforge
	Directory = bbntpd
	revision = HEAD
</File>

<File ntpd>
	Server = cvs4-sourceforge
	directory = bbntpd
	revision = HEAD
</File>

<File ntpd.default>
	Server = cvs4-sourceforge
	directory = bbntpd
	revision = HEAD
</File>

<Package>
	<bbntpd>
		Version = 1
		Revision = 1
		
		Help <<EOF
		bbntpd provides the busybox ntpd configuration files
		LEAF package by __PACKAGER__, __BUILDDATE__ 
		EOF
                <Permissions>                                                                                                  
			Files = 644
			Directories = 755
		</Permissions>

		<Owner>
		Files = root:root
		Directories = root:root
		</Owner>
	
	<Contents>
		<File>
			Source          = etc/init.d/ntpd
			Filename        = etc/init.d/ntpd
			Type            = binary
			Permissions     = 755
		</File>

		<File>
			Source          = etc/default/ntpd
			Filename        = etc/default/ntpd
			Type            = binary
			Type            = local
			Type            = conf
			Description     = busybox ntpd options
			Permissions     = 644
</File>	
	
	</Contents>
	</bbntpd>
</Package>
--- NEW FILE: ntpd ---
#! /bin/sh
#
# skeleton	example file to build /etc/init.d/ scripts.
#		This file should be used to construct scripts for /etc/init.d.
#
#		Written by Miquel van Smoorenburg <[email protected]>.
#		Modified for Debian 
#		by Ian Murdock <[email protected]>.
#
# Version:	@(#)skeleton  1.9  26-Feb-2001  [email protected]
#
RCDLINKS="2,S25 3,S25 4,S25 5,S25 0,K25 1,K25 6,K25"

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/ntpd
NAME=ntpd
DESC="BusyBox ntpd"

test -x $DAEMON || exit 0

# read our control file
. /etc/default/ntpd


set -e

case "$1" in
  start)
	echo -n "Starting $DESC "
	if [ "$NTPDRUN" = "yes" ]; then
	start-stop-daemon --start --quiet --exec $DAEMON -- $NTPDOPTS
	echo 
	fi
	;;
  stop)
	echo -n "Stopping $DESC "
	start-stop-daemon --stop --oknodo --quiet --exec $DAEMON 2>/dev/null
	echo 
	;;
  restart|force-reload)
	echo -n "Restarting $DESC "
	start-stop-daemon --stop --oknodo --quiet --exec $DAEMON 2>/dev/null
	sleep 1
	if [ "$NTPDRUN" = "yes" ]; then
	start-stop-daemon --start --quiet --exec $DAEMON -- $NTPDOPTS
	echo 
	fi
	;;
  *)
	N=/etc/init.d/$NAME
	echo "Usage: $N {start|stop|restart|force-reload}" >&2
	exit 1
	;;
esac

exit 0


------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d