ofonod(8) [debian man page]

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

NAME

       ofonod - oFono mobile telephony daemon

SYNOPSIS

       ofonod [options]

DESCRIPTION

       ofonod is a daemon which provides an oFono stack for interfacing mobile telephony devices.  oFono is controlled through D-Bus; for example,
       one can tell ofonod to send AT commands over /dev/rfcomm0  by  calling  the  D-Bus  method  org.ofono.at.Manager.Create.   /etc/dbus-1/sys-
       tem.d/ofono.conf is used to manage D-Bus permissions for oFono.

OPTIONS

       --debug, -d
	      Enable  debug information output. Note multiple arguments to -d can be specified, colon, comma or space separated. The arguments are
	      relative source code filenames for which debugging output should be enabled; output shell-style globs  are  accepted  (e.g.:  "plug-
	      ins/*:src/main.c").

       --nodetach, -n
	      Don't run as daemon in background.

       SEE ALSO

       dbus-send(1)

FILES

       /etc/dbus-1/system.d/ofono.conf

AUTHOR

       This man page was written by Andres Salomon <dilinger@collabora.co.uk>.

								     Jul 2009								 ofonod(8)

dbus-cleanup-sockets(1) 				      General Commands Manual					   dbus-cleanup-sockets(1)

NAME

       dbus-cleanup-sockets - clean up leftover sockets in a directory

SYNOPSIS

       dbus-cleanup-sockets [DIRECTORY]

DESCRIPTION

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

       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'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"

AUTHOR

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

BUGS

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

															   dbus-cleanup-sockets(1)