On Sun, Sep 20, 2015 at 04:00:56PM +0059, Jason McIntyre wrote: > > > > there is a "d" missing at the end. > > > > And "In a tamed program, systrace(4) is disabled" sounds better to me, but > > jmc might have an opinion on that.
no problem, I am not too confident in my english wording :) > > This could also be mentioned in the systrace(4) manpage, after all, if your > > wondering why systrace doesnt work, you won't know that the program is > > tamed and thus won't look in tame(2)? > > > > i wouldn;t worry about the exact wording too much, but it probably does > make sense to flag it in systrace(4) too. > I make a new patch, for tame.2 and systrace.4 For systrace.4 , I change the wording a bit in order to avoid "tamed" and be able to use "tame" with a .Xr . Perhaps another way is possible ? Else, I am not completely sure about saying "systrace is disabled". It isn't systrace(4) per se, but just the possibility to use systrace for this specific program once the tame(2) was called. -- Sebastien Marie Index: lib/libc/sys/tame.2 =================================================================== RCS file: /cvs/src/lib/libc/sys/tame.2,v retrieving revision 1.27 diff -u -p -r1.27 tame.2 --- lib/libc/sys/tame.2 11 Sep 2015 09:01:16 -0000 1.27 +++ lib/libc/sys/tame.2 23 Sep 2015 09:35:37 -0000 @@ -431,3 +431,7 @@ The .Fn tame system call appeared in .Ox 5.8 . +.Sh CAVEATS +In a tamed program, +.Xr systrace 4 +is disabled. Index: share/man/man4/systrace.4 =================================================================== RCS file: /cvs/src/share/man/man4/systrace.4,v retrieving revision 1.21 diff -u -p -r1.21 systrace.4 --- share/man/man4/systrace.4 14 Jun 2014 00:24:38 -0000 1.21 +++ share/man/man4/systrace.4 23 Sep 2015 09:35:37 -0000 @@ -484,3 +484,9 @@ When creating new policies, if .Va strp_maxents is not large enough to accommodate any system calls needed for fundamental process operations, the traced process will block forever. +.Pp +In a program using +.Xr tame 2 +, +.Nm +is disabled.
