ASIO例子中的，守護進程初始化

標籤：des   style   blog   http   color   io   os   使用   ar   

// daemon.cpp// 該例子示範結合ASIO和POSIX標準系統的fork系統調用，產生一個守護進程。//時間伺服器？// Copyright (c) 2003-2014 Christopher M. Kohlhoff (chris at kohlhoff dot com)//// Distributed under the Boost Software License, Version 1.0. (See accompanying// file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)//#include <boost/asio/io_service.hpp>#include <boost/asio/ip/udp.hpp>#include <boost/asio/signal_set.hpp>#include <boost/array.hpp>#include <boost/bind.hpp>#include <ctime>#include <iostream>#include <syslog.h>#include <unistd.h>using boost::asio::ip::udp;//定義個UDP時間伺服器類class udp_daytime_server{public:  udp_daytime_server(boost::asio::io_service& io_service)    : socket_(io_service, udp::endpoint(udp::v4(), 13))  {      //執行個體化後立刻開始接收    start_receive();  }private:  void start_receive()  {    socket_.async_receive_from(        boost::asio::buffer(recv_buffer_), remote_endpoint_,        boost::bind(&udp_daytime_server::handle_receive, this, _1));  }  void handle_receive(const boost::system::error_code& ec)  {    if (!ec || ec == boost::asio::error::message_size)    {      using namespace std; // For time_t, time and ctime;      time_t now = time(0);      std::string message = ctime(&now);      boost::system::error_code ignored_ec;      socket_.send_to(boost::asio::buffer(message),          remote_endpoint_, 0, ignored_ec);    }    start_receive();  }  udp::socket socket_;  udp::endpoint remote_endpoint_;  boost::array<char, 1> recv_buffer_;};int main(){  try  {    boost::asio::io_service io_service;    // Initialise the server before becoming a daemon. If the process is    // started from a shell, this means any errors will be reported back to the    // user.    //如果程式是通過shell啟動的，那麼所有錯誤將返回給使用者。    udp_daytime_server server(io_service);    // Register signal handlers so that the daemon may be shut down. You may    // also want to register for other signals, such as SIGHUP to trigger a    // re-read of a configuration file.    //註冊訊號handlers。以便退出，停止。    boost::asio::signal_set signals(io_service, SIGINT, SIGTERM);    signals.async_wait(        boost::bind(&boost::asio::io_service::stop, &io_service));    // Inform the io_service that we are about to become a daemon. The    // io_service cleans up any internal resources, such as threads, that may    // interfere with forking.    //通知io_service，要將進程進行daemon化，io_service將清除任意內部資源？比如說線程，將會影響fork    io_service.notify_fork(boost::asio::io_service::fork_prepare);    // Fork the process and have the parent exit. If the process was started    // from a shell, this returns control to the user. Forking a new process is    // also a prerequisite for the subsequent call to setsid().    //fork該進程後，父進程退出。如果該進程是從shell啟動的，那麼對於使用者來說將是立刻返回。    //fork一個新的進程也是隨後調用setsid的先決條件。setsid建立一個新的會話。    //這些步驟是守護進程編程規則。詳情見APUE第十三章。    if (pid_t pid = fork())    {      if (pid > 0)      {        // We‘re in the parent process and need to exit.        //        // When the exit() function is used, the program terminates without        // invoking local variables‘ destructors. Only global variables are        // destroyed. As the io_service object is a local variable, this means        // we do not have to call:        //        //   io_service.notify_fork(boost::asio::io_service::fork_parent);        //        // However, this line should be added before each call to exit() if        // using a global io_service object. An additional call:        //        //   io_service.notify_fork(boost::asio::io_service::fork_prepare);        //        // should also precede the second fork().          /*              此處為父進程邏輯，當exit函數調用後。程式將不會調用局部變數的解構函式，而全域變數的解構函式會被調用。          因為io_service是局部對象，所以這就意味著我們沒有必要調用          io_service.notify_fork(boost::asio::io_service::fork_parent);          但是，當使用io_service作為全域對象的時候，是有必要在每次調用exit之前調用以上一行代碼。          另外需要在第二次fork前調用o_service.notify_fork(boost::asio::io_service::fork_prepare);          */        exit(0);      }      else      {        syslog(LOG_ERR | LOG_USER, "First fork failed: %m");        return 1;      }    }    // Make the process a new session leader. This detaches it from the    // terminal.    //開啟新的會話，並作為會話leader，與終端分離。    setsid();    // A process inherits its working directory from its parent. This could be    // on a mounted filesystem, which means that the running daemon would    // prevent this filesystem from being unmounted. Changing to the root    // directory avoids this problem.    //為了防止守護進程所在的檔案系統未被掛載，故更改到根目錄。    chdir("/");    // The file mode creation mask is also inherited from the parent process.    // We don‘t want to restrict the permissions on files created by the    // daemon, so the mask is cleared.    //為了不想限制守護進程建立的檔案的許可權，故umask設為0    umask(0);    // A second fork ensures the process cannot acquire a controlling terminal.    //第二次fork保證該進程無法擷取終端，因為不是leader？    if (pid_t pid = fork())    {      if (pid > 0)      {        exit(0);      }      else      {        syslog(LOG_ERR | LOG_USER, "Second fork failed: %m");        return 1;      }    }    // Close the standard streams. This decouples the daemon from the terminal    // that started it.    //關閉標準輸入輸出出錯，與終端分開。    close(0);    close(1);    close(2);    // We don‘t want the daemon to have any standard input.    //不需要任何標準輸入。為什麼這麼用？    if (open("/dev/null", O_RDONLY) < 0)    {      syslog(LOG_ERR | LOG_USER, "Unable to open /dev/null: %m");      return 1;    }    // Send standard output to a log file.    //重新導向標準輸出至log檔案    const char* output = "/tmp/asio.daemon.out";    const int flags = O_WRONLY | O_CREAT | O_APPEND;    const mode_t mode = S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH;    if (open(output, flags, mode) < 0)    {      syslog(LOG_ERR | LOG_USER, "Unable to open output file %s: %m", output);      return 1;    }    // Also send standard error to the same log file.    if (dup(1) < 0)    {      syslog(LOG_ERR | LOG_USER, "Unable to dup output descriptor: %m");      return 1;    }    // Inform the io_service that we have finished becoming a daemon. The    // io_service uses this opportunity to create any internal file descriptors    // that need to be private to the new process.    //告知io_service已變成守護進程。    io_service.notify_fork(boost::asio::io_service::fork_child);    // The io_service can now be used normally.    syslog(LOG_INFO | LOG_USER, "Daemon started");    io_service.run();    syslog(LOG_INFO | LOG_USER, "Daemon stopped");  }  catch (std::exception& e)  {    syslog(LOG_ERR | LOG_USER, "Exception: %s", e.what());    std::cerr << "Exception: " << e.what() << std::endl;  }}

 

ASIO例子中的，守護進程初始化