Marcus Ramberg <[EMAIL PROTECTED]> wrote on 08/28/2008 02:05:44 PM: > > On 13. aug.. 2008, at 13.40, Dermot wrote: > > > > Thanx Carl and Sorry Matthias, I didn't follow you exactly because > > > > su apache > > This account is currently not available
look at your apache users' passwd entry, you will see a shell for /sbin/nologin (which produces that error), if you pass a valid shell to su you can use it to run commands as apache... #su -s /bin/sh -c "whoami" apache apache > > > > and > > > > su -m apache > > bash: /root/.bashrc: Permission denied > > > > So I have chown apache:apache MyApp directory and it works. > > > > Is it okay to leave the top level directory and the datafile owned by > > the httpd user? I would have thought all the other code should be > > read-only for other that user. > > SQLite requires write access on the directory the data file is in as > well as the data file to be able to provide locking. leaving the app > writeable by the httpd user isn't really recommended. I suggest moving > your sqlite database to a db directory or something similar. > > Marcus > > _______________________________________________ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/