// daemon.cpp
// ~~~~~~~~~~
//
-// Copyright (c) 2003-2016 Christopher M. Kohlhoff (chris at kohlhoff dot com)
+// Copyright (c) 2003-2017 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/io_context.hpp>
#include <boost/asio/ip/udp.hpp>
#include <boost/asio/signal_set.hpp>
#include <boost/array.hpp>
class udp_daytime_server
{
public:
- udp_daytime_server(boost::asio::io_service& io_service)
- : socket_(io_service, udp::endpoint(udp::v4(), 13))
+ udp_daytime_server(boost::asio::io_context& io_context)
+ : socket_(io_context, udp::endpoint(udp::v4(), 13))
{
start_receive();
}
void handle_receive(const boost::system::error_code& ec)
{
- if (!ec || ec == boost::asio::error::message_size)
+ if (!ec)
{
using namespace std; // For time_t, time and ctime;
time_t now = time(0);
{
try
{
- boost::asio::io_service io_service;
+ boost::asio::io_context io_context;
// 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.
- udp_daytime_server server(io_service);
+ udp_daytime_server server(io_context);
// 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.
- boost::asio::signal_set signals(io_service, SIGINT, SIGTERM);
+ boost::asio::signal_set signals(io_context, SIGINT, SIGTERM);
signals.async_wait(
- boost::bind(&boost::asio::io_service::stop, &io_service));
+ boost::bind(&boost::asio::io_context::stop, &io_context));
- // 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
+ // Inform the io_context that we are about to become a daemon. The
+ // io_context cleans up any internal resources, such as threads, that may
// interfere with forking.
- io_service.notify_fork(boost::asio::io_service::fork_prepare);
+ io_context.notify_fork(boost::asio::io_context::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
//
// 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
+ // destroyed. As the io_context object is a local variable, this means
// we do not have to call:
//
- // io_service.notify_fork(boost::asio::io_service::fork_parent);
+ // io_context.notify_fork(boost::asio::io_context::fork_parent);
//
// However, this line should be added before each call to exit() if
- // using a global io_service object. An additional call:
+ // using a global io_context object. An additional call:
//
- // io_service.notify_fork(boost::asio::io_service::fork_prepare);
+ // io_context.notify_fork(boost::asio::io_context::fork_prepare);
//
// should also precede the second fork().
exit(0);
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
+ // Inform the io_context that we have finished becoming a daemon. The
+ // io_context uses this opportunity to create any internal file descriptors
// that need to be private to the new process.
- io_service.notify_fork(boost::asio::io_service::fork_child);
+ io_context.notify_fork(boost::asio::io_context::fork_child);
- // The io_service can now be used normally.
+ // The io_context can now be used normally.
syslog(LOG_INFO | LOG_USER, "Daemon started");
- io_service.run();
+ io_context.run();
syslog(LOG_INFO | LOG_USER, "Daemon stopped");
}
catch (std::exception& e)