about summary refs log tree commit diff
path: root/doc/tryexec.html
blob: c9f049715c07fabcf21ff0a16c1a877bea7a7bbb (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
<html>
  <head>
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  <meta http-equiv="Content-Language" content="en" />
  <title>execline: the tryexec command</title>
  <meta name="Description" content="execline: the tryexec command" />
  <meta name="Keywords" content="execline command tryexec" />
  <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> -->
 </head>
<body>

<p>
<a href="index.html">execline</a><br />
<a href="http://skarnet.org/software/">Software</a><br />
<a href="http://skarnet.org/">skarnet.org</a>
</p>

<h1> The <tt>tryexec</tt> program </h1>

<p>
<tt>tryexec</tt> executes into a command line, with a fallback.
</p>

<h2> Interface </h2>

<p>
 In an <a href="execlineb.html">execlineb</a> script:
</p>

<pre>
     tryexec [ -n ] [ -c ] [ -l ] [ -a argv0 ] { <em>prog1...</em> } <em>prog2...</em>
</pre>

<ul>
 <li> <tt>tryexec</tt> reads <em>prog1...</em> in a
<a href="el_semicolon.html">block</a>. It then executes into it,
completely forgetting <em>prog2...</em> </li>
 <li> If for some reason the <tt>execve()</tt> fails - for instance,
a non-executable <em>prog1</em> - then <tt>tryexec</tt> executes
into <em>prog2...</em> instead. </li>
</ul>

<h2> Options </h2>

<ul>
 <li> <tt>-n</tt>&nbsp;: reverse <em>prog1...</em> and <em>prog2...</em>'s
role. The latter becomes the main execution path and the former becomes
the fallback. </li>
</ul>

<p>
  The <tt>-c</tt>, <tt>-l</tt> and <tt>-a</tt> options have the same
semantics as with the <a href="exec.html">exec</a> program.
</p>

<h2> Notes </h2>

<ul>
 <li> <tt>tryexec <em>prog1...</em> "" <em>prog2...</em></tt> would be
equivalent to
<tt>sh -c 'exec <em>prog1...</em> || exec <em>prog2...</em>'</tt>, if
such a shell construct existed. Unfortunately, the shell language does
not offer that functionality. </li>
</ul>

</body>
</html>