On Fri, Jun 4, 2010 at 8:58 AM, Rich Shepard <[email protected]> wrote: > I just upgraded to the Ledger123-2.6.30 version and cannot log in: access > denied. I'm not sure what permission changed. > > First, I untarred the downloaded tarball and retarred it using a directory > called 'sql-ledger' so it would untar into /usr/local/sql-ledger. Second, I > untarred it there and checked that all directories have 755 permissions. > They do. > > It's been quite a long time since a version upgrade here changed the perms > so I lose access. What do I change (and to what perms) to get it working > again?
The owner/group of your SQL-Ledger directory needs to be the same as that of the Apache (or whatever webserver you are using) process, except for the parent one that runs as superuser (root). For example: # ps -ef | egrep httpd root 2275 1 0 2009 ? 00:01:02 /usr/sbin/httpd apache 31628 2275 0 04:02 ? 00:00:00 /usr/sbin/httpd apache 31629 2275 0 04:02 ? 00:00:00 /usr/sbin/httpd apache 31630 2275 0 04:02 ? 00:00:00 /usr/sbin/httpd So, in my case, the "apache" user is the one running the webserver, & my webserver's document directory is /var/www, so I expect the "apache" user to own it: # ls -ld /var/www drwxr-xr-x 9 apache apache 4096 Dec 1 2009 /var/www It does, as expected. Hope this helps. -- Best Regards, Wallace _______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
