oddjobd(8)
π 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 tostderr. Implies-n. Basically: she will tell you everything that's going on. Oversharing era. π-ppidfile β 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. π-ttimeout β Specifies the amount of time which will pass between attempts to reconnect to the bus ifoddjobdis disconnected for any reason. And here's the detail nobody reads: if the specified timeout is above 5, thenoddjobdwill 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. πβ¨
π¦ where this page comes from
- centos-stream 10: oddjob 0.34.7-14.el10 Β· BSD-3-Clause
- centos-stream 9: oddjob 0.34.7-7.el9 Β· BSD
- debian bookworm: oddjob 0.34.7-1+b2 Β· BSD-3-Clause
- debian trixie: oddjob 0.34.7-2.1 Β· BSD-3-Clause
- fedora 43: oddjob 0.34.7-17.fc43 Β· BSD-3-Clause
- fedora 44: oddjob 0.34.7-18.fc44 Β· BSD-3-Clause
- opensuse-leap 16.0: oddjob 0.34.7-bp160.1.13 Β· BSD-3-Clause
- opensuse-leap 16.0: oddjob 0.34.7-bp160.1.13 Β· BSD-3-Clause
- opensuse-leap 16.0: oddjob 0.34.7-bp160.1.13 Β· BSD-3-Clause
- opensuse-leap 16.0: oddjob 0.34.7-bp160.1.13 Β· BSD-3-Clause
- ubuntu jammy: oddjob 0.34.6-1 Β· BSD-3-Clause
- ubuntu noble: oddjob 0.34.7-2 Β· BSD-3-Clause
- ubuntu questing: oddjob 0.34.7-2.1build1
- ubuntu resolute: oddjob 0.34.7-2.1build2 Β· BSD-3-Clause
- ubuntu stonking: oddjob 0.34.7-2.1build2 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms