Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use more markup.

This commit is contained in:
wiz 2016-01-11 06:21:23 +00:00
parent 98e9d5f901
commit 0905aa5acf
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
share/man/man4/filemon.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: filemon.4,v 1.18 2016/01/11 01:45:27 pgoyette Exp $
.\" $NetBSD: filemon.4,v 1.19 2016/01/11 06:21:23 wiz Exp $
.\"
.\" Copyright (c) 2011, Juniper Networks, Inc.
.\"
@ -154,7 +154,7 @@ indicates the version of
A
.Nm
instance is created by opening
.Dv /dev/filemon .
.Pa /dev/filemon .
Then use
.Fn ioctl filemon_fd FILEMON_SET_PID &pid
to identify the target process to monitor, and
@ -219,9 +219,10 @@ successful, and is thus more complex to post-process.
.Nm
was contributed by Juniper Networks.
.Sh SECURITY CONSIDERATIONS
If the monitored process exits, and its pid gets reused, filemon will
continue to report events for the new process (and its descendants)
without any authorization checks.
If the monitored process exits, and its pid gets reused,
.Nm
will continue to report events for the new process (and its
descendants) without any authorization checks.
.Pp
Monitoring of a process enables the target process to write to the
tracking process's file descriptor.
@ -238,8 +239,9 @@ any descendants of such processes can be tracked.
If two processes are monitored, and one is a descendant of the other, events
related to the descendant process and its further descendants are delivered
only to the descendant process's monitor.
If a process is being monitored by two instances of filemon, events will be
delivered only to the first instance created (when
If a process is being monitored by two instances of
.Nm ,
events will be delivered only to the first instance created (when
.Pa /dev/filemon
was opened), regardless of the order in which the monitoring processes
called