Shulou(Shulou.com)06/01 Report--

As long as there is a packet that conforms to the rules, the LED light will XY. How can this effect be achieved?

I have a lot of ways to compare it: use LOG target to send kernel logs, rsyslogd intercept, redirect to filter, call shell to operate LED lights. Although it is very roundabout, isn't it advocated to play like this on UNIX?

What is the most direct way? I think we should write an event target, and report the packet to user space through netlink as long as it matches. With this event target, even LOG can be distributed through user space's listen daemon. After all, doesn't the information from printk finally get syslog daemon through syslog system calls?

I really can't figure out why I want to process event in the kernel, just because it's more convenient to maintain timer. Moreover, the name acquisition is not good, I think this problem is more serious, although it really will not affect the function. Even if I could design a kernel-state event mechanism to trigger and handle events, I wouldn't assume that the mechanism is associated with any particular object. The receiver of the event can of course be a LED light, but can't it be a horn, power supply?

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.