diff options
author | Denis Vlasenko <vda.linux@googlemail.com> | 2007-01-11 17:20:00 +0000 |
---|---|---|
committer | Denis Vlasenko <vda.linux@googlemail.com> | 2007-01-11 17:20:00 +0000 |
commit | f7996f3b700a22797565e9aa57e251e6e3ac1e4d (patch) | |
tree | af4e797eef0a65f4e3dba94b325da0ec08452d36 /docs/sigint.htm | |
parent | 3821fb13ea404d243115ff8ec161273b62826513 (diff) | |
download | busybox-w32-f7996f3b700a22797565e9aa57e251e6e3ac1e4d.tar.gz busybox-w32-f7996f3b700a22797565e9aa57e251e6e3ac1e4d.tar.bz2 busybox-w32-f7996f3b700a22797565e9aa57e251e6e3ac1e4d.zip |
Trailing whitespace removal over entire tree
Diffstat (limited to 'docs/sigint.htm')
-rw-r--r-- | docs/sigint.htm | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/sigint.htm b/docs/sigint.htm index 6fe76bbef..e230f4df7 100644 --- a/docs/sigint.htm +++ b/docs/sigint.htm | |||
@@ -40,7 +40,7 @@ scripts using <code>Control-C</code>. Or have interactive applications | |||
40 | that don't behave right when sending SIGINT. Examples are emacs'es | 40 | that don't behave right when sending SIGINT. Examples are emacs'es |
41 | that die on Control-g or shellscript statements that sometimes are | 41 | that die on Control-g or shellscript statements that sometimes are |
42 | executed and sometimes not, apparently not determined by the user's | 42 | executed and sometimes not, apparently not determined by the user's |
43 | intention. | 43 | intention. |
44 | 44 | ||
45 | 45 | ||
46 | </td></tr><tr><th valign=top align=left>Required knowledge: </th> | 46 | </td></tr><tr><th valign=top align=left>Required knowledge: </th> |
@@ -101,7 +101,7 @@ just exit. | |||
101 | 101 | ||
102 | <p>Now imagine the user hits C-c while a shellscript is executing its | 102 | <p>Now imagine the user hits C-c while a shellscript is executing its |
103 | first program. The following programs receive SIGINT: program1 and | 103 | first program. The following programs receive SIGINT: program1 and |
104 | also the shell executing the script. program1 exits. | 104 | also the shell executing the script. program1 exits. |
105 | 105 | ||
106 | <p>But what should the shell do? If we say that it is only the | 106 | <p>But what should the shell do? If we say that it is only the |
107 | innermost's programs business to react on SIGINT, the shell will do | 107 | innermost's programs business to react on SIGINT, the shell will do |
@@ -351,7 +351,7 @@ that do not properly communicate the required information up to the | |||
351 | calling program. | 351 | calling program. |
352 | 352 | ||
353 | <p>Unless a program messes with signal handling, the system does this | 353 | <p>Unless a program messes with signal handling, the system does this |
354 | automatically. | 354 | automatically. |
355 | 355 | ||
356 | <p>There are programs that want to exit on SIGINT, but they don't let | 356 | <p>There are programs that want to exit on SIGINT, but they don't let |
357 | the system do the automatic exit, because they want to do some | 357 | the system do the automatic exit, because they want to do some |
@@ -425,7 +425,7 @@ Notes: | |||
425 | special numeric value. People often assume this since the manuals for | 425 | special numeric value. People often assume this since the manuals for |
426 | shells often list some return value for exactly this. But this is just | 426 | shells often list some return value for exactly this. But this is just |
427 | a convention for your shell script. It does not work from one UNIX API | 427 | a convention for your shell script. It does not work from one UNIX API |
428 | program to another. | 428 | program to another. |
429 | 429 | ||
430 | <P>All that happens is that the shell sets the "$?" variable to a | 430 | <P>All that happens is that the shell sets the "$?" variable to a |
431 | special numeric value for the convenience of your script, because your | 431 | special numeric value for the convenience of your script, because your |
@@ -571,7 +571,7 @@ comments the scripts echo. | |||
571 | <tr valign=top align=left> | 571 | <tr valign=top align=left> |
572 | <td>IUE</td> | 572 | <td>IUE</td> |
573 | <td>The shell executing a script exits immediately if it receives | 573 | <td>The shell executing a script exits immediately if it receives |
574 | SIGINT.</td> | 574 | SIGINT.</td> |
575 | <td>4.4BSD ash (ash), NetBSD, FreeBSD prior to 3.0/22.8</td> | 575 | <td>4.4BSD ash (ash), NetBSD, FreeBSD prior to 3.0/22.8</td> |
576 | <td>The editor session is lost and subsequent commands are not | 576 | <td>The editor session is lost and subsequent commands are not |
577 | executed.</td> | 577 | executed.</td> |
@@ -605,7 +605,7 @@ will further commands from the script be executed. </td> | |||
605 | signal (either it had the default handler for SIGINT or it killed | 605 | signal (either it had the default handler for SIGINT or it killed |
606 | itself). </td> | 606 | itself). </td> |
607 | <td>bash (Linux /bin/sh), most commercial /bin/sh, FreeBSD /bin/sh | 607 | <td>bash (Linux /bin/sh), most commercial /bin/sh, FreeBSD /bin/sh |
608 | from 3.0/2.2.8.</td> | 608 | from 3.0/2.2.8.</td> |
609 | <td>The editor continues as normal and subsequent commands are | 609 | <td>The editor continues as normal and subsequent commands are |
610 | executed. </td> | 610 | executed. </td> |
611 | <td>The editor continues as normal and subsequent commands are | 611 | <td>The editor continues as normal and subsequent commands are |
@@ -615,7 +615,7 @@ child exits, but only if the child exited with signal status. If | |||
615 | the child did a normal exit (even if it received SIGINT, but catches | 615 | the child did a normal exit (even if it received SIGINT, but catches |
616 | it), the script will continue. </td> | 616 | it), the script will continue. </td> |
617 | <td>The child must be implemented right, or the user will not be able | 617 | <td>The child must be implemented right, or the user will not be able |
618 | to break shell scripts reliably.</td> | 618 | to break shell scripts reliably.</td> |
619 | </tr> | 619 | </tr> |
620 | 620 | ||
621 | </table> | 621 | </table> |