docs/126451: Exit status of nc(1) is not documented
Ronald F.Guilmette
rfg at tristatelogic.com
Mon Aug 11 10:40:02 UTC 2008
>Number: 126451
>Category: docs
>Synopsis: Exit status of nc(1) is not documented
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Aug 11 10:40:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Ronald F. Guilmette
>Release: FreeBSD 7.0-RELEASE i386
>Organization:
Infinite Monkeys & Co. LLC
>Environment:
System: FreeBSD 7.0-RELEASE
>Description:
The man page for nc(1) fails to document the possible exit stati
of the program.
>How-To-Repeat:
man 1 nc
>Fix:
Add an EXIT STATUS section to the man page for nc(1).
The exit status seems to be 0 if all goes well, or else 1 if any
of the following errors occurs: (a) hostname given on the command
line does not resolve or (b) connection is refused by the remote
host or (c) connection to remote host times out before connection
is established or (d) -l option used with privledged portno (<1024)
when nc is executed by an unprivledged user or (e) -l option used,
but hostname does not correspond to any IP address associated with
any local IP interface.
There are probably man other conditions that could be associated
with a non-zero exit status. Ideally, they should all be listed
in the man page.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-doc
mailing list