Date: Thu, 11 May 2017 05:32:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 219210] net/x11vnc: Clarified the "Shared Memory Attach" failure message Message-ID: <bug-219210-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219210 Bug ID: 219210 Summary: net/x11vnc: Clarified the "Shared Memory Attach" failure message Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: dinoex@FreeBSD.org Reporter: yuri@rawbw.com Assignee: dinoex@FreeBSD.org Flags: maintainer-feedback?(dinoex@FreeBSD.org) Created attachment 182502 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D182502&action= =3Dedit patch Hi Dirk, This is a followup to our e-mail conversation. I troubleshooted the problem and found that x11vnc triggers the failure of shmat(2) called by Xorg with errno=3D24 (EMFILE), which indicates that sysc= tl(8) kern.ipc.shmseg limit is exceeded. I added to the error message so that x11vnc message will point users in the right direction should they meet the same error. Some graphics-intense apps can use a lot of shared memory in Xorg, and this eventually causes the limit to be exceeded, and x11vnc to fail. Users should increase the limit as needed for their local conditions. This is the related addition to shmat(2) manpage: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219209 Thanks, Yuri --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219210-13>