Sahid pointed out that the swift-init will traverse a search path and
start a daemon for every config file it finds so no change to the init
script is needed. Initial tests suggest this completely covers my use
case. I will continue testing and report back. I will mark the bug as
invalid for the moment. Thanks Sahid !
** Changed in: cloud-archive/mitaka
Status: Triaged => Invalid
** Changed in: cloud-archive/ocata
Status: Triaged => Invalid
** Changed in: cloud-archive/queens
Status: Triaged => Invalid
** Changed in: cloud-archive/rocky
Status: Triaged => Invalid
** Changed in: cloud-archive/stein
Status: Triaged => Invalid
** Changed in: cloud-archive/train
Status: Triaged => Invalid
** Changed in: cloud-archive/ussuri
Status: Triaged => Invalid
** Changed in: swift (Ubuntu Xenial)
Status: Triaged => Invalid
** Changed in: swift (Ubuntu Bionic)
Status: Triaged => Invalid
** Changed in: swift (Ubuntu Disco)
Status: Triaged => Invalid
** Changed in: swift (Ubuntu Eoan)
Status: Triaged => Invalid
** Changed in: swift (Ubuntu Focal)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854718
Title:
Groups of swift daemons are all forced to use the same config
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1854718/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
