> I found a pretty useful article at > http://www.linuxjournal.com/article.php?sid=4143 on how to use > Apache::Session with Mason.
I'm afraid that is not a very good article. It's out of date, and shows poor error handling. If you want to use sessions with Mason, you should be using the session handler that Mason provides. That is available on CPAN and is supported on the Mason list. Apache::Session::DBI (which is what the article refers to) is ancient and should not be used. > Permission denied at > /Library/Perl/Apache/Session/SysVSemaphoreLocker.pm line 46. > > Which seems to indicate it isn't. I STFW, and found several people who > seem to have had the same problem I have, but the solutions proffered > involve ipcs and ipcrm, which don't exist on my Mac OS X 10.2.6 system. You shouldn't use the IPC locking in Apache::Session. You didn't mention which database you're using, but most of them have alternative ways of doing locking. In my opinion, the locking approach taken in Apache::Session is not a good one for the average web site and you should simply turn it off by using the NullLocker. > Suggestions are more than welcome; I'm not quite sure how > Session::SysVSempaphoreLocker got involved in the first place, since I > don't explicitly reference it. Apache::Session::DBI uses it for locking. - Perrin
