Opened 6 years ago

Last modified 4 years ago

#3043 new enhancement

User-submitted upstart script (for CentOS 6.4)

Reported by: shane Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: Unclassified Version: git
Keywords: Cc: miles@…
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 1 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

A user submitted an upstart script with the following mail.

From: "Miles Brennan" <miles@brennan.id.au>
To: <bind-users@lists.isc.org>
Subject: BIND10 Upstart Script
Date: Tue, 9 Jul 2013 18:05:06 +1000

Hey All.

 

New list user here.. Miles from Brisbane.AU, currently tinkering with BIND10
just to see what it's like and evaluate stability for potential use in a
startup.

 

Background: A Geek!, I authored the Linux Home Server HOWTO
(www.brennan.id.au <http://www.brennan.id.au> ) a few years back to make it
easier for users to build their own home environment.

 

I looked long and hard for a good init / upstart script for BIND10, but
ended up writing my own to suit my CentOS 6.4 environment.

 

I thought you might like it for your WIKI so others can start playing with
BIND10 a little more.

 

Usage.

-        initctl start bind10

-        initctl restart bind10

-        initctl stop bind10

 

Cheers,

Miles

 

============================================================

 

vi /etc/init/bind10.conf

 

 

description "BIND10 is a DNS server with DHCPv4 and DHCPv6 server support"

 

env
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:
/usr/local/libexec/bind10

export PATH

 

start on runlevel [345]

stop on runlevel [0126]

 

pre-start script

 

        exec logger -p user.warning -t upstart-bind10 "BIND10 daemon
starting"

 

end script

 

exec b10-init --user bind --config-file /usr/local/var/bind10/b10-config.db
\

               --pid-file /usr/local/var/bind10/bind10.pid \

               --msgq-socket-file /usr/local/var/bind10/msgq_socket \

               --data-path /usr/local/var/bind10 --cmdctl-port 8080

 

#pre-stop

 

post-stop exec logger -p user.warning -t upstart-bind10 "BIND10 daemon
stopped"

 

respawn

kill timeout 30

console none

Subtickets

Change History (9)

comment:1 Changed 6 years ago by shane

  • Cc miles@… added

comment:2 Changed 6 years ago by muks

I don't know about this ticket. Some points:

  • Fedora has switched to systemd. RHEL7 will also use systemd. BIND 10 already has systemd scripts in Fedora.
  • RHEL6 (and CentOS6) does not have packaged dependencies for BIND 10 yet (Python 3 is notably missing).
  • In any case, this should probably be moved to system specific notes page as an attachment for packagers to use, as it doesn't belong in the BIND 10 tree. This is OS and distro specific.

comment:3 Changed 6 years ago by muks

  • Estimated Difficulty changed from 0 to 1

comment:4 Changed 6 years ago by muks

  • Milestone New Tasks deleted

We decided that we'd move this to a wiki page (as instructions).

Clearing milestone.

comment:5 Changed 5 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:6 Changed 5 years ago by jpopelka

For systemd service unit files see #3529

comment:7 Changed 5 years ago by tomek

  • Milestone changed from Remaining BIND10 tickets to Common Outstanding Tasks
  • Version set to git

comment:8 Changed 4 years ago by tomek

  • Milestone changed from Common Outstanding Tasks to DHCP Outstanding Tasks

comment:9 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

Note: See TracTickets for help on using tickets.