HTML中forks的含义,doc/html/boost_asio/example/cpp03/fork/daemon.cpp

这个示例展示了如何使用Boost.Asio库在C++中实现一个UDP日间服务器。服务器接收请求并发送当前时间作为响应。代码涉及信号处理、守护进程化、错误处理和I/O上下文操作。

doc/html/boost_asio/example/cpp03/fork/daemon.cpp

//

// daemon.cpp

// ~~~~~~~~~~

//

// 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

#include

#include

#include

#include

#include

#include

#include

#include

using boost::asio::ip::udp;

class udp_daytime_server

{

public:

udp_daytime_server(boost::asio::io_context& io_context)

: socket_(io_context, 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)

{

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 recv_buffer_;

};

int main()

{

try

{

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_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_context, SIGINT, SIGTERM);

signals.async_wait(

boost::bind(&boost::asio::io_context::stop, &io_context));

// 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_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

// also a prerequisite for the subsequent call to setsid().

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_context object is a local variable, this means

// we do not have to call:

//

// 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_context object. An additional call:

//

// io_context.notify_fork(boost::asio::io_context::fork_prepare);

//

// should also precede the second fork().

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.

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);

// A second fork ensures the process cannot acquire a controlling terminal.

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.

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_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_context.notify_fork(boost::asio::io_context::fork_child);

// The io_context can now be used normally.

syslog(LOG_INFO | LOG_USER, "Daemon started");

io_context.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;

}

}

内容概要:本文系统阐述了企业新闻发稿在生成式引擎优化(GEO)时代下的全渠道策略与效果评估体系,涵盖当前企业传播面临的预算、资源、内容与效果评估四大挑战,并深入分析2025年新闻发稿行业五大趋势,包括AI驱动的智能化转型、精准化传播、首发内容价值提升、内容资产化及数据可视化。文章重点解析央媒、地方官媒、综合门户和自媒体四类媒体资源的特性、传播优势与发稿策略,提出基于内容适配性、时间节奏、话题设计的策略制定方法,并构建涵盖品牌价值、销售转化与GEO优化的多维评估框架。此外,结合“传声港”工具实操指南,提供AI智能投放、效果监测、自媒体管理与舆情应对的全流程解决方案,并针对科技、消费、B2B、区域品牌四大行业推出定制化发稿方案。; 适合人群:企业市场/公关负责人、品牌传播管理者、数字营销从业者及中小企业决策者,具备一定媒体传播经验并希望提升发稿效率与ROI的专业人士。; 使用场景及目标:①制定科学的新闻发稿策略,实现从“流量思维”向“价值思维”转型;②构建央媒定调、门户扩散、自媒体互动的立体化传播矩阵;③利用AI工具实现精准投放与GEO优化,提升品牌在AI搜索中的权威性与可见性;④通过数据驱动评估体系量化品牌影响力与销售转化效果。; 阅读建议:建议结合文中提供的实操清单、案例分析与工具指南进行系统学习,重点关注媒体适配性策略与GEO评估指标,在实际发稿中分阶段试点“AI+全渠道”组合策略,并定期复盘优化,以实现品牌传播的长期复利效应。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值