svn commit: r279603 - in head: bin/rcp usr.bin/rlogin usr.bin/rsh

[Edward Tomasz Napierała]

On 0305T1555, Gleb Smirnoff wrote:
> On Thu, Mar 05, 2015 at 03:40:37PM +0300, Slawa Olhovchenkov wrote:
> S> > nc(1), which is a pure socket testing tool. For telnet(1) this
> S> > capability is a side effect.
> S> 
> S> You don't try this in practice.
> S> % nc zxy.spb.ru 81
> S> %
> S> % telnet zxy.spb.ru 81
> S> Trying 195.70.199.98...
> S> telnet: connect to address 195.70.199.98: Connection refused
> S> telnet: Unable to connect to remote host
> S> 
> S> nc is not usable. 
> 
> Yes, this how unix way works. Command has return value, or
> you can use '-v', of you want it to be chatty.

Actually, not giving error message on error by default seems quite
broken to me.  Standard UNIX utilities don't fail silently:

% cat /bin/nope
cat: /bin/nope: No such file or directory