From: Damien O'R. <da...@en...> - 2011-09-30 23:05:34
|
Steve, thanks for looking into it. I guess it was the 'here's an option ... but it doesn't work straight up' and 'here's another option but it has drawbacks' ... nothing complicated. Just thought it curious given that the situation (the restricted ports) has been like that for a long time ... whether right or wrong ... and it comes across as having to implement hacks around it. Anyway no big deal ... Thanks Damien On 01/10/2011, at 3:49 AM, Steve Vinoski wrote: > On Fri, Sep 30, 2011 at 1:43 AM, Damien O'Rourke <da...@en...> wrote: >> One other part that I've either mis-interpreted or is not quite clear .... >> trying to run version 1.90 on ports 80 and 443 ... the PDF (May 24, 2011) >> mentions adding the username to the config file but this kills startup with >> 'username' as an unknown token. And the on-site doc talks about other work >> arounds. > > Yes, there does seem to be a problem related to "username" -- thanks > for bringing it to our attention. Not sure yet if it's a code problem > or a doc problem, but either way I'll fix it. > >> So does that mean on Linux there's no simple 'run as this user after start' >> as per other web servers? Just the (not entirely convincing) workarounds >> listed in the web doc? > > Well, I don't think the use of authbind as shown on this page: > > http://yaws.hyber.org/privbind.yaws > > is very difficult -- seems pretty simple to me. What part of it is > complicated, or unconvincing? > > thanks, > --steve |