c – 在多线程程序中如何使用boost :: asio正确处理fork()?

前端之家收集整理的这篇文章主要介绍了c – 在多线程程序中如何使用boost :: asio正确处理fork()?前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我在使用Boost Asio以多线程方式从多线程程序中正确处理创建子进程时遇到麻烦.

如果我理解正确,在Unix世界中启动一个子进程的方法调用fork(),然后调用exec *().另外,如果我正确理解,调用fork()将会重复所有的文件描述符等等,这些都需要在子进程中关闭,除非标记为FD_CLOEXEC(因此在调用exec *()时被原子关闭).

Boost Asio需要通过调用fork()才能正常通知调用notify_fork().但是,在多线程程序中,这会产生以下几个问题:

>如果我正确理解,默认情况下,插件是由子进程继承的.它们可以设置为SOCK_CLOEXEC – 但不能直接创建*,因此如果从另一个线程创建子进程,则导致定时窗口.
> notify_fork()要求没有其他线程调用任何其他io_service函数,也没有与io_service关联的任何其他I / O对象的任何函数.这似乎不是可行的 – 所有的程序是多线程的,因为一个原因.
>如果我理解正确,fork()和exec *()之间的任何函数调用都需要异步信号安全(见fork() documentation).没有关于notify_fork()调用异步信号安全的文档.实际上,如果我看看Boost Asio的源代码(至少在版本1.54中),可能会有pthread_mutex_lock的电话,这不是异步信号安全(参见Signal Concepts,还有其他的电话是不在白名单上).

问题#1我可以通过分离子进程和套接文件的创建来解决问题,以便我可以确保在创建的套接字和设置SOCK_CLOEXEC之间的窗口中不会创建子进程.问题#2是棘手的,我可能需要确保所有的asio处理程序线程都被阻止,做叉子,然后重新创建它们,这是最好的,最糟糕的是真的很糟糕(我的未决定时器呢? ).问题#3似乎完全不可能正确使用.

如何在一个多线程程序中与fork()exec *()正确使用Boost Asio?
…还是我“分叉”?

请让我知道,如果我误解了任何基本概念(我提出Windows编程,而不是* nix …).

编辑:
* – 实际上可以创建直接在Linux上设置的SOCK_CLOEXEC的套接字,从2.6.27开始可用(参见socket() documentation).在Windows上,相应的标志WSA_FLAG_NO_HANDLE_INHERIT可用于Windows 7 SP 1 / Windows Server 2008 R2 SP 1(参见WSASocket() documentation). OS X似乎并不支持.

解决方法

在多线程程序中,io_service::notify_fork()在孩子中调用不安全.但是,Boost.Asio希望它可以基于 fork() support进行调用,因为这是当孩子关闭父母以前的内部文件描述符并创建新的内容时.虽然Boost.Asio显式列出了调用io_service :: notify_fork()的前提条件,保证在fork()期间内部组件的状态,但是对 implementation的简要概述则表明std :: vector :: push_back()可能会从免费商店分配内存,并且分配不能保证是异步信号安全的.

就这样说,一个可能值得考虑的解决方案是fork(),当它仍然是单线程时.子进程将保持单线程,并在父进程通过进程间通信被告知执行fork()和exec()时执行.这种分离通过在执行fork()和exec()时消除管理多个线程的状态的需要来简化问题.

以下是一个完整的示例,演示此方法,多线程服务器将通过UDP接收文件名,子进程将执行fork()和exec()来运行文件名/usr/bin/touch.为了使这个例子变得更加可读,我已经选择使用stackful coroutines.

  1. #include <unistd.h> // execl,fork
  2. #include <iostream>
  3. #include <string>
  4. #include <boost/bind.hpp>
  5. #include <boost/asio.hpp>
  6. #include <boost/asio/spawn.hpp>
  7. #include <boost/make_shared.hpp>
  8. #include <boost/shared_ptr.hpp>
  9. #include <boost/thread.hpp>
  10.  
  11. /// @brief launcher receives a command from inter-process communication,/// and will then fork,allowing the child process to return to
  12. /// the caller.
  13. class launcher
  14. {
  15. public:
  16. launcher(boost::asio::io_service& io_service,boost::asio::local::datagram_protocol::socket& socket,std::string& command)
  17. : io_service_(io_service),socket_(socket),command_(command)
  18. {}
  19.  
  20. void operator()(boost::asio::yield_context yield)
  21. {
  22. std::vector<char> buffer;
  23. while (command_.empty())
  24. {
  25. // Wait for server to write data.
  26. std::cout << "launcher is waiting for data" << std::endl;
  27. socket_.async_receive(boost::asio::null_buffers(),yield);
  28.  
  29. // Resize buffer and read all data.
  30. buffer.resize(socket_.available());
  31. socket_.receive(boost::asio::buffer(buffer));
  32.  
  33. io_service_.notify_fork(boost::asio::io_service::fork_prepare);
  34. if (fork() == 0) // child
  35. {
  36. io_service_.notify_fork(boost::asio::io_service::fork_child);
  37. command_.assign(buffer.begin(),buffer.end());
  38. }
  39. else // parent
  40. {
  41. io_service_.notify_fork(boost::asio::io_service::fork_parent);
  42. }
  43. }
  44. }
  45.  
  46. private:
  47. boost::asio::io_service& io_service_;
  48. boost::asio::local::datagram_protocol::socket& socket_;
  49. std::string& command_;
  50. };
  51.  
  52. using boost::asio::ip::udp;
  53.  
  54. /// @brief server reads filenames from UDP and then uses
  55. /// inter-process communication to delegate forking and exec
  56. /// to the child launcher process.
  57. class server
  58. {
  59. public:
  60. server(boost::asio::io_service& io_service,short port)
  61. : io_service_(io_service),launcher_socket_(socket),socket_(boost::make_shared<udp::socket>(
  62. boost::ref(io_service),udp::endpoint(udp::v4(),port)))
  63. {}
  64.  
  65. void operator()(boost::asio::yield_context yield)
  66. {
  67. udp::endpoint sender_endpoint;
  68. std::vector<char> buffer;
  69. for (;;)
  70. {
  71. std::cout << "server is waiting for data" << std::endl;
  72. // Wait for data to become available.
  73. socket_->async_receive_from(boost::asio::null_buffers(),sender_endpoint,yield);
  74.  
  75. // Resize buffer and read all data.
  76. buffer.resize(socket_->available());
  77. socket_->receive_from(boost::asio::buffer(buffer),sender_endpoint);
  78. std::cout << "server got data: ";
  79. std::cout.write(&buffer[0],buffer.size());
  80. std::cout << std::endl;
  81.  
  82. // Write filename to launcher.
  83. launcher_socket_.async_send(boost::asio::buffer(buffer),yield);
  84. }
  85. }
  86.  
  87. private:
  88. boost::asio::io_service& io_service_;
  89. boost::asio::local::datagram_protocol::socket& launcher_socket_;
  90.  
  91. // To be used as a coroutine,server must be copyable,so make socket_
  92. // copyable.
  93. boost::shared_ptr<udp::socket> socket_;
  94. };
  95.  
  96. int main(int argc,char* argv[])
  97. {
  98. std::string filename;
  99.  
  100. // Try/catch provides exception handling,but also allows for the lifetime
  101. // of the io_service and its IO objects to be controlled.
  102. try
  103. {
  104. if (argc != 2)
  105. {
  106. std::cerr << "Usage: <port>\n";
  107. return 1;
  108. }
  109.  
  110. boost::thread_group threads;
  111. boost::asio::io_service io_service;
  112.  
  113. // Create two connected sockets for inter-process communication.
  114. boost::asio::local::datagram_protocol::socket parent_socket(io_service);
  115. boost::asio::local::datagram_protocol::socket child_socket(io_service);
  116. boost::asio::local::connect_pair(parent_socket,child_socket);
  117.  
  118. io_service.notify_fork(boost::asio::io_service::fork_prepare);
  119. if (fork() == 0) // child
  120. {
  121. io_service.notify_fork(boost::asio::io_service::fork_child);
  122. parent_socket.close();
  123. boost::asio::spawn(io_service,launcher(io_service,child_socket,filename));
  124. }
  125. else // parent
  126. {
  127. io_service.notify_fork(boost::asio::io_service::fork_parent);
  128. child_socket.close();
  129. boost::asio::spawn(io_service,server(io_service,parent_socket,std::atoi(argv[1])));
  130.  
  131. // Spawn additional threads.
  132. for (std::size_t i = 0; i < 3; ++i)
  133. {
  134. threads.create_thread(
  135. boost::bind(&boost::asio::io_service::run,&io_service));
  136. }
  137. }
  138.  
  139. io_service.run();
  140. threads.join_all();
  141. }
  142. catch (std::exception& e)
  143. {
  144. std::cerr << "Exception: " << e.what() << "\n";
  145. }
  146.  
  147. // Now that the io_service and IO objects have been destroyed,all internal
  148. // Boost.Asio file descriptors have been closed,so the execl should be
  149. // in a clean state. If the filename has been set,then exec touch.
  150. if (!filename.empty())
  151. {
  152. std::cout << "creating file: " << filename << std::endl;
  153. execl("/usr/bin/touch","touch",filename.c_str(),static_cast<char*>(0));
  154. }
  155. }

1号航站楼:

  1. $ls
  2. a.out example.cpp
  3. $./a.out 12345
  4. server is waiting for data
  5. launcher is waiting for data
  6. server got data: a
  7. server is waiting for data
  8. launcher is waiting for data
  9. creating file: a
  10. server got data: b
  11. server is waiting for data
  12. launcher is waiting for data
  13. creating file: b
  14. server got data: c
  15. server is waiting for data
  16. launcher is waiting for data
  17. creating file: c
  18. ctrl + c
  19. $ls
  20. a a.out b c example.cpp

2号航站楼:

  1. $nc -u 127.0.0.1 12345
  2. actrl + dbctrl + dcctrl + d

猜你在找的C&C++相关文章