summaryrefslogtreecommitdiff
path: root/doc/dbus-cleanup-sockets.1
blob: a062d498f6b281a5d6f1609f6b2a3ed58901f38c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
.\" 
.\" dbus\-cleanup\-sockets manual page.
.\" Copyright (C) 2003 Red Hat, Inc.
.\"
.TH dbus\-cleanup\-sockets 1
.SH NAME
dbus\-cleanup\-sockets \- clean up leftover sockets in a directory
.SH SYNOPSIS
.PP
.B dbus\-cleanup\-sockets [DIRECTORY]

.SH DESCRIPTION

The \fIdbus\-cleanup\-sockets\fP command cleans up unused D\-Bus
connection sockets. See http://www.freedesktop.org/software/dbus/ for
more information about the big picture.

.PP
If given no arguments, \fIdbus\-cleanup\-sockets\fP cleans up sockets 
in the standard default socket directory for the
per\-user\-login\-session message bus; this is usually /tmp. 
Optionally, you can pass a different directory on the command line.

.PP
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. 

.PP
On most other flavors of UNIX, it's 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 mop up any leaked sockets.
Or you can just ignore the leaked sockets, they aren't really hurting
anything, other than cluttering the output of "ls /tmp"

.SH AUTHOR
dbus\-cleanup\-sockets was adapted by Havoc Pennington from
linc\-cleanup\-sockets written by Michael Meeks.

.SH BUGS
Please send bug reports to the D\-Bus mailing list or bug tracker,
see http://www.freedesktop.org/software/dbus/