After discussion, I'm not sure if this is possible for chroot based
containers since there really is no concept of "starting" or "opening" a
chroot.
That said, we could possible have some sort of libertine-chroot-manager
that could set this up, but any benefits may not outweigh the work
required and the current way works.
** Also affects: libertine/devel
Importance: Undecided
Status: New
** Also affects: libertine/trunk
Importance: Undecided
Status: New
** Also affects: libertine (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libertine/devel
Importance: Undecided => Medium
** Changed in: libertine/trunk
Importance: Undecided => Medium
** Changed in: libertine (Ubuntu)
Importance: Undecided => Medium
** Changed in: libertine/devel
Status: New => Triaged
** Changed in: libertine/trunk
Status: New => Triaged
** Changed in: libertine (Ubuntu)
Status: New => Triaged
** Description changed:
- Currently we create proxy sockets per application. This shoudlnt be
+ Currently we create proxy sockets per application. This shouldn't be
needed. We should only need one proxy socket per container that is open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586193
Title:
Only one proxy socket should be needed for a container
To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1586193/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
