RE: [PHP] Making a Session Longer
> > RCVD_IN_OSIRUSOFT_COM (0.6 points) RBL: Received via a > relay in relays.osirusoft.com > >[RBL check: found > 4.131.92.216.relays.osirusoft.com.] > > X_OSIRU_OPEN_RELAY (2.9 points) RBL: DNSBL: sender is > Confirmed Open Relay > > You might want to check your email server. Its listed as an > open relay > and your messages are getting logged as spam :( You might want to fix your Spamassassin configuration to reflect that fact that relays.osirusoft.com has been taken out of action and is no longer valid, and that to encourage people to make the fix, the failure mode is that every IP address returns a positive. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Making a Session Longer
Free Grafton wrote: This mail is probably spam. The original message has been attached along with this report, so you can recognize or block similar unwanted mail in future. See http://spamassassin.org/tag/ for more details. Content preview: We offer an application for our customers which allows them to log into their organization and participate in discussions, register for events and build their websites. We are using Apache 2.0.47, PHP 4.3.3 and MySQL 4.0.15 for the application. We use session cookies with PHP to establish their permissions and store other information about them while they are logged in. [...] Content analysis details: (5.30 points, 5 required) ADDR_FREE (1.6 points) From Address contains FREE MIME_LONG_LINE_QP (0.2 points) RAW: Quoted-printable line longer than 76 characters RCVD_IN_OSIRUSOFT_COM (0.6 points) RBL: Received via a relay in relays.osirusoft.com [RBL check: found 4.131.92.216.relays.osirusoft.com.] X_OSIRU_OPEN_RELAY (2.9 points) RBL: DNSBL: sender is Confirmed Open Relay USER_AGENT (0.0 points) Has a User-Agent header [ snip ] You might want to check your email server. Its listed as an open relay and your messages are getting logged as spam :( -- Burhan Khalid phplist[at]meidomus[dot]com http://www.meidomus.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Making a Session Longer
Free, I am assuming you are using PHP sessions. If you are storing sessions using the your own save handler routines (this is quite common when saving session in the MySQL database), you have the ability to establish your own session timeout and "Garbage Cleanup" routines. This means you can cause the session timeout for your application to be different from other applications on the same server, provided you are storing your sessions in a different place than other applications (your own session table or directory). see session_set_save_handler(); in the manual Not sure about the shortening time limits, perhaps the current garbage cleanup routine has a bug. This is easy to do if your session table is in MySQL, since the database "timestamp" data type is not the same as a "date/time" data type. The date/time is returned as a string formatted "-mm-dd hh:mm:ss" and the time stamp is returned as a string "mmddhhmmss". I would look for a bug in the session_read or the session_gc routines. You know it just occurred to me, that if you are using files in the /tmp directory for storing sessions, all you need is one application with a bad "Garbage Collection" routine on this same server and using the /tmp directory, to affect all applications with just the symptoms you are seeing. good luck, Warren Vail -Original Message- From: Free Grafton [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2003 12:14 PM To: [EMAIL PROTECTED] Subject: [PHP] Making a Session Longer We offer an application for our customers which allows them to log into their organization and participate in discussions, register for events and build their websites. We are using Apache 2.0.47, PHP 4.3.3 and MySQL 4.0.15 for the application. We use session cookies with PHP to establish their permissions and store other information about them while they are logged in. The problem we are experiencing is that we are starting to have so many users on at one time that they are getting bumped off faster and faster. We have increased the MaxUsers in apache up to 1000, but that doesn¹t seem to make any difference. Our session_cookie is set to 0 in the php.ini file so there is no inherent timeout for users. We have 1.5GB of memory on our production server and aren¹t experiencing any memory swaps, so I don¹t think that is it as well. The only other possible thing I can think is that it might be related to session.gc_maxlifetime =1440 in the php.ini file. I have looked and can¹t really find much valuable information on what this really does and if it would have any affect on our sites. So, if anyone has some advise on what we can try, it sure would be greatly appreciated. Have an excellent day! Free Grafton -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Making a Session Longer
From: "Free Grafton" <[EMAIL PROTECTED]> > The problem we are experiencing is that we are starting to have so many > users on at one time that they are getting bumped off faster and faster. We > have increased the MaxUsers in apache up to 1000, but that doesn¹t seem to > make any difference. Our session_cookie is set to 0 in the php.ini file so > there is no inherent timeout for users. We have 1.5GB of memory on our > production server and aren¹t experiencing any memory swaps, so I don¹t think > that is it as well. What do you mean by "bumped off"? Is their session data disappearing? Maybe you have so many concurrent users that the "unique" session id isn't unique anymore and people are being given the same ID, overwriting the data? If you're referring to session.cookie_lifetime being set to zero, that means it only exists until the browser is closed, then the cookie is deleted. > The only other possible thing I can think is that it might be related to > session.gc_maxlifetime =1440 in the php.ini file. I have looked and can¹t > really find much valuable information on what this really does and if it > would have any affect on our sites. I don't think this would be causing the trouble. This setting controls the cleanup of old session files in your temp directory. When the garbage collection is triggered, if the session file has not been accessed for over 1440 seconds, it's deleted. If someone still has a cookie matching this session, then when they return to the site, a new (empty) file will be created. ---John Holmes... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
