Re: SESSION Not behaving II: permission denied(13)

On Sat, Oct 18, 2003 at 03:44:31PM +0300, Burhan Khalid wrote: > [-^-!-%- wrote: > >Yep. It's me again. 96 hours into the battle, and SESSIONS are still > >winning. > > > >I've written my login script and is now getting the following error. > >Please advise. > > > >Warning: open(/tmp/sess_a690c089dead297c95034d9fe243f860, O_RDWR) failed: > >Permission denied (13) in Unknown on line 0 > > > >Warning: Failed to write session data (files). Please verify that the > >current setting of session.save_path is correct (/tmp) in Unknown on line > >0 > > First thing, make sure /tmp exists. > If it does, make sure that the apache user has permissions to write to > it. You can modify its permissions so that the apache user and/or group > can write to /tmp; or you can chmod it to 777 (which could lead to other > security issues). > > This should get rid of your warnings. > > -- > Burhan Khalid > phplist[at]meidomus[dot]com > http://www.meidomus.com > The standard permissions for /tmp are 1777. This allows any user to write to tmp, but only the user who created a specific file (eg, the session file as apache) can delete the file. Further, sesssions are created with a very restrictive permission set, so that ony the apache user and root will be able to read the data. Bottom line: make sure that /tmp exists and that its permissions are 1777. (as root, chmod 1777 /tmp) -- Jim Kaufman mailto:jmk@linuxforbusiness.net Linux Evangelist cell: 612-481-9778 public key 0x6D802619 fax: 952-937-9832 http://www.linuxforbusiness.net