Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dbus-cleanup-sockets(1) [opensolaris man page]

dbus-cleanup-sockets(1) 					   User Commands					   dbus-cleanup-sockets(1)

NAME
dbus-cleanup-sockets - clean up leftover sockets in a directory SYNOPSIS
dbus-cleanup-sockets [--help] [--version] [directory] DESCRIPTION
The dbus-cleanup-sockets command cleans up unused D-Bus connection sockets. If given no arguments, dbus-cleanup-sockets cleans up sockets in the standard default socket directory for the per-user-login-session mes- sage bus; this is usually /tmp. Optionally, you can pass a different directory on the command line. On Linux, this program is essentially useless, because D-Bus defaults to using "abstract sockets" that exist only in memory and don't have a corresponding file in /tmp. On most other flavors of UNIX, it is possible for the socket files to leak when programs using D-Bus exit abnormally or without closing their D-Bus connections. Thus, it might be interesting to run dbus-cleanup-sockets in a cron job to clean up any leaked sockets. Or you can just ignore the leaked sockets, they are not really hurting anything, other than cluttering the /tmp directory. See http://www.freedesktop.org/software/dbus/ for more information. OPTIONS
The following options are supported: --help Show help information on standard output and exit. --version Print the version of dbus-cleanup-sockets OPERANDS
The following operands are supported: directory Clean up sockets in the specified directory rather than the default socket directory. EXIT STATUS
The following exit values are returned: 0 Application exited successfully >0 Application exited with failure FILES
The following files are used by this application: /usr/bin/dbus-cleanup-sockets Executable for dbus-cleanup-sockets /tmp Default location for D-Bus connection sockets ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWdbus | +-----------------------------+-----------------------------+ |Interface stability |Volatile | +-----------------------------+-----------------------------+ SEE ALSO
dbus-daemon(1), dbus-launch(1), dbus-monitor(1), dbus-send(1), dbus-uuidgen(1), libdbus-glib-1(3), attributes(5) NOTES
For authorship information refer to http://www.freedesktop.org/software/dbus/doc/AUTHORS. Updated by Brian Cameron, Sun Microsystems Inc., 2007. dbus-cleanup-sockets was adapted by Havoc Pennington from linc-cleanup-sockets written by Michael Meeks. Documentation updated by Brian Cameron, Sun Microsystems Inc., 2007. Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/ SunOS 5.11 19 Nov 2007 dbus-cleanup-sockets(1)

Check Out this Related Man Page

dbus-uuidgen(1) 					      General Commands Manual						   dbus-uuidgen(1)

NAME
dbus-uuidgen - Utility to generate UUIDs SYNOPSIS
dbus-uuidgen [--version] [--ensure[=FILENAME]] [--get[=FILENAME]] DESCRIPTION
The dbus-uuidgen command generates or reads a universally unique ID. Note that the D-Bus UUID has no relationship to RFC 4122 and does not generate UUIDs compatible with that spec. Many systems have a sepa- rate command for that (often called "uuidgen"). See http://www.freedesktop.org/software/dbus/ for more information about D-Bus. The primary usage of dbus-uuidgen is to run in the post-install script of a D-Bus package like this: dbus-uuidgen --ensure This will ensure that /var/lib/dbus/machine-id exists and has the uuid in it. It won't overwrite an existing uuid, since this id should remain fixed for a single machine until the next reboot at least. The important properties of the machine UUID are that 1) it remains unchanged until the next reboot and 2) it is different for any two run- ning instances of the OS kernel. That is, if two processes see the same UUID, they should also see the same shared memory, UNIX domain sockets, local X displays, localhost.localdomain resolution, process IDs, and so forth. If you run dbus-uuidgen with no options it just prints a new uuid made up out of thin air. If you run it with --get, it prints the machine UUID by default, or the UUID in the specified file if you specify a file. If you try to change an existing machine-id on a running system, it will probably result in bad things happening. Don't try to change this file. Also, don't make it the same on two different systems; it needs to be different anytime there are two different kernels running. The UUID should be different on two different virtual machines, because there are two different kernels. OPTIONS
The following options are supported: --get[=FILENAME] If a filename is not given, defaults to localstatedir/lib/dbus/machine-id (localstatedir is usually /var). If this file exists and is valid, the uuid in the file is printed on stdout. Otherwise, the command exits with a nonzero status. --ensure[=FILENAME] If a filename is not given, defaults to localstatedir/lib/dbus/machine-id (localstatedir is usually /var). If this file exists then it will be validated, and a failure code returned if it contains the wrong thing. If the file does not exist, it will be created with a new uuid in it. On success, prints no output. --version Print the version of dbus-uuidgen AUTHOR
See http://www.freedesktop.org/software/dbus/doc/AUTHORS BUGS
Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/ dbus-uuidgen(1)
Man Page