On Sat, 7 Apr 2012 11:38:40 +0100 Neil Bothwick <n...@digimed.co.uk> wrote:
> On Sat, 7 Apr 2012 02:47:41 -0600, Carlos Sura wrote: > > > > The problem is that it is trying to write to /var/lock, which is > > > on / at this point, rather than /run/lock, which is on a > > > writeable tmpfs. > > > I got this error, and saw a bugfile on Gentoo, just downgrade to > > your previous working version and you will get it working again. > > That bug report also showed the correct solution. There's no need to > downgrade, just change the locking_dir location from /var/lock > to /run/lock. Not only is this simpler and faster, it means another > update can't cause the same problem. > > So this makes the how many'eth time you've posted this exact same information to the list this week? -- Alan McKinnnon alan.mckin...@gmail.com
