Project

General

Profile

Actions
Copy link

Bug #394

closed

AF_UNIX: seemingly can't use relative path for server.bind

Added by Anonymous almost 19 years ago. Updated about 16 years ago.

Status:
Invalid
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

When I use this setting in my config file:


server.bind = "./lighttpd.socket"

I get this error when starting lighttpd:


2005-11-29 15:16:38: (network.c.223) gethostbyname failed:  3 ./lighttpd.socket

And when I use this setting in my config file:


server.bind = "lighttpd.socket"

I get this error when starting lighttpd:


2005-11-29 15:22:03: (network.c.265) can't bind to port 80 Can't assign requested address

In both cases, my expectation is that lighttpd would start normally, creating and binding to a socket in the current working directory named 'lighttpd.socket'.

I am running lighttpd 1.4.8 with the stock lighttpd.conf (except for the server.bind changes) under FreeBSD 4.11.

-- chad

Actions
Copy link
 #1

Updated by jan almost 19 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

In changeset r947 the option server.bind was documented.

For a unix-domain socket the pathname has to be absolute. Otherwise it is treated as hostname and is tried to be resolved.

This is considered as 'Not a Bug'.

Actions
Copy link
 #2

Updated by stbuehler about 16 years ago

  • Status changed from Fixed to Invalid
Actions
Copy link

Also available in: Atom