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;

}

}

【论文复现】一种基于价格弹性矩阵的居民峰谷分时电价激励策略【需求响应】(Matlab代码实现)内容概要:本文介绍了一种基于价格弹性矩阵的居民峰谷分时电价激励策略,旨在通过需求响应机制优化电力系统的负荷分布。该研究利用Matlab进行代码实现,构建了居民用电行为与电价变动之间的价格弹性模型,通过分析不同时间段电价调整对用户用电习惯的影响,设计合理的峰谷电价方案,引导用户错峰用电,从而实现电网负荷的削峰填谷,提升电力系统运行效率与稳定性。文中详细阐述了价格弹性矩阵的构建方法、优化目标函数的设计以及求解算法的实现过程,并通过仿真验证了所提策略的有效性。; 适合人群:具备一定电力系统基础知识和Matlab编程能力,从事需求响应、电价机制研究或智能电网优化等相关领域的科研人员及研究生。; 使用场景及目标:①研究居民用电行为对电价变化的响应特性;②设计并仿真基于价格弹性矩阵的峰谷分时电价激励策略;③实现需求响应下的电力负荷优化调度;④为电力公司制定科学合理的电价政策提供理论支持和技术工具。; 阅读建议:建议读者结合提供的Matlab代码进行实践操作,深入理解价格弹性建模与优化求解过程,同时可参考文中方法拓展至其他需求响应场景,如工业用户、商业楼宇等,进一步提升研究的广度与深度。
针对TC275微控制器平台,基于AUTOSAR标准的引导加载程序实现方案 本方案详细阐述了一种专为英飞凌TC275系列微控制器设计的引导加载系统。该系统严格遵循汽车开放系统架构(AUTOSAR)规范进行开发,旨在实现可靠的应用程序刷写与启动管理功能。 核心设计严格遵循AUTOSAR分层软件架构。基础软件模块(BSW)的配置与管理完全符合标准要求,确保了与不同AUTOSAR兼容工具链及软件组件的无缝集成。引导加载程序本身作为独立的软件实体,实现了与上层应用软件的完全解耦,其功能涵盖启动阶段的硬件初始化、完整性校验、程序跳转逻辑以及通过指定通信接口(如CAN或以太网)接收和验证新软件数据包。 在具体实现层面,工程代码重点处理了TC275芯片特有的多核架构与内存映射机制。代码包含了对所有必要外设驱动(如Flash存储器驱动、通信控制器驱动)的初始化与抽象层封装,并设计了严谨的故障安全机制与回滚策略,以确保在软件更新过程中出现意外中断时,系统能够恢复到已知的稳定状态。整个引导流程的设计充分考虑了时序确定性、资源占用优化以及功能安全相关需求,为汽车电子控制单元的固件维护与升级提供了符合行业标准的底层支持。 资源来源于网络分享,仅用于学习交流使用,请勿用于商业,如有侵权请联系我删除!
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值