aboutsummaryrefslogtreecommitdiffstats
path: root/README
blob: d7cbe8733292e8ce41d475fbae2b004b44aba802 (plain) (blame)
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
NAME
	sshexec - run a command through ssh(1) with normal command syntax

SYNOPSIS
	sshexec [{ [ssh=ssh-command] [dir=directory] [cd=(strict|lax)]
	        [[fd]{>,>>,>|,<,<>}[&]=file] [asis=asis-marker
		[nasis=asis-count]] }] [ssh-option] ... destination
		command [argument] ...

DESCRIPTION
	The sshexec utility is a wrapper for SSH that makes it easy to
	run commands directly in the SSH command.

	sshexec passes any argument after } to ssh-command (ssh if not
	specified), but it rewrites command and the arguments to one
	argument that can be passed into ssh(1) to describe each argument
	as separate arguments. It may also rewrite destination to remove
	information that's not supported by ssh(1) and inserts extra
	arguments after it (it may also add a -- argument immediately
	before destination) to cause the remote shell it change working
	directory to directory, if specified, and execute the provided
	command and arguments as a regular command rather than as shell
	code joined by together by spaces.

OPTIONS
	sshexec options may be placed at the very beginning enclosed
	with the arguments { and }. sshexec options, if any, shall be
	placed in the same { }-group. Any other option will be passed
	as is to the ssh(1) utility or ssh-command. The sshexec utility
	has a build it list of options recognised by the ssh(1) utility
	and will not allow anything matching this list. The sshexec
	utility does not allow mixing options and operands: no option
	may be placed after destination, such options will be treated
	as the command or an argument.

	The following sshexec options are supported:

	ssh=ssh-command
		Instead of looking for ssh in PATH, the sshexec utility
		shall use ssh-command, which it will look for in PATH
		if it is only a file name (does not contain a slash (/)).

	dir=directory
		In the remote, change working directory to directory
		before executing command.

	cd=strict
		Fail without executing the command if it's not possible
		to set directory as the remote working directory.

	cd=lax
		Continue (but warn) executing the command even if it's
		not possible to set directory as the remote working
		directory.

	[fd]>=file
		After changing working directory (assuming one is
		specified), create or truncate the specified file and
		open it for writing, using file descriptor number fd.
		(Default fd is 1 (standard output).)

	[fd]>>=file
		After changing working directory (assuming one is
		specified), create the specified file if it does not
		exist and open it for writing in append-mode, using
		file descriptor number fd. (Default fd is 1
		(standard output).)

	[fd]>|=file
		After changing working directory (assuming one is
		specified), create the specified file, but fail if it
		already exists, and open it for writing, using file
		descriptor number fd. (Default fd is 1 (standard
		output).)

	[fd]<=file
		After changing working directory (assuming one is
		specified), open the specified file, for reading, using
		file descriptor number fd. (Default fd is 0 (standard
		input).)

	[fd]<>=file
		After changing working directory (assuming one is
		specified), open the specified file, for reading and
		writing, creating it if it does not already exist,
		using file descriptor number fd. (Default fd is 0
		(standard input).)

	[fd]{>,>>,>|}&=file
		Duplicate the file descriptor fd giving the new file
		descriptor the number file. (Default fd is 1 (standard
		output).)

	[fd]{>,>>,>|}&=-
		Close the file descriptor fd. (Default fd is 1
		(standard output).)

	[fd]{<,<>}&=file
		Duplicate the file descriptor fd giving the new file
		descriptor the number file. (Default fd is 0 (standard
		input).)

	[fd]{<,<>}&=-
		Close the file descriptor fd. (Default fd is 0
		(standard input).)

	asis=asis-marker
		Any argument equal to asis-marker will be skipped over
		and instead the next argument (regardless of whether
		it to is equal to asis-marker) will be interpreted as
		raw shell code string that shall be inserted without
		escaping.

	masis=asis-count
		If specified, asis-marker shall only have it's specified
		affect up to asis-count times.

OPERANDS
	The following operands are supported:

	destination
		The destination to connect and log into. It shall be
		eitherin the form [user@]hostname[:directory] or in the
		form ssh[exec]://[user@]hostname[:port][/directory].

		user shall be the name of the remote user. If not
		specified, the name of the local user running the	
		utility will be used.

		hostname shall be the address to the remote machine.

		port shall be the port or service name for the port
		to connect to on the remote machine.

		directory shall be directory to change the remote
		working directory. This is an alternative to (with the
		exact same behaviour) to the dir option and cannot be
		combined with it.

	command [argument] ...
		Whereas the ssh(1) utility would simply join the command
		and argument arguments with a space between each of
		them as pass it to the remote shell for execution, the
		sshexec utility forces the remote shell to treat each
		of the as separate arguments and cause the shell to
		executing them as a non-builtin command.

		command must not contain an equals sign (=) or be just
		a dash ("-").

BUGS
	The remote shell must be sufficiently similar to sh(1posix).
	Namely, it must support the cd builtin command and the commands
	exec and printf is expected by POSIX. Additionally, it must
	support "$( )", ' ', and &&, and argument separation with the
	SP character. The remote shell must also not treat any
	alphanumeric character, underscore (_) or slash (/) as special
	characters.

SEE ALSO
	ssh(1), sshcd(1)