Wed, 24 Feb 2010 21:42:25 -0500 On Wed, 2010-02-24 at 18:41 +0100, Bruno Prémont wrote: > On Wed, 24 February 2010 "John A. Sullivan III" <jsullivan@opensourcedevel.com> wrote: > > > Hello, all. Has anyone gotten the Google Chrome browser to work in a > > VServer? No need to spend a lot of time on this. We are prepared to > > go do battle with it but, if someone else has solved it already, it > > would save us the time. It looks like its default configuration > > insists in writing to /dev/shm. Am I correct to assume that is a > > very bad idea in a vserver guest? Thanks - John > > > > [1538:1538:4716833642534:ERROR:/usr/local/google/b/slave/chrome-official-linux-64/build/src/base/shared memory posix.cc(192)] > > Creating shared memory in /dev/shm/com.google.chrome.xLMyJH failed: > > No such file or directory > > [1538:1538:4716833642580:ERROR:/usr/local/google/b/slave/chrome-official-linux-64/build/src/base/shared memory posix.cc(194)] > > This is frequently caused by incorrect permissions on /dev/shm. Try > > 'sudo chmod 777 /dev/shm' to fix. > > Would it help to symlink /dev/shm to somewhere under /tmp (assuming > /tmp is tmpfs)? Otherwise you could add a tmpfs for /dev/shm in fstab of > your vserver's configuration. > > Bruno Apparently there is a /dev/shm in my vserver guest. For kicks, I changed the group to a group in which the user was a member and granted write rights for the group to /dev/shm. Chrome works with this. However, are there any security issues with allowing vserver guests to write to their own /dev/shm? Thanks - John