oddjobd(8)

πŸ“¦
version 0.34.7 Β· 3 versions
  • 0.34.7 Β· centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 0.34.7 Β· nixos 26.05
  • 0.34.7 Β· nixpkgs unstable
, in centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– oddjobd(8) πŸ’–

okay bestie, sit DOWN, because this one is literally the girlboss of the system β€” meet oddjobd, the privileged operations for unprivileged processes daemon. Yes she does the scary root stuff so your regular little user account doesn't have to. Iconic behavior. πŸ‘‘


✨ SYNOPSIS ✨

oddjobd [-n] [-d] [-p pidfile] [-c configfile] [-S] [-t timeout]

that's it. that's the whole vibe. six little flags and a whole lotta power. πŸ’…


🌸 DESCRIPTION 🌸

Okay so here's the tea: the oddjobd daemon is the one who serves up the com.redhat.oddjob service on the system-wide message bus. Every single facility she provides? She provides it as its own separate D-Bus method. No bundling, no sneaky two-for-ones, just clean little methods. ✨

Any method can be invoked by name by any user β€” but bestie, hear me when I say subject to access controls, and those are enforced by both D-Bus and oddjobd herself. Two bouncers at the door. You are not sneaking in. 🚫

Most methods are implemented as helper programs. So the daemon is lowkey the manager and the helpers are the ones actually doing the shift. 🫢


πŸŽ€ OPTIONS πŸŽ€

  • -n β€” Do not fork and become a daemon process. She stays right where you can see her. No ghosting into the background. πŸ‘€
  • -d β€” Print debugging messages to stderr. Implies -n. Basically: she will tell you everything that's going on. Oversharing era. 😭
  • -p pidfile β€” Store the daemon's process ID in the named file. So you can always find her later. πŸ’–
  • -c /etc/oddjobd.conf β€” Read the daemon's configuration from the named file. Default is right there in the flag, bestie. πŸŽ€
  • -S β€” Connect to the session bus instead of the system bus. Used for testing only. Do NOT ship this. I'm serious. πŸ™ˆ
  • -t timeout β€” Specifies the amount of time which will pass between attempts to reconnect to the bus if oddjobd is disconnected for any reason. And here's the detail nobody reads: if the specified timeout is above 5, then oddjobd will first attempt to connect up to 10 times at intervals of 5 seconds. The default reconnect timeout is 30 seconds. So she's patient, but she's not that patient. ⏰

πŸ¦‹ SIGNALS πŸ¦‹

  • SIGHUP β€” Reload the configuration. But listen: client requests which are in the process of being served will run to completion even if the newly-loaded configuration does not include the service, object, interface, or method. So if you were mid-request when she reloaded, you're finishing that request. She's not gonna cut you off mid-sentence. main character respect. ✨

🌈 SEE ALSO 🌈

go read those too, bestie, iykyk πŸ“š


and that's the whole page, fr fr πŸ’œ this lil guide came straight from the oddjob Manual, dated 5 April 2006 β€” yes she's vintage, and yes she still ate. πŸŽ€βœ¨