s6-rc-update does not stop or start services in changed bundle
I am not sure if I am misunderstanding what s6-rc-update is intended to do.
I have gone through this process a couple times now, and I always must manually stop or start the service. Below is a transcript of removing cupsd from the default bundle, and having to manually stop the service.
I am especially confused by the documentation saying that s6-rc will inspect the difference between the two compiled databases and stop services that are not present in the new compiled database. (Docs excerpted below)
I get similar (lack of) behavior when adding cupsd back to the default bundle. Am I doing something wrong? Or am I just misunderstanding the expectations of s6-rc-update?
From: https://skarnet.org/software/s6-rc/s6-rc-update.html (under restarts)
The transcript below indicates "stopping services in the old database" and "bringing selected services down"
# s6-rc-db contents default | grep cupsd
cupsd
# pgrep cupsd 11756
# rm /etc/s6/adminsv/default/contents.d/cupsd
# s6-rc-compile /etc/s6/rc/compiled-new /etc/s6/adminsv /etc/s6/sv
# s6-rc-update -v3 /etc/s6/rc/compiled-new
s6-rc-update: info: computing state adjustments
s6-rc-update: info: stopping services in the old database
s6-rc: info: bringing selected services down
s6-rc-update: info: updating state and service directories
s6-rc-update: info: successfully switched to new database
s6-rc-update: info: updating s6rc-fdholder pipe storage
s6-rc-update: info: cleaning up scan directory
s6-rc-update: info: starting services in the new database
s6-rc: info: bringing selected services up
# s6-rc-db contents default | grep cupsd
# pgrep cupsd
11756
# s6-rc stop cupsd