[oprof-cvs] CVS: oprofile/doc oprofile.sgml,1.18,1.19

[John L. <mov...@us...>]

Update of /cvsroot/oprofile/oprofile/doc
In directory usw-pr-cvs1:/tmp/cvs-serv30522/doc

Modified Files:
	oprofile.sgml 
Log Message:
I got bored of typing echo 1 >/proc/sys/dev/oprofile/dump ...



Index: oprofile.sgml
===================================================================
RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.sgml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -d -r1.18 -r1.19
--- oprofile.sgml	2001/08/02 17:55:22	1.18
+++ oprofile.sgml	2001/08/11 01:45:54	1.19
@@ -210,7 +210,7 @@
 <para>
 Anyway, data will be processed by daemon every ten minutes. I'm too lazy to wait that long, so force the issue with :
 </para>
-<para><command>echo 1 &gt;/proc/sys/dev/oprofile/dump</command></para>
+<para><command>op_dump</command></para>
 <para> 
 which will ask the kernel module to dump as much data as it can to the daemon.
 <note>
@@ -636,7 +636,7 @@
 OProfile does a little <emphasis>too</emphasis> good a job of keeping overhead low, and no data reaches
 the profiler. This can happen on lightly-loaded machines. Remember you can force a dump at any time with :
 </para>
-<para><command>echo 1 &gt;/proc/sys/dev/oprofile/dump</command></para>
+<para><command>op_dump</command></para>
 <para>Remember to do this before complaining there is no profiling data !
 Now that we've got some data, it has to be processed. That's the job of
 <command>oprofpp</command>. This works on a sample file in the <filename>/var/opd/samples/</filename> directory,