- Status Closed
- Percent Complete
- Task Type Feature Request
- Category Backend/Core
- Assigned To No-one
- Operating System All
- Severity Low
- Priority Very Low
- Reported Version 1.0-beta
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Flyspray - The bug killer!
Opened by Oliver Vogel - 25.11.2015
Last edited by peterdd - 02.12.2015
Opened by Oliver Vogel - 25.11.2015
Last edited by peterdd - 02.12.2015
FS#2092 - Notice: session_start(): ps_files_cleanup_dir: opendir(/tmp) failed
i know, this “bug” was reportet some time ago and you decide, not to fix it, because you sayed this is not a error.
But PLEASE THINK ABOUT Managed-Server or shared-hosting Environments.
If the Admin of this systems decided NOT to make it writeable there is no chance for you to change this.
Maybe you can add a config-value, where this directory could be. for example:
/hosting/custimers/12345/webs/12/tmp
it is no problem for me to make this path writeable (because this is INSIDE my web). But is is absolutely not possible for me to make /tmp
wirteable...
Closed by peterdd
02.12.2015 22:58
Reason for closing: Won't fix
Additional comments about closing:
02.12.2015 22:58
Reason for closing: Won't fix
Additional comments about closing:
server config problem, not a job for
flyspray.
Could you please reference the 'old' tasks in which it was discussed/decided?
So the current devs can review the arguments and decision.
No propblem
https://bugs.flyspray.org/task/1634
could you post output of phpinfo, at least session configuration section?
Or scan the output for '/tmp'.
Maybe similiar issue? :
http://stackoverflow.com/questions/2904862/issues-with-php-5-3-and-sessions-folder
At a first look it seems a problem of php(php.ini) configuration issue for the shared hosting customers.
i talked (phoned) with my ISP and you are right.
they told me (and i can see this with phpinfo();) that the session.save_path is set to /tmp and that this is NO PROBLEM in 99% of the scripts because they let php manage the session-files. In this case everything works fine.
BUT in 1% the script itself wants to manage the session-files and this crashes. i now created a new php.ini (my ISP alows meto do this) and changed the session.save_path to a path i can access.
now let's see what hapens tomorrow. do i have to remove the old session-files by my onw (cron) or does flyspray handle this for me?
i tell you!