我正在开发一个“本地”PHP项目。 这是一个在Debian VM中运行的PHP应用程序，用于用户自己的PC上。
我有一些从/etc/init.d作为根服务运行的python脚本，它们负责处理应用程序更新，日志，与USB外围设备的通信以及杂项。
编辑1：该VM是一个Turnkey Linux LAMP映像，Python版本是2.7.3，MySQL 5.5.47
PHP应用程序通过TCP套接字与python服务对话，发送用户需要的特定任务的请求。
现在，我试图让用户select让MySQL服务器只绑定到本地主机还是与networking上的其他用户共享。 为此，我有python服务通过my.cnf文件，并注释掉bind-address = 127.0.0.1行，或者取消注释，使服务器再次本地。
在my.cnf编辑之后，python脚本调用/etc/init.d/mysql restart以使更改生效。
问题是，现在mysql最终收听了python服务正在侦听的PHP请求的端口，如果我需要重新启动服务Python失败，声称它不能打开端口，因为它已经被使用了。
我无法弄清楚为什么地狱会最终在Python服务使用的端口监听，而不是如my.cnf文件所说的3306。
另外，如果我ssh到虚拟机，并手动重新启动mysql它回到侦听3306，我可以启动python服务确定。
python一些代码：
RECV_BUFFER = 4096 DAEMON_PORT = 5555 daemon_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM) daemon_socket.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1) daemon_socket.bind(("localhost", DAEMON_PORT)) daemon_socket.listen(10) //// SOCKET HANDLING, QUEUE and etc if (data =='share:enable'): import fileinput import re import subprocess for line in fileinput.input('/etc/mysql/my.cnf', inplace = 1): print re.sub(r'#*bind-address',"#bind-address", line), print subprocess.check_output(['/etc/init.d/mysql','restart']) 示例输出：
$> lsof -i ... ... python 17219 root 4u IPv4 25311 0t0 TCP localhost:5555 (LISTEN) mysqld 20773 mysql 10u IPv4 33299 0t0 TCP localhost:mysql (LISTEN) $> echo 'share:enable' | netcat localhost 5555 $> lsof -i .... .... python 17219 root 4u IPv4 25311 0t0 TCP localhost:5555 (LISTEN) mysqld_sa 17361 root 4u IPv4 25311 0t0 TCP localhost:5555 (LISTEN) mysqld 17856 mysql 4u IPv4 25311 0t0 TCP localhost:5555 (LISTEN) mysqld 17856 mysql 13u IPv4 25782 0t0 TCP localhost:mysql (LISTEN) logger 17857 root 4u IPv4 25311 0t0 TCP localhost:5555 (LISTEN)
编辑2：添加我的my.cnf MySQLconfiguration文件。
# # The MySQL database server configuration file. # # You can copy this to one of: # - "/etc/mysql/my.cnf" to set global options, # - "~/.my.cnf" to set user-specific options. # # One can use all long options that the program supports. # Run program with --help to get a list of available options and with # --print-defaults to see which it would actually understand and use. # # For explanations see # http://dev.mysql.com/doc/mysql/en/server-system-variables.html # This will be passed to all mysql clients # It has been reported that passwords should be enclosed with ticks/quotes # escpecially if they contain "#" chars... # Remember to edit /etc/mysql/debian.cnf when changing the socket location. [client] port = 3306 socket = /var/run/mysqld/mysqld.sock # Here is entries for some specific programs # The following values assume you have at least 32M ram # This was formally known as [safe_mysqld]. Both versions are currently parsed. [mysqld_safe] socket = /var/run/mysqld/mysqld.sock nice = 0 [mysqld] # # * Basic Settings # user = mysql pid-file = /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port = 3306 basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp lc-messages-dir = /usr/share/mysql skip-external-locking # # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. bind-address = 127.0.0.1 # # * Fine Tuning # key_buffer = 16M max_allowed_packet = 16M thread_stack = 192K thread_cache_size = 8 # This replaces the startup script and checks MyISAM tables if needed # the first time they are touched myisam-recover = BACKUP #max_connections = 100 #table_cache = 64 #thread_concurrency = 10 # # * Query Cache Configuration # query_cache_limit = 1M query_cache_size = 16M # # * Logging and Replication # # Both location gets rotated by the cronjob. # Be aware that this log type is a performance killer. # As of 5.1 you can enable the log at runtime! #general_log_file = /var/log/mysql/mysql.log #general_log = 1 # # Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf. # # Here you can see queries with especially long duration #log_slow_queries = /var/log/mysql/mysql-slow.log #long_query_time = 2 #log-queries-not-using-indexes # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. #server-id = 1 #log_bin = /var/log/mysql/mysql-bin.log expire_logs_days = 10 max_binlog_size = 100M #binlog_do_db = include_database_name #binlog_ignore_db = include_database_name # # * InnoDB # # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. # Read the manual for more InnoDB related options. There are many! # # * Security Features # # Read the manual, too, if you want chroot! # chroot = /var/lib/mysql/ # # For generating SSL certificates I recommend the OpenSSL GUI "tinyca". # # ssl-ca=/etc/mysql/cacert.pem # ssl-cert=/etc/mysql/server-cert.pem # ssl-key=/etc/mysql/server-key.pem [mysqldump] #quick quote-names max_allowed_packet = 16M [mysql] #no-auto-rehash # faster start of mysql but no tab completition [isamchk] key_buffer = 16M # # * IMPORTANT: Additional settings that can override those from this file! # The files must end with '.cnf', otherwise they'll be ignored. # !includedir /etc/mysql/conf.d/
这是与MySQL和更多的与python做更less。
当你启动一个进程时，它会从创build它的进程中inheritance很多信息，包括它的文件描述符。 你的发现是，mysqlinheritance了你的进程产生的监听套接字。
要解决这个问题，你需要改变你的python代码，不要使用subprocess.Popen(..., close_fds=True) subprocess.check_output(...) ，而是使用subprocess.Popen(..., close_fds=True)
或者，在你的套接字上设置CLOEXEC标志将阻止它永远被inheritance – 虽然你需要testing这种行为在你的所有代码path中都能正常工作，并且没有什么奇怪的事情会发生。 以下是这样做的基础。
from fcntl import fcntl, FD_CLOEXEC, F_GETFD, F_SETFD flags = fcntl(socketfd, F_GETFD) flags |= FD_CLOEXEC fcntl(socketfd, F_SETFD, flags)
要么解决您的监听套接字问题。