[HN Gopher] Systemd Inhibitor Locks Deep Dive
___________________________________________________________________
Systemd Inhibitor Locks Deep Dive
Author : zdw
Score : 25 points
Date : 2021-04-09 15:39 UTC (1 days ago)
(HTM) web link (trstringer.com)
(TXT) w3m dump (trstringer.com)
| Spivak wrote:
| I appreciate any article that approaches systemd as an API server
| that consumes dbus. I wish this was more common because I think
| the design is fantastic and should be emulated all over Linux
| userspace. So many services are spinning up random http, grpc
| servers or littering the filesystem with Unix sockets when dbus
| is so dang powerful.
| wrkronmiller wrote:
| What is the advantage of dbus over Unix sockets?
| yrro wrote:
| What's the advantage of REST when you have TCP sockets?
| taway098123 wrote:
| Dbus is mostly just a message queue for Unix sockets. Think
| Kafka or SQS but only for local services.
| nottorp wrote:
| > So many services are spinning up random http, grpc servers or
| littering the filesystem with Unix sockets when dbus is so dang
| powerful.
|
| Or to rephrase, so many services are not depending on dbus :)
|
| You can't win.
| CameronNemo wrote:
| Seriously if you do not need dbus, don't bother learning it.
| You will only have it in specific situations and most people
| don't know it as well as grpc or REST.
| nottorp wrote:
| So how do you cancel an inhibitor lock held by a stuck process?
| CameronNemo wrote:
| reboot(RB_POWER_OFF)
|
| https://man.voidlinux.org/man2/reboot.2
| taway098123 wrote:
| You just kill the process, which causes the file descriptor to
| close. Cancelling the inhibitor lock by other means wouldn't do
| much, there's no way to get out of that situation without
| forcibly shutting the process down or disrupting its state.
___________________________________________________________________
(page generated 2021-04-10 23:00 UTC)