Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #413
Difficulty: Medium
The AT&T 3B1, also known as the PC7300 or UNIX PC, was a desktop workstation computer based on the Motorola MC68010 microprocessor, running an operating system from Convergent Technology (based on Unix System V Release 2).
True or False?
Linux & Unix Commands - Search Man Pages

oddjobd(8) [centos man page]

oddjobd(8)						      System Manager's Manual							oddjobd(8)

oddjobd - privileged operations for unprivileged processes SYNOPSIS
oddjobd [-n] [-d] [-p pidfile] [-c configfile] [-S] [-t timeout] DESCRIPTION
The oddjobd daemon provides the com.redhat.oddjob service on the system-wide message bus. Each facility which oddjobd provides is provided as a separate D-Bus method. Any method can be invoked by name by any user, subject to access controls enforced by both D-Bus and oddjobd. Most methods are implemented as helper programs. OPTIONS
-n Do not fork and become a daemon process. -d Print debugging messages to stderr. Implies -n. -p pidfile Store the daemon's process ID in the named file. -c /etc/oddjobd.conf Read the daemon's configuration from the named file. -S Connect to the session bus instead of the system bus. Used for testing only. -t timeout Specifies the amount of time which will pass between attempts to reconnect to the bus if oddjobd is disconnected for any reason. 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. SIGNALS
SIGHUP Reload the configuration. 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. SEE ALSO
oddjob_request(1) oddjob.conf(5) oddjobd.conf(5) oddjob Manual 5 April 2006 oddjobd(8)

Check Out this Related Man Page

oddjobd.conf(5) 						File Formats Manual						   oddjobd.conf(5)

oddjobd.conf - configuration for oddjobd DESCRIPTION
The /etc/oddjobd.conf configuration file specifies which services the oddjobd server provides over the D-Bus, and authorization rules which are enforced in addition to those enforced by the system message bus. The configuration file is an XML document. The top-level element type is <oddjobconfig>, which contains one or more <service> elements. Each <service> describes a service which will be provided on the system-wide message bus. Each <object> describes an object path which will will be recognized by the specified service. The object path may include wildcards, in which case any call to an object with a path name which matches the specified path will be accepted. An object contains one or more <interface> elements, each of which describes a group of methods described in <method> elements. Each <method> element must specify the method name as a value for its name attribute and may include a <helper> element which the name of an executable to run as its exec attribute and the number of arguments which will be passed to the helper as its argument attribute. A <helper> may also include attributes indicating whether or not the invoking user's name should be prepended to that argument list, and whether that argument list should be passed in to the helper via stdin (the default) or on its command line. Each <oddjobconfig>, <service>, <object>, <interface>, or <method> element may also include authorization elements <allow> and <deny>. Each <allow> or <deny> rule specifies some combination of a user name and/or a UID range which the invoking user must match for the rule to apply. A rule can also specify the caller's SELinux context, user, role, or execution domain, and be applied or not based on whether or not policy is being enforced. All <deny> rules for the method are checked first, followed by all of its <allow> rules. If no matches are found, the <deny> rules for the containing <interface> element are checked, followed by its <allow> rules, and so on. If all ACLs are searched and no matches turn up, access is denied. The oddjobd server will automatically supply information used by the D-Bus introspection mechanism on behalf of your objects, but only if the client which is requesting the information is allowed to invoke the Introspect method of the org.freedesktop.DBus.Introspectable inter- face provided by the object. The configuration file may also indicate that the contents of other files should be read by the configuration parser, using an <include> element. EXAMPLES
Here is an example file: <?xml version="1.0"?> <oddjobconfig/> Another: <?xml version="1.0"?> <oddjobconfig> <allow user="wally"/> <service name="com.redhat.oddjob"> <allow user="polly"/> <object name="/com/redhat/oddjob"> <allow user="holly"/> <interface name="com.redhat.oddjob"> <allow user="bob"/> <method name="pwd"> <helper exec="/bin/pwd" argument_count="0" prepend_user_name="no"/> <allow user="jimmy"/> <allow user="billy"/> <allow min_uid="0" max_uid="1000"/> </method> <method name="reboot"> <helper exec="/sbin/reboot" argument_count="0"/> </method> </interface> <interface name="org.freedesktop.DBus.Introspectable"> <allow min_uid="0" max_uid="0"/> </interface> </object> </service> <include ignore_missing="yes">/etc/oddjobd-local.conf</include> <include ignore_missing="yes">/etc/oddjobd.conf.d/*.conf</include> </oddjobconfig> And another: <?xml version="1.0"?> <oddjobconfig> <service name=""> <object name="/com/example/power"> <interface name="com.example.shutdown"> <method name="reboot"> <allow user="root"/> <helper exec="/sbin/reboot" argument_count="0"/> </method> </interface> <interface name="org.freedesktop.DBus.Introspectable"> <allow min_uid="0" max_uid="0"/> </interface> </object> <object name="/com/example/power"> <interface name="com.example.shutdown"> <method name="poweroff"> <allow user="root"/> <helper exec="/sbin/poweroff" argument_count="0"/> </method> </interface> <interface name="org.freedesktop.DBus.Introspectable"> <allow min_uid="0" max_uid="0"/> </interface> </object> </service> </oddjobconfig> SEE ALSO
oddjob_request(1) oddjob.conf(5) oddjobd(8) oddjob Manual 5 April 2006 oddjobd.conf(5)

Featured Tech Videos