intro.8 (3d45e180f437865262fc7c39fc3239641f305737) | intro.8 (a8f838798e01deb60a7835a75a29b91fe22ad9ac) |
---|---|
1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 51 unchanged lines hidden (view full) --- 60.Ql Xr inetd 61and 62.Ql Xr ftpd 63are also described. 64The section 65.Ql Xr crash 66should be consulted to understand how to interpret system 67crash dumps. | 1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 51 unchanged lines hidden (view full) --- 60.Ql Xr inetd 61and 62.Ql Xr ftpd 63are also described. 64The section 65.Ql Xr crash 66should be consulted to understand how to interpret system 67crash dumps. |
68.Pp 69All commands set an exit status. 70Its value may be tested 71to see if the command completed normally. 72Unless otherwise noted (rare), the value 0 signifies successful 73completion of the command, while a value >0 indicates an error. 74Some commands attempt to describe the nature of the failure by using 75error codes defined in 76.Xr sysexits 3 , 77or set the status to arbitrary values >0 (typically 1), but many 78such values are not described in the manual. |
|
68.Sh HISTORY 69The 70.Nm 71section manual page appeared in 72.Bx 4.2 . | 79.Sh HISTORY 80The 81.Nm 82section manual page appeared in 83.Bx 4.2 . |