구차니의 잡동사니 모음

ajxplorer를 쓰다보면 대충 30분 정도 지나면 자동으로 로그아웃 되는데..
솔찍히 이정도 시간이면 내부망이어도 1기가 겨우 올리는 정도라 대략 좌절을 하게 된다.
(올리다가 세션 종료되면 파일 올리던거 무효됨)

ajaxplorer의 conf.php에서
AJXP_CLIENT_TIMEOUT_TIME을 0으로 적어주거나

php.ini 에서
session.gc_maxlifetime 을 늘려주거나 하는 식으로 변경하면 될 듯
  

ajaxplorer/server/conf/conf.php 268 /***********************************************/ 269 /* CLIENT SESSION OPTIONS 270 /*********************************************/ 271 // The length of the client session in SECONDS. By default, it's copying 272 // the server session length. In most PHP installation, it will be 1440, ie 24minutes. 273 // You can set this value to 0, this will make the client session "infinite" by 274 // pinging the server at regular occasions (thus keeping the PHP session alive). 275 // This is not a recommanded setting for evident security reasons. 276 //define("AJXP_CLIENT_TIMEOUT_TIME", intval(ini_get("session.gc_maxlifetime"))); 277 define("AJXP_CLIENT_TIMEOUT_TIME", intval(ini_get("session.gc_maxlifetime"))); 278 // The number of MINUTES before the session expiration 279 // where the client issues a warning. 280 define("AJXP_CLIENT_TIMEOUT_WARN_BEFORE", 3);

/etc/php5/apache2/php.ini 1500 ; After this number of seconds, stored data will be seen as 'garbage' and 1501 ; cleaned up by the garbage collection process. 1502 ; http://php.net/session.gc-maxlifetime 1503 session.gc_maxlifetime = 1440 1504 1505 ; NOTE: If you are using the subdirectory option for storing session files 1506 ;       (see session.save_path above), then garbage collection does *not* 1507 ;       happen automatically.  You will need to do your own garbage 1508 ;       collection through a shell script, cron entry, or some other method. 1509 ;       For example, the following script would is the equivalent of 1510 ;       setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes): 1511 ;          cd /path/to/sessions; find -cmin +24 | xargs rm 1512 1513 ; PHP 4.2 and less have an undocumented feature/bug that allows you to 1514 ; to initialize a session variable in the global scope, even when register_globals 1515 ; is disabled.  PHP 4.3 and later will warn you, if this feature is used. 1516 ; You can disable the feature and the warning separately. At this time, 1517 ; the warning is only displayed, if bug_compat_42 is enabled. This feature 1518 ; introduces some serious security problems if not handled correctly. It's 1519 ; recommended that you do not use this feature on production servers. But you 1520 ; should enable this on development servers and enable the warning as well. If you 1521 ; do not enable the feature on development servers, you won't be warned when it's 1522 ; used and debugging errors caused by this can be difficult to track down. 1523 ; Default Value: On 1524 ; Development Value: On 1525 ; Production Value: Off 1526 ; http://php.net/session.bug-compat-42

[링크 : http://www.lge.co.kr//brand/nethard/support/NethardQnaDetailCmd.laf?brand=NETHARD]