From: Ashley J G. <sql...@pu...> - 2007-01-24 03:43:43
|
Hi Rich, In the doc subdirectory you will find instructions for each version's upgrade. Essentially the bit you need to do is (do this from the root of your sl install, eg /usr/local/sql-ledger/): 2. fix permissions # chown -hR nobody:nogroup * # chmod 711 templates users css spool Note: replace nobody:nogroup with your web server user and group So if apache runs as "apache" then you do chown -hR apache:apache * Ultimately I think your problem is that the config file is owned by yourself, not apache, but you'll have other issues if you don't fix the whole lot by doing to two steps above (note that the first step sets ownership recursively, so will include your conf file etc). -- Regards, Ashley J Gittins web: http://www.purple.dropbear.id.au jabber: agi...@pu... On Wednesday 24 January 2007 08:43, Rich Shepard wrote: > On Tue, 23 Jan 2007, Rich Shepard wrote: > > That's what I tried. /usr/local/sql-ledger/users has permissions 777 > > (rwxrwxrwx). The files in that directory -- specifically rshepard.conf -- > > is owned by me and has 755 permissions (rwxr-xr-x). /usr/local/sql-ledger > > is owned by root.root with 755 permissions. > > I also forgot to write that immediately after upgrading sql-ledger from > -2.6.21 to -2.6.22 I logged in to ensure that the application upgrade > caused no problems. > > Rich |