These to are set in configure so that they end up in
LocalSite.cfg
as
$TWiki::cfg{SessionExpiresAfter} = '16400';
$TWiki::cfg{SessionDir} = '/tmp/ramdisk';
However, these hashes are not recognized in any module.
In
TWiki.pm
, however, there are:
$cfg{UseClientSessions} = 1;
$cfg{Sessions}{IDsInURLs} = 0;
$cfg{Sessions}{UseIPMatching} = 1;
$cfg{Sessions}{MapIP2SID} = 0;
$cfg{Sessions}{Dir} = '/tmp';
$cfg{Sessions}{ExpireAfter} = '21600';
Obviously this didn't show up when both
$TWiki::cfg{SessionDir}
and
$TWiki::cfg{Session}{Dir}
were set to
/tmp
but as soom as I tried setting up a ramdisk to see if speeding up that storage would help I uncovered this.
If I put the
$cfg{Sessions}{Dir}
in
LocalSite.cfg
manually and then run
bin/configure
all the other things that should have
{Session}
now do.
How this came about may be of interest.
To do performance comparisons, I took a copy of a July version of Dakar that is live in the field, tarballed it up and untarred it twice on my test platform. It has some topics with complex searches and applications so is a suitable piece of heavy exercise.
One copy I overwrote with the new code and templates, but had the old
LocalSite.cfg
. The old
LocalSite.cfg
had the
$cfg{SessionDir}
format, and even after running
bin/configure
it didn't pick up the new style entries. As I said, I had to put them in manually and remove the old ones. The order of parsing may have something to do with it. Yes, this is a very unusual bug, unlikely to occur in any reasonable situation, so I'm depreciating it and just leaving it for the record. If I fgind any evidence it is due to some instability I will re-open it.
--
AJA