[PATCH] Documentation/scheduler: fix links in sched-stats

[PATCH] Documentation/scheduler: fix links in sched-stats

[Andre Azevedo]

The rain.com domain recently moved to pdxhosts.com, making the scheduler
documentation point to broken links. Fix the links in the scheduler
documentation.

CC: Rick Lindsley <ricklind@linux.vnet.ibm.com>
Signed-off-by: Andre Azevedo <andre.azevedo@gmail.com>
---
 Documentation/scheduler/sched-stats.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/scheduler/sched-stats.rst b/Documentation/scheduler/sched-stats.rst
index 0cb0aa714545..dd9b99a025f7 100644
--- a/Documentation/scheduler/sched-stats.rst
+++ b/Documentation/scheduler/sched-stats.rst
@@ -28,7 +28,7 @@ of these will need to start with a baseline observation and then calculate
 the change in the counters at each subsequent observation.  A perl script
 which does this for many of the fields is available at
 
-    http://eaglet.rain.com/rick/linux/schedstat/
+    http://eaglet.pdxhosts.com/rick/linux/schedstat/
 
 Note that any such script will necessarily be version-specific, as the main
 reason to change versions is changes in the output format.  For those wishing
@@ -164,4 +164,4 @@ report on how well a particular process or set of processes is faring
 under the scheduler's policies.  A simple version of such a program is
 available at
 
-    http://eaglet.rain.com/rick/linux/schedstat/v12/latency.c
+    http://eaglet.pdxhosts.com/rick/linux/schedstat/v12/latency.c
-- 
2.17.1

Re: [PATCH] Documentation/scheduler: fix links in sched-stats

[Jonathan Corbet]

On Sat, 26 Oct 2019 12:55:54 -0700
Andre Azevedo <andre.azevedo@gmail.com> wrote:

> The rain.com domain recently moved to pdxhosts.com, making the scheduler
> documentation point to broken links. Fix the links in the scheduler
> documentation.
> 
> CC: Rick Lindsley <ricklind@linux.vnet.ibm.com>
> Signed-off-by: Andre Azevedo <andre.azevedo@gmail.com>

Working links are better than dead ones, so I've applied this.  It still
appears to be rather old stuff, though - 2.6.x was a while ago at this
point.  It would sure be nice to get this information current and in
Documentation/ directly at some point ... 

Thanks,

jon