summaryrefslogtreecommitdiff
path: root/windows/win_dotnet_ngen.py
diff options
context:
space:
mode:
authorPeter Mounce <peter.mounce@just-eat.com>2015-05-09 11:01:46 +0100
committerPeter Mounce <peter.mounce@just-eat.com>2015-05-19 11:47:49 +0100
commitc32262732013e2177dd4779be4984ffb580dea9e (patch)
treee9ac6ef6cc06d2843bdcce73b563f08099df432d /windows/win_dotnet_ngen.py
parent52a87e16379edf21c46bf45725694cad4c5a91f5 (diff)
downloadansible-modules-extras-c32262732013e2177dd4779be4984ffb580dea9e.tar.gz
use the notes property
Diffstat (limited to 'windows/win_dotnet_ngen.py')
-rw-r--r--windows/win_dotnet_ngen.py7
1 files changed, 4 insertions, 3 deletions
diff --git a/windows/win_dotnet_ngen.py b/windows/win_dotnet_ngen.py
index 5f6d4506..90f464a1 100644
--- a/windows/win_dotnet_ngen.py
+++ b/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
'''