Bug 173664

Summary: csup(1) manpage refers to "runsocks", which was part of net/socks5, which doesn't exist now
Product: Documentation Reporter: Wojciech A. Koszek <wkoszek>
Component: Books & ArticlesAssignee: Eitan Adler <eadler>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Wojciech A. Koszek freebsd_committer freebsd_triage 2012-11-16 18:50:00 UTC
I did 'man csup' in hope to find ready-to-use solution for getting csup(1) to work from behind the SOCKS5 proxy.

Manual page is referring to "standard runsocks" command.

I had to Google to learn it's a part of "net/socks5" port.

I tried pkg_add -r socks5

No such a port. After

portsnap fetch
portsnap extract

You can see this port doesn't exist anymore.

We need ready to use solution ("givemewhatevernecessarytomakeproxywork.sh") to get this configuration going quickly.

How-To-Repeat: man csup
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2013-02-09 00:39:44 UTC
Responsible Changed
From-To: freebsd-doc->eadler

I'll take it.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2013-02-09 00:44:10 UTC
State Changed
From-To: open->analyzed

awaiting approval or review prior to commit (no action needed from 
submitter)
Comment 3 dfilter service freebsd_committer freebsd_triage 2013-02-09 17:14:10 UTC
Author: eadler
Date: Sat Feb  9 17:13:54 2013
New Revision: 246594
URL: http://svnweb.freebsd.org/changeset/base/246594

Log:
  Reference something which exists instead of the non-existent runsocks
  program.
  
  PR:		docs/173664
  Submitted by:	wkoszek
  Approved by:	bcr (mentor)

Modified:
  head/usr.bin/csup/csup.1

Modified: head/usr.bin/csup/csup.1
==============================================================================
--- head/usr.bin/csup/csup.1	Sat Feb  9 17:13:51 2013	(r246593)
+++ head/usr.bin/csup/csup.1	Sat Feb  9 17:13:54 2013	(r246594)
@@ -24,7 +24,7 @@
 .\" $Id: cvsup.1,v 1.70 2003/03/04 18:23:46 jdp Exp $
 .\" $FreeBSD$
 .\"
-.Dd February 1, 2006
+.Dd Feburary 8, 2013
 .Dt CSUP 1
 .Os FreeBSD
 .Sh NAME
@@ -902,14 +902,14 @@ will work through any firewall which per
 port 5999 of the server host.
 .Sh USING csup WITH SOCKS
 .Nm
-can be used through a SOCKS proxy server with the standard
-.Nm runsocks
+can be used through a SOCKS proxy server with the
+.Nm tsocks
 command.
-Your
+The
 .Nm
 executable needs to be dynamically-linked with the system
 libraries for
-.Nm runsocks
+.Nm tsocks
 to work properly.
 .Sh USING ssh PORT FORWARDING
 As an alternative to SOCKS, a user behind a firewall can penetrate it
_______________________________________________
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org"
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2013-02-09 17:24:14 UTC
State Changed
From-To: analyzed->patched

committed
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2013-04-28 03:25:33 UTC
State Changed
From-To: patched->closed

Committed. Thanks!