Paths

Table of Contentst

-
usr.sbin/bhyve/
-
bhyve/
1
bhyve.8

bhyve: document signals handling and exit codes
ClosedPublic
Actions

Authored by novel on Apr 17 2016, 3:55 AM.

Details

Reviewers

grehan
neel
wblock

Group Reviewers

Doc Committers
manpages

Commits

rS298341: Update the bhyve(8) man page:

Summary

Update the bhyve(8) man page:

Document powering off by sending SIGTERM signal
Document exit codes

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

novel updated this revision to Diff 15273.Apr 17 2016, 3:55 AM

novel retitled this revision from to bhyve: document signals handling and exit codes.

novel updated this object.

novel edited the test plan for this revision. (Show Details)

novel added reviewers: neel, grehan, Doc Committers.

novel set the repository for this revision to rS FreeBSD src repository - subversion.

Herald added a reviewer: manpages. · View Herald TranscriptApr 17 2016, 3:55 AM

Herald added a subscriber: imp. · View Herald Transcript

wblock added a subscriber: wblock.Apr 17 2016, 4:42 PM

wblock added inline comments.

usr.sbin/bhyve/bhyve.8
302	How about a shorter version: Exit status indicates how the VM was terminated:
310	"VM was" in these three entries is redundant and can just be eliminated entirely.
312	s/Triple/triple/ to match the other entries.

Oh, and remember to update .Dd. Nice to routinely run igor -R bhyve.8 and mandoc -Tlint bhyve.8 before commit, too.

Updated wording
Updated .Dd

Herald edited edge metadata. · View Herald TranscriptApr 18 2016, 7:33 AM

novel marked 3 inline comments as done.Apr 18 2016, 7:33 AM

Thanks!

This revision is now accepted and ready to land.Apr 18 2016, 7:02 PM

In D5982#127617, @wblock wrote:

Thanks!

Thank you for review, Warren. Does that mean that I, as a ports committer, can commit it?

neel accepted this revision.Apr 19 2016, 6:11 PM

neel edited edge metadata.

In D5982#127701, @novel wrote:

In D5982#127617, @wblock wrote:

Thanks!

Thank you for review, Warren. Does that mean that I, as a ports committer, can commit it?

I usually think of accepting a review as separate from an "Approved-by", but I'll give an Approved-by for this. Remember to enter that on the commit.

Closed by commit rS298341: Update the bhyve(8) man page: (authored by novel). · Explain WhyApr 20 2016, 6:29 AM

This revision was automatically updated to reflect the committed changes.

novel mentioned this in rS298341: Update the bhyve(8) man page:.

Revision Contents
Changeset List

Path

Size

usr.sbin/

bhyve/

bhyve.8

22 lines

Diff 15273

View Options

usr.sbin/bhyve/bhyve.8

	Show First 20 Lines • Show All 42 Lines • ▼ Show 20 Lines
	.Op Fl t Ar trstr			.Op Fl t Ar trstr
	.Ar command			.Ar command
	.Sh DESCRIPTION			.Sh DESCRIPTION
	The			The
	.Nm			.Nm
	utility enables kernel trace logging for the specified processes.			utility enables kernel trace logging for the specified processes.
	Kernel trace data is logged to the file			Kernel trace data is logged to the file
	.Pa ktrace.out .			.Pa ktrace.out .
	The kernel operations that are traced include system calls,			The kernel operations that are traced include system calls
				.Pq see Xr intro 2 ,
	.Xr namei 9			.Xr namei 9
				kibUnsubmitted Not Done Inline Actions Might be convert namei reference in the similar way: file system path lookups .Pq Xr namei 9 , kib: Might be convert namei reference in the similar way: file system path lookups .Pq Xr namei 9 ,
	translations, signal processing, and			translations, signal processing
				.Pq Xr sigaction 2 ,
				and
	.Tn I/O .			.Tn I/O .
	.Pp			.Pp
	Once tracing is enabled on a process, trace data will be logged until			Once tracing is enabled on a process, trace data will be logged until
	either the process exits or the trace point is cleared.			either the process exits or the trace point is cleared.
	A traced process can generate enormous amounts of log data quickly;			A traced process can generate enormous amounts of log data quickly;
	It is strongly suggested that users memorize how to disable tracing before			It is strongly suggested that users memorize how to disable tracing before
	attempting to trace a process.			attempting to trace a process.
	The following command is sufficient to disable tracing on all user-owned			The following command is sufficient to disable tracing on all user-owned
	▲ Show 20 Lines • Show All 131 Lines • ▼ Show 20 Lines
	.Dl $ ktrace -c -f tracedata			.Dl $ ktrace -c -f tracedata
	.Pp			.Pp
	Disable tracing of all user-owned processes:			Disable tracing of all user-owned processes:
	.Dl $ ktrace -C			.Dl $ ktrace -C
	.Sh SEE ALSO			.Sh SEE ALSO
	.Xr dtrace 1 ,			.Xr dtrace 1 ,
	.Xr kdump 1 ,			.Xr kdump 1 ,
	.Xr truss 1 ,			.Xr truss 1 ,
				.Xr intro 2 ,
	.Xr ktrace 2 ,			.Xr ktrace 2 ,
				.Xr sigaction 2 ,
	.Xr utrace 2 ,			.Xr utrace 2 ,
	.Xr capsicum 4 ,			.Xr capsicum 4 ,
	.Xr namei 9			.Xr namei 9
	.Sh HISTORY			.Sh HISTORY
	The			The
	.Nm			.Nm
	command appeared in			command appeared in
	.Bx 4.4 .			.Bx 4.4 .
	.Sh BUGS			.Sh BUGS
	Only works if			Only works if
	.Ar trfile			.Ar trfile
	is a regular file.			is a regular file.

bhyve: document signals handling and exit codesClosedPublicActions