[hunchentoot-devel] less-than-helpful error message

[Cyrus Harmon]

I have no idea if this is the right thing to do for lispworks or not, but this seems to work on SBCL.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: hunchentoot-recursive-lock.patch
Type: application/octet-stream
Size: 1060 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/tbnl-devel/attachments/20100622/b34c4d73/attachment.obj>
-------------- next part --------------


Thanks,

Cyrus

On Jun 15, 2010, at 9:39 PM, Hans H?bner wrote:

> On Wed, Jun 16, 2010 at 01:49, Cyrus Harmon <ch-tbnl at bobobeach.com> wrote:
>> So, while trying to track down an unrelated issue where my handlers aren't getting called anymore, I came across the following issue where failure to open the message log file results in an error, which, in turn, attempts to open the message log file. The problem in this case was that the permissions were bogus for the directory I was trying to open. But, still, we should probably have a nicer error message than "recursive lock attempt" here.
> 
> I agree.  Can you supply a patch that corrects the problem?  Using a
> recursive lock would probably the easiest solution.
> 
> Thanks,
> Hans
> 
> _______________________________________________
> tbnl-devel site list
> tbnl-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/tbnl-devel