from the eucalyptus-cc init script:
# now kill the services
pidfiles="$EUCALYPTUS/var/run/eucalyptus/net/euca-dhcp.pid
$EUCALYPTUS/var/run/eucalyptus/eucalyptus-cc.pid"
for pidfile in $pidfiles ; do
if [ -s $pidfile ]; then
pid=`cat
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => Medium
** Changed in: eucalyptus (Ubuntu)
Status: In Progress => Triaged
--
'eucalyptus-cc stop' does not kill the eucalyptus dhcpd3 process
https://bugs.launchpad.net/bugs/342054
You received this bug notification because you
Several times when shutting down the CC and Cloud init scripts I've been left
with the dhcpd3 process owning one of the listening 877x sockets (according to
netstat --tcp -nlp) and requiring a SIGKILL to die.
I wondered if this was fallout from init scripts sending SIGKILL to the daemons
in some
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) => Soren Hansen (soren)
Status: New => In Progress
--
'eucalyptus-cc stop' does not kill the eucalyptus dhcpd3 process
https://bugs.launchpad.net/bugs/342054
You received this bug notification because you are a member of Ubuntu
