Your message dated Sat, 02 Apr 2011 08:48:39 +0530
with message-id <1301714320.15766.30.camel@pi0307572>
and subject line Re: Bug#620450: gnome-keyring: Please create
$GNOME_KEYRING_CONTROL directory in /var/run rather than /tmp
has caused the Debian Bug report #620450,
regarding gnome-keyring: Please create $GNOME_KEYRING_CONTROL directory in
/var/run rather than /tmp
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
620450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620450
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-keyring
Version: 2.30.3-5
Severity: normal
gnome-keyring creates a temporary directory for its control socket in
/tmp. This temporary directory often doesn't get properly cleaned up,
resulting in the accumulation of directories in /tmp. (Right now I have
a pile of /tmp/keyring-* directories accumulated just in the past month
since I last removed all of them. Other systems I've used have many
screenfuls of these directories.)
This directory seems like a perfect fit for /var/run. Moving the
directory there should not affect any existing applications, since they
all reference it via $GNOME_KEYRING_CONTROL. Furthermore, this would
ensure that they get cleaned up at boot time, at a minimum (or
automatically disappear when using a tmpfs for /var/run).
- Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-keyring depends on:
ii dbus-x11 1.4.6-1 simple interprocess messaging syst
ii gconf2 2.28.1-6 GNOME configuration database syste
ii libc6 2.11.2-13 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.4.6-1 simple interprocess messaging syst
ii libgcr0 2.30.3-5 Library for Crypto UI related task
ii libgcrypt11 1.4.6-5 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.28.4-1 The GLib library of C routines
ii libgp11-0 2.30.3-5 Glib wrapper library for PKCS#11 -
ii libgtk2.0-0 2.24.3-1~sid1 The GTK+ graphical user interface
ii libtasn1-3 2.9-2 Manage ASN.1 structures (runtime)
Versions of packages gnome-keyring recommends:
ii libpam-gnome-keyring 2.30.3-5 PAM module to unlock the GNOME key
gnome-keyring suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Le vendredi 01 avril 2011 à 15:55 -0700, Josh Triplett a écrit :
> gnome-keyring creates a temporary directory for its control socket in
> /tmp. This temporary directory often doesn't get properly cleaned up,
> resulting in the accumulation of directories in /tmp. (Right now I have
> a pile of /tmp/keyring-* directories accumulated just in the past month
> since I last removed all of them. Other systems I've used have many
> screenfuls of these directories.)
>
> This directory seems like a perfect fit for /var/run.
No, it is a perfect fit for /tmp. /var/run is 0755, /tmp is 1777.
--
.''`.
: :' : “You would need to ask a lawyer if you don't know
`. `' that a handshake of course makes a valid contract.”
`- -- J???rg Schilling
--- End Message ---
