1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
|
From: Lucas Nussbaum <lucas@debian.org>
Date: Wed, 26 Jul 2017 08:07:05 +0200
Subject: Fix some typos in docs
Forwarded: https://gitlab.inria.fr/taktuk/taktuk/-/issues/2
---
Perl-Module/lib/TakTuk/Pilot.pm | 16 ++++++++--------
taktuk | 4 ++--
taktuk.in | 4 ++--
taktuk.pod | 16 ++++++++--------
taktuk_module.pod | 2 +-
taktukcomm.pod | 4 ++--
6 files changed, 23 insertions(+), 23 deletions(-)
--- a/Perl-Module/lib/TakTuk/Pilot.pm
+++ b/Perl-Module/lib/TakTuk/Pilot.pm
@@ -503,7 +503,7 @@
}
}
- die "This script requieres as arguments hostnames to contact\n"
+ die "This script requires as arguments hostnames to contact\n"
unless scalar(@ARGV);
my $taktuk = TakTuk::Pilot->new();
@@ -587,24 +587,24 @@
command => TakTuk command line to be executed
timeout => optional timeout on the wait for TakTuk output
-Upon occurence of the timeout (if one has been given), C<run> will returns an
+Upon occurrence of the timeout (if one has been given), C<run> will returns an
C<ETMOUT> error code. Note the in this case B<TakTuk> execution will not be
terminated and should be resumed at some point by calling C<continue>.
=item B<continue>B<()>
-Resumes a B<TakTuk> execution interrupted by timeout occurence.
+Resumes a B<TakTuk> execution interrupted by timeout occurrence.
=item B<add_descriptor(%)>
Because the call to C<run> is blocking, waiting for B<TakTuk> output, it might
-be interesting to let the C<TakTuk::Pilot> module monitor I/O occurence related
+be interesting to let the C<TakTuk::Pilot> module monitor I/O occurrence related
to other file descriptors.
This is the intent of C<add_descriptor>. This function takes a hash as
parameter in which the following fields might be defined:
type => 'read', 'write' or 'exception', this is the
- type of I/O possiblities that should be
+ type of I/O possibilities that should be
monitored on the descriptor, as in select
system call (mandatory).
filehandle => file descriptor to monitor (mandatory).
@@ -619,10 +619,10 @@
taktuk => reference to the TakTuk object from which
the function was called.
- type => type of I/O occuring (as in add_callback)
+ type => type of I/O occurring (as in add_callback)
filehandle => the related file descriptor. Notice that the
user is in charge of performing the I/O
- operation itslef (sysread or syswrite).
+ operation itself (sysread or syswrite).
Notice also that, because of the use of a
select in TakTuk::Pilot, the use of buffered
I/O on this descriptor is strongly discouraged
@@ -689,7 +689,7 @@
=item B<TakTuk::Pilot::ETMOUT>
-A timeout occured in a call to C<run>.
+A timeout occurred in a call to C<run>.
=item B<TakTuk::Pilot::ETKTRN>
--- a/taktuk.in
+++ b/taktuk.in
@@ -660,7 +660,7 @@
sub find_sequence($$);
# Returns the content of the buffer associated to a descriptor and empty it
sub flush_buffer($);
-# Returns a textual description of any error that occured using send or recv
+# Returns a textual description of any error that occurred using send or recv
sub error_msg($);
# Sends a message to another node arguments are the node number and the message
sub send(%);
@@ -1155,7 +1155,7 @@
resulting arity is not specified)
-e, --end-group : ends a deployment group
-f, --machines-file name : name is the name of a file that contains remote
- machines names (equivalent to several -m opions)
+ machines names (equivalent to several -m options)
-l, --login name : sets the login name for the following hosts
-m, --machine name -[ -] : name is the name of a remote host to be deployed
with its optional arguments between -[ and -]
--- a/taktuk.pod
+++ b/taktuk.pod
@@ -116,7 +116,7 @@
=item B<--machines-file> filename
C<filename> is the name of a file that contains remote machines names
-(equivalent to several C<-m> opions). In each line of this file, the first word
+(equivalent to several C<-m> options). In each line of this file, the first word
is considered as a machine name and the remaining as comments.
=item B<-l> login
@@ -184,7 +184,7 @@
=item B<--send-files> files
-gives to B<TakTuk> a list of files to be sent upon successfull remote
+gives to B<TakTuk> a list of files to be sent upon successful remote
connection. Use with caution as it will slow down deployment (the files are
transferred before the end of the deployment). The intended use is NOT to
transfer application data files (rather use the C<put> command to transfer such
@@ -419,7 +419,7 @@
the time in seconds since Jan. 1, 1970 at which the connector command replied
to the local B<TakTuk> instance (note that this does not include the
-initialization exange occuring before the remote B<TakTuk> is considered as
+initialization exange occurring before the remote B<TakTuk> is considered as
functional).
=item C<$start_date> (C<output>, C<error>, C<connector> and C<status>)
@@ -430,7 +430,7 @@
=item C<$init_date> (C<connector> and C<state> only)
the time in seconds since Jan. 1, 1970 at which the remote B<TakTuk> completed
-its initilization.
+its initialization.
=item C<$stop_date> (C<connector> and C<status> only)
@@ -522,7 +522,7 @@
disables B<TakTuk> logical numbering and the variables C<TAKTUK_COUNT> and
C<TAKTUK_RANK> are not defined in executed commands. This has the advantage of
-removing the global synchronization occuring at the end of the deployment and
+removing the global synchronization occurring at the end of the deployment and
making the deployment more efficient.
WARNING: use this option only before any remote node specification (C<-m> or
@@ -681,7 +681,7 @@
=item B<exec> parameters * command line *
Executes the C<command line> on the local machine. Inputs/outputs of the
-execution are multiplexed and fowarded to the B<TakTuk> root.
+execution are multiplexed and forwarded to the B<TakTuk> root.
This command accepts optional parameters that enable the attachment of
callbacks triggered by timeouts to the execution of the command. See section
L<"EXEC PARAMETERS"> for more details.
@@ -1258,7 +1258,7 @@
taktuk -d 1 -m host1 -m host2 -m host3 broadcast exec [ 'echo $$' ]
-Finally, the default will use a dynamicly constructed topology:
+Finally, the default will use a dynamically constructed topology:
taktuk -d 0 -m host1 -m host2 -m host3 broadcast exec [ 'echo $$' ]
@@ -1314,7 +1314,7 @@
since version 3.4, files transfer is supported directly by TakTuk. Notice that
this transfer uses the B<TakTuk> network (usually a tree composed of ssh
-connections by default). This network is not efficient for the tranfer of large
+connections by default). This network is not efficient for the transfer of large
files (both topologically and from a protocol point of view), so keep this in
mind when using this feature.
--- a/taktuk_module.pod
+++ b/taktuk_module.pod
@@ -115,7 +115,7 @@
=back
When an error occur, all these functions set the variable C<$TakTuk::error>
-to the numeric code of the error that occured. A textual description of the
+to the numeric code of the error that occurred. A textual description of the
error is provided by the function C<TakTuk::error_msg($)> that takes the error
code as an argument.
--- a/taktukcomm.pod
+++ b/taktukcomm.pod
@@ -154,7 +154,7 @@
blocks until the reception of a message. If a regular message is received,
C<taktuk_recv> sets the value of its arguments: C<from> to the logical number
-of the sender, C<buffer> to the data received wich is made of
+of the sender, C<buffer> to the data received which is made of
C<length> bytes. If timeout is not NULL, C<taktuk_recv()> might receive a
timeout notification. In this case, C<taktuk_recv()> returns the TAKTUK_ETMOUT
error code.
@@ -225,7 +225,7 @@
=item TAKTUK_EALLOC
-An internal memory allocation failure occured.
+An internal memory allocation failure occurred.
=item TAKTUK_EIBUFF
|
