Blame SOURCES/0000-remove-conf.patch

f56ccc
diff -rup numad-0.5git/numad.8 numad-0.5git-new/numad.8
f56ccc
--- numad-0.5git/numad.8	2015-06-02 13:16:31.000000000 +0200
f56ccc
+++ numad-0.5git-new/numad.8	2019-03-26 09:20:45.887766101 +0100
f56ccc
@@ -98,8 +98,7 @@ Sets the time interval that numad waits
f56ccc
 <\fImin_interval\fP> is 5 seconds.  Setting a <\fImax_interval\fP> of zero will
f56ccc
 cause the daemon to exit.  (This is the normal mechanism to terminate the
f56ccc
 daemon.)  A bigger <\fImax_interval\fP> will decrease numad overhead but also
f56ccc
-decrease responsiveness to changing loads.  The default numad max_interval can
f56ccc
-be changed in the numad.conf file.
f56ccc
+decrease responsiveness to changing loads.
f56ccc
 .TP
f56ccc
 \fB\-K\fR <\fI0|1\fP>
f56ccc
 This option controls whether numad keeps interleaved memory spread across NUMA
f56ccc
@@ -210,8 +209,6 @@ numad can manage.
f56ccc
 .LP
f56ccc
 \fI/usr/bin/numad\fP
f56ccc
 .br
f56ccc
-\fI/etc/numad.conf\fP
f56ccc
-.br
f56ccc
 \fI/var/log/numad.log\fP
f56ccc
 .br
f56ccc
 \fI/var/run/numad.pid\fP