Comment 2 for bug 1060559

I have a startup script that I use for all the openstack services, it's a basic redhat/centos init script for chkconfig.

The start command is:

    daemon --user quantum --pidfile $pidfile "$exec --config-dir $config_dir --config-file $config_file --log-file $logfile &>/dev/null & echo \$! > $pidfile"

Where:

suffix=dhcp
prog=openstack-quantum-${suffix}-agent
exec="/usr/bin/quantum-${suffix}-agent"
config_dir="/etc/openstack/quantum"
config_file="/etc/openstack/quantum/${suffix}_agent.ini"
pidfile="/var/run/openstack/quantum-${suffix}-agent.pid"
logfile="/var/log/openstack/quantum-${suffix}-agent.log"

I end up with a python command running like:

/usr/bin/python /usr/bin/quantum-dhcp-agent --config-dir /etc/openstack/quantum --config-file /etc/openstack/quantum/dhcp_agent.ini --log-file /var/log/openstack/quantum-dhcp-agent.log

The only odd thing I see is it runs dnsmasq twice, not sure why:

dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tap77a55569-aa --except-interface=lo --domain=openstacklocal --pid-file=/var/lib/openstack/quantum/data/dhcp/8a56b7a4-06ae-404f-acee-9715b8823f7f/pid --dhcp-hostsfile=/var/lib/openstack/quantum/data/dhcp/8a56b7a4-06ae-404f-acee-9715b8823f7f/host --dhcp-optsfile=/var/lib/openstack/quantum/data/dhcp/8a56b7a4-06ae-404f-acee-9715b8823f7f/opts --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update --leasefile-ro --dhcp-range=set:tag0,10.0.0.0,static,120s

The only difference I see between the two processes is one is run as root and the other one is run as nobody.