From 761197707bd134acbaf1c2262dc2b70444d53c27 Mon Sep 17 00:00:00 2001 From: Peter Mounce Date: Sat, 9 May 2015 11:01:46 +0100 Subject: [PATCH] use the notes property --- lib/ansible/modules/extras/windows/win_dotnet_ngen.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/lib/ansible/modules/extras/windows/win_dotnet_ngen.py b/lib/ansible/modules/extras/windows/win_dotnet_ngen.py index 5f6d45062d6..90f464a1b0b 100644 --- a/lib/ansible/modules/extras/windows/win_dotnet_ngen.py +++ b/lib/ansible/modules/extras/windows/win_dotnet_ngen.py @@ -31,9 +31,10 @@ description: - This happens via scheduled task, usually at some inopportune time. - This module allows you to run this task on your own schedule, so you incur the CPU hit at some more convenient and controlled time. - "http://blogs.msdn.com/b/dotnet/archive/2013/08/06/wondering-why-mscorsvw-exe-has-high-cpu-usage-you-can-speed-it-up.aspx" - - "Note: there are in fact two scheduled tasks for ngen but they have no triggers so aren't a problem" - - "Note: there's no way to test if they've been completed (?)" - - Note: the stdout is quite likely to be several megabytes +notes: + - there are in fact two scheduled tasks for ngen but they have no triggers so aren't a problem + - there's no way to test if they've been completed (?) + - the stdout is quite likely to be several megabytes options: author: Peter Mounce '''