Date: Fri, 03 Aug 2018 05:25:26 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 230082] bhyve doesn't set process title Message-ID: <bug-230082-27103-0KdTcy0mf6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230082-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-230082-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230082 Yuichiro NAITO <naito.yuichiro@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed Resolution|--- |FIXED --- Comment #9 from Yuichiro NAITO <naito.yuichiro@gmail.com> --- (In reply to Mariusz Zaborski from comment #7) > The setproctitle(3) looks fine with me - I will commit it. Thanks for the commit. > With the ps_string the problem is a little more complicated. > In my opinion the title is a part of a global namespace so we should not = be ab\ le to change it but I would like to discussed this. I misunderstood sysctl behavior. I saw that original (before r335939) setproctitle(3) calls sysctl like this. ``` sysctl([CTL_KERN, KERN_PROC, KEN_PROC_ARGS, getpid()], ...) ``` This code works in capability mode all the time (independent of r335939). I thought calling sysctl("kern.ps_strings") was also safe in capability mod= e. But, the sysctl is allowed to write only... > In this bug report can we only focus on the bhyve title issue? Yes, I don't see any other problems for now. I will close this PR. Thank you! --=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-230082-27103-0KdTcy0mf6>