[elinks-users] elinks dies with weird message if ~/.elinks not writeable

Mikel Ward mward at aconex.com
Mon Oct 13 19:33:24 PDT 2008


In elinks 0.11 and 0.12, I get this error message on startup:
  ERROR at interlink.c:329: The call to connect() failed: 13 (Permission denied)

Which doesn't give me enough information to understand the cause.

Running it inside strace shows that it couldn't create a Unix domain
socket in ~/.elinks because that directory wasn't writeable by me.

The attached patch makes it print this instead:
  ERROR at interlink.c:343: connect() failed on /home/mward/.elinks/socket0: 13 (Permission denied)

I hope you can use it or implement something like it.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: elinks.socketerror.patch
Type: text/x-patch
Size: 2522 bytes
Desc: not available
URL: <http://lists.linuxfromscratch.org/pipermail/elinks-users/attachments/20081014/8ca8ede0/attachment.bin>

More information about the elinks-users mailing list