|
From: Chris W. <ch...@cw...> - 2002-03-12 12:09:35
|
On Tue, 2002-03-12 at 14:39, Matt Olson wrote: > Okay... now I'm getting a bunch of "can't insert duplicate key" > type errors from the partial success of previous runs, that's > (I guess) acceptable. And I get a superuser username and a > random password. Not bad! Excellent! If you want a clean run (which is probably a good idea), then you can just drop the database, recreate it and run install_sql again. > Moral of this story: if you've (well, I've :-) just installed > something, and it isn't working, check file permissions. > Especially if the error is "can't locate" or "can't open". I've actually never had this problem. Not because I'm thorough or anything, I just figured the 'make install' process ensures that file permissions are at least 444 for everything a module needs. Maybe this is a umask issue. (I'm seeing umask issues around every corner now :-). Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |