*** This bug is a duplicate of bug 1511118 ***
https://bugs.launchpad.net/bugs/1511118
Hi, as the bug title says, it's a problem with socat, not with epoptes.
We cannot solve it in the epoptes code.
We've had reported it in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=803378, you can comment there to show that it's
important to you, so that the socat debian maintainers backport the
patch that the upstream developer supplied.
** Bug watch added: Debian Bug tracker #803378
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803378
** Also affects: socat (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803378
Importance: Unknown
Status: Unknown
** Changed in: epoptes
Status: New => Invalid
** Also affects: socat (Ubuntu)
Importance: Undecided
Status: New
** Changed in: socat (Ubuntu)
Importance: Undecided => Critical
** Changed in: socat (Ubuntu)
Status: New => Confirmed
** This bug has been marked a duplicate of bug 1511118
100% cpu usage with unresolved name server
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to socat in Ubuntu.
https://bugs.launchpad.net/bugs/1518140
Title:
socat using 100% of CPU
To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1518140/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
