By default, dbus places a socket at /var/run/dbus/system_socket If this directory does not exist, then dbus fails to start. The dbus ebuild creates this directory, however, if the user has placed /var/run on a tmpfs, then this directory will not exist at startup, so dbus will fail to start at boot. A quick workaround is to test for the existance of the directory in the init.d script, then create it if necessary.
Created attachment 80573 [details, diff] patch to dbus init.d file
Quick work around is not to delete anything in /var/run and especially not deleting stuff that's got a .keepdir file in it.
1) Why is this resolved as WONTFIX? Its a super-simple fix and I already provided a patch? 2) I didn't delete anything. I simply had /var/run mounted on tmpfs, which is a standard practice given the purpose of the directory. So at boot time, the directory does not exist. 3) According to the FHS (http://www.pathname.com/fhs/2.2/fhs-5.13.html) "5.13 /var/run : Run-time variable data 5.13.1 Purpose This directory contains system information data describing the system since it was booted. Files under this directory must be cleared (removed or truncated as appropriate) at the beginning of the boot process." I know that Gentoo doesn't try for FHS compliance, but should ebuilds really be relying upon a persistant /var/run for their functionality? 4) I really don't appretiate the condescending tone of your response. Before you assume that all users are stupid and beneath you, why don't you think for one second that they could have a valid concern.
Before you scream at me, check the new initscript. Notice the commit time is well before your tirade.
Where in my comment do I "scream at you?" I simply state facts to counter your inexplicable resolving of the bug as WONTFIX and call you out on your mocking me in your reply. If I were screaming a tirade at you I WOULD TYPE LIKE THIS!!!!!
You know, you really are a jerk: Revision 1.2 - (view) (download) (annotate) - [select for diffs] Tue Mar 14 06:56:39 2006 UTC (18 hours, 48 minutes ago) by cardoe Branch: MAIN CVS Tags: HEAD Changes since 1.1: +4 -6 lines Diff to previous 1.1 Handle PEBCAK error (Portage version: 2.1_pre6-r2) Mounting /var/run on tmpfs is a standard practice. Ubuntu does it by default, as does Solaris and tons of other *nix-like systems. Mounting /var/run as tmpfs does not indicate a problem with a user, just that your shitty little script is broken. I can tell that you must be about 12 years old, because rather than say a quick "thanks" to a user for 1) filing a bug and 2) submitting a pathc to fix it, you feel the need to insult them, mark the bug as WONTFIX, then apply the patch anyway! And insult the patch submitter to boot! Maybe when you grow up, you won't be such an a$$hole.
Funny. I have Breezy here and it does not. I have Dapper on VMWare and it does not either. I've also checked Debian & Fedora and they don't have this either. I just downloaded the Ubuntu and Debian source debs and read through their initscripts and they do not create the directory. The directory is created by the installing deb package and assumed to be there always. In fact the same failure will result if you do this on Debian/Ubuntu. So much for the standard practice argument...
