1.1 --- a/docs/wiki/Resources Fri May 13 00:22:56 2016 +0200
1.2 +++ b/docs/wiki/Resources Fri May 13 00:28:46 2016 +0200
1.3 @@ -383,19 +383,34 @@
1.4 but a tool is also provided to set such limits. For example:
1.5
1.6 {{{
1.7 -set_quota_limit.py 'mailto:resource-car-cadillac@example.com' \
1.8 - 'mailto:vincent.vole@example.com' PT10H
1.9 +cat <<EOF | set_quota_limits.py 'mailto:resource-car-cadillac@example.com'
1.10 +mailto:vincent.vole@example.com PT10H
1.11 +EOF
1.12 }}}
1.13
1.14 -This indicates that the given user may only reserve 10 hours of events or less
1.15 -within the given quota (corresponding to a specific resource in the above
1.16 -example). Attempts to schedule more time will be declined.
1.17 +{{{#!wiki tip
1.18 +In the above example, shell syntax is used to indicate a
1.19 +[[http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07_04|here document]]
1.20 +providing a kind of "inline" file that is terminated by the final `EOF`.
1.21 +The contents of this file are piped to the tool with a single argument given
1.22 +indicating the quota involved.
1.23 +
1.24 +You could also just invoke the tool and then enter the limit descriptions,
1.25 +ending the input with Ctrl-D or equivalent end-of-file keystroke, or save
1.26 +the descriptions in a file and then use input redirection with the filename.
1.27 +}}}
1.28 +
1.29 +The above example indicates that the given user may only reserve 10 hours
1.30 +of events or less time within the given quota (corresponding to a specific
1.31 +resource in the above example). Attempts to schedule more time will be
1.32 +declined.
1.33
1.34 To impose a general quota, the special `*` identity can be used:
1.35
1.36 {{{
1.37 -set_quota_limit.py 'mailto:resource-car-cadillac@example.com' \
1.38 - '*' PT10H
1.39 +cat <<EOF | set_quota_limits.py 'mailto:resource-car-cadillac@example.com'
1.40 +* PT10H
1.41 +EOF
1.42 }}}
1.43
1.44 When a user identity is not listed and no general quota is defined, that