Thanks for your fast answer!
> are you sure?
>
> that looks suspiciously like a permissions error on the directory
> /var/lib/php/session, NOT an ownership error on
> /var/lib/php/session/sess_12345.
> Are you sure your users are able to create files in this directory?
/var/lib/php/session is rw to all users (777 for testing).
If no session-files would be created at all, you'd be right, but when the error
occurs a session-file with the refered name already exists, created by an other
php-app executed earlier. The session-file has the same name, owned by the user
who "executed" the other php-app earlier. So it is a "File already
exists"-Problem, but as php cant open/read it, because of owner-missmatch and
no rights (rw for owner only) php acts like it could not create it.
> That's because it only matters who has read permission on a session file
> when php tries to instantiate that particular session id. Normally php
> sessions will create random id unless it is informed of a previously active
> session via the appropriate cookie or query string variable. Thus, running php
> under multiple accounts will also retain the randomness thereby preventing
> conflicts of id.
As even colleagues who tried it had the same issues from different PCs i guess
cookies are not the cause, but i will check that!
> google-foo: umask
I tried umask, but it didnt work. Can you give me some hints on that?
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
_______________________________________________
suPHP mailing list
[email protected]
https://lists.marsching.com/mailman/listinfo/suphp
