ftp-proxy can only open one listening socket, so to use it with
both IPv4 and IPv6, two instances are required. Now that rc.subr
does exact matches of the process name, we could add a separate
rc script for this. Do we want to do this?

(snmpd and ntpd have the same restriction, but don't have a simple
command line flag that would allow them to be handled in this way).

Index: rc.d/ftpproxy6
===================================================================
RCS file: rc.d/ftpproxy6
diff -N rc.d/ftpproxy6
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ rc.d/ftpproxy6      12 Sep 2015 12:16:37 -0000
@@ -0,0 +1,11 @@
+#!/bin/sh
+#
+# $OpenBSD$
+
+daemon="/usr/sbin/ftp-proxy -6"
+
+. /etc/rc.d/rc.subr
+
+rc_reload=NO
+
+rc_cmd $1
Index: rc.conf
===================================================================
RCS file: /cvs/src/etc/rc.conf,v
retrieving revision 1.204
diff -u -p -r1.204 rc.conf
--- rc.conf     3 Aug 2015 04:19:25 -0000       1.204
+++ rc.conf     12 Sep 2015 12:16:37 -0000
@@ -22,6 +22,7 @@ dhcrelay_flags=NO     # for normal use: "-i 
 dvmrpd_flags=NO
 ftpd_flags=NO          # set to NO if ftpd is running out of inetd
 ftpproxy_flags=NO
+ftpproxy6_flags=NO
 hostapd_flags=NO
 hotplugd_flags=NO
 httpd_flags=NO
@@ -40,7 +41,7 @@ mopd_flags=NO
 mrouted_flags=NO       # be sure to enable multicast_router below
 npppd_flags=NO
 nsd_flags=NO
-ntpd_flags=
+ntpd_flags=NO
 ospfd_flags=NO
 ospf6d_flags=NO
 pflogd_flags=          # add more flags, e.g. "-s 256"
Index: rc
===================================================================
RCS file: /cvs/src/etc/rc,v
retrieving revision 1.460
diff -u -p -r1.460 rc
--- rc  28 Aug 2015 18:10:46 -0000      1.460
+++ rc  12 Sep 2015 12:16:37 -0000
@@ -488,7 +488,7 @@ if ifconfig lo0 inet6 >/dev/null 2>&1; t
 fi
 
 start_daemon hostapd lpd smtpd slowcgi httpd ftpd
-start_daemon ftpproxy tftpd tftpproxy identd inetd rarpd bootparamd
+start_daemon ftpproxy ftpproxy6 tftpd tftpproxy identd inetd rarpd bootparamd
 start_daemon rbootd mopd spamd spamlogd sndiod
 echo '.'
 

Reply via email to