systemD vs Thunder Feature Comparison
Created on June 21, 2022
| Sl | Feature | Systemd | Thunder |
| 1 | Init Script/Service format | Config Files (ini) | Json files |
| 2 | Main dependencies | Dbus | wpeframework plugins launcher |
| 3 | Standalone Init system | Yes | Need another Init system to launch Thunder |
| 4 | Running as Daemon | Yes | Yes |
| 5 | Cross service dependencies/events | yes | No |
| 6 | Parallel service startup | Yes | Yes |
| 7 | License | LGPL v2.1+ | ? |
| 8 | Filesystem mounting | .mount units | not supported |
| 9 | Initial service launcher | systemd | Initd/busybox init |
| 10 | RDK service launcher | systemd | WPEFramework plugins launcher |
| 11 | Total memory consumption (RPI) | 80M | 73M ? |
| 12 | logging | systemd-journald | /var/log/messages |
| 13 | Ability to support multiple log files | via journal filters | Not supported |
| 14 | Support for runlevels | targets | Not supported |
| 15 | Zombie processes | Processes can be configured for oneshot and there are no zombie occurances | |
| 16 | Open issues | ||
| “Monitor” plugin needs to support PluginLauncher processes |
Go To Top

