Stop base kills the stack screen and run swift-init stop. However, this still leaves swift processes running. The swift process may be killed using something like pkill (like used on devstack stop_swift)
openstack@deacon:/opt/stack/grizzly/devstack$ swift-init all stop
No container-updater running
No account-auditor running
No object-replicator running
No proxy-server running
No container-replicator running
No object-auditor running
No object-expirer running
No container-auditor running
No container-server running
No account-server running
No account-reaper running
No container-sync running
No account-replicator running
No object-updater running
No object-server running
openstack@deacon:/opt/stack/grizzly/devstack$ ps aux | grep swift
1000 5880 0.0 0.0 75876 15492 ? Ss 15:52 0:00 /usr/bin/python /usr/local/bin/swift-account-auditor /etc/swift/account-server/1.conf
1000 5881 0.0 0.0 1543240 15372 ? Ssl 15:52 0:00 /usr/bin/python /usr/local/bin/swift-object-replicator /etc/swift/object-server/1.conf
1000 5883 0.0 0.0 75948 15800 ? Ss 15:52 0:00 /usr/bin/python /usr/local/bin/swift-container-replicator /etc/swift/container-server/1.conf
1000 5884 0.0 0.0 72728 14660 ? Ss 15:52 0:00 /usr/bin/python /usr/local/bin/swift-object-auditor /etc/swift/object-server/1.conf
1000 5885 0.0 0.0 75808 15496 ? Ss 15:52 0:00 /usr/bin/python /usr/local/bin/swift-container-auditor /etc/swift/container-server/1.conf
1000 5888 0.0 0.0 75744 15172 ? Ss 15:52 0:00 /usr/bin/python /usr/local/bin/swift-account-reaper /etc/swift/account-server/1.conf
1000 5889 0.0 0.0 75944 15652 ? Ss 15:52 0:00 /usr/bin/python /usr/local/bin/swift-container-sync /etc/swift/container-server/1.conf
1000 5890 0.0 0.0 75932 15796 ? Ss 15:52 0:00 /usr/bin/python /usr/local/bin/swift-account-replicator /etc/swift/account-server/1.conf
1000 5932 0.3 0.0 72896 12892 ? S 15:52 0:12 /usr/bin/python /usr/local/bin/swift-object-auditor /etc/swift/object-server/1.conf
Should this be opened as a bug to swift-init?
Fix proposed to branch: master
Review: https:/