Add back more dire warning to pt-ioprofile.

bin/pt-ioprofile

@@ -916,9 +916,9 @@ the result. If you specify a FILE, then step 1) is not performed.
 
 =head1 RISKS
 
-Percona Toolkit is mature, proven in the real world, and well tested,
-but all database tools can pose a risk to the system and the database
-server.  Before using this tool, please:
+B<WARNING>: pt-ioprofile freezes the server and may crash the process, or
+make it perform badly after detaching, or leave it in a sleeping state!
+Before using this tool, please:
 
 =over
 
@@ -930,6 +930,9 @@ server.  Before using this tool, please:
 
 =item * Backup your production server and verify the backups
 
+pt-ioprofile should be considered an intrusive tool, and should not be used
+on production servers unless you understand and accept the risks.
+
 =back
 
 =head1 DESCRIPTION
@@ -945,6 +948,14 @@ process for 30 seconds.  The output is like:
 
 You probably need to run this tool as root.
 
+pt-ioprofile works by attaching C<strace> to the process using C<ptrace()>,
+which will make it run very slowly until C<strace> detaches.  In addition to
+freezing the server, there is some risk of the process crashing or performing
+badly after C<strace> detaches from it, or of C<strace> not detaching cleanly
+and leaving the process in a sleeping state.  As a result, this should be
+considered an intrusive tool, and should not be used on production servers
+unless you are comfortable with that.
+
 =head1 OPTIONS
 
 =over

bin/pt-table-sync

@@ -11337,7 +11337,7 @@ through replication and change master1's data:
 
 =head1 RISKS
 
-C<WARNING>: pt-table-sync changes data!  Before using this tool, please:
+B<WARNING>: pt-table-sync changes data!  Before using this tool, please:
 
 =over