On 8/24/24 04:31, Stuart Henderson wrote:
On 2024/08/23 22:04, David Colburn wrote:
On 8/21/24 14:25, Stuart Henderson wrote:
On 2024/08/21 14:02, David Colburn wrote:
"$ cat /var/www/dev/null"

Returns to the prompt.

Here's this ...

b7# rcctl -d start lighttpd
doing _rc_parse_conf
lighttpd_flags empty, using default >-f /etc/lighttpd.conf<
doing rc_check
lighttpd
doing rc_start
doing _rc_wait_for_start
doing rc_check
2024-08-21 13:59:01:
(/usr/obj/ports/lighttpd-1.4.74-mysql/lighttpd-1.4.74/src/configfile.c.1840)
opening errorlog 'logs/error.log' failed: Permission denied
Well that is failing on writing /var/www/logs/error.log

I just checked and the permissions for

/var/www/logs/error.log

are 644 converted from "-rw-r--r--" (if I'm reading things correctly).

Is that correct?

Owner and Group are "www www" - is that correct?

That depends on what user you have got lighttpd running as.
If it's the default, _lighttpd, then that yser needs to be able
to write to the log file that lighttpd is configured to use.

Seems the port docs, or perhaps defaults, could do with some
tweaks as there are definitely some things which are not obvious
(/dev/null and not mounting nodev) and are a bit hard to figure
out unless you know OpenBSD. But you might want to pick a
different web server if you're needing help with file
permissions etc as there's a lot more documentation you can
find online for e.g. nginx or apache httpd than lighttpd.

I looked at all three and chose lighttpd for a variety of reasons that

I won't go into atm.

If you're saying that lighttpd isn't ready to deploy in OpenBSD then I guess

I'll have to look at one of the other two - which would be unfortunate.

If you're saying that with a few adjustments lighttpd can be made to work

with OpenBSD (as well as it does with Linux) then I'm fine with a learning curve.

Despite various quirks (and missing drivers) I've been primarily using Linux for

over 20 years - rather than Apple or MS.

(I also have Graphene on my Pixel phone vs google/alphabet's Android.)

Thanks.

Reply via email to