From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: cgit@lists.zx2c4.com
Cc: gs-cgit-lists.zx2c4.com@gluelogic.com
Subject: Re: cgit 1.2.3: lighttpd 1.4.57, AlpineLinux [edge]: using cache breaks delivery
Date: Tue, 29 Dec 2020 18:04:51 +0100 [thread overview]
Message-ID: <20201229170451.2ofYK%steffen@sdaoden.eu> (raw)
In-Reply-To: <20201222212207.3qb-M%steffen@sdaoden.eu>
Steffen Nurpmeso wrote in
<20201222212207.3qb-M%steffen@sdaoden.eu>:
|Steffen Nurpmeso wrote in
| <20201222150957._aAW5%steffen@sdaoden.eu>:
||Steffen Nurpmeso wrote in
|| <20201222135537.ovyl4%steffen@sdaoden.eu>:
|||gs-cgit-lists.zx2c4.com@gluelogic.com wrote in
||| <20201222061206.GA54419@xps13>:
||||>Steffen Nurpmeso wrote in
||||> <20201221193127.zbZeP%steffen at sdaoden.eu>:
||||>|John Keeping wrote in
||||>| <X+DiDgGaPaynnocI at john.keeping.me.uk>:
||||>||On Mon, Dec 21, 2020 at 05:26:19PM +0100, Steffen Nurpmeso wrote:
||||>||> I discovered today that cgit no longer delivers pages, and it must
||||>||> have been like that for some time. The server looks show
||||>||> successful delivery, the cgit cache is populated and rotated just
||||>||> correctly, but all cgit delivers is that final error of main() as
| ...
||||>||> I am pretty sure cgit delivered some weeks ago, the most notable
||||>||> difference is that AlpineLinux switched to Lighttpd 1.4.56 then
||||>||> .57, which seems to have brought tremendous changes under the
||||> ...
||||>|But the file was generated normally:
| ...
||||>||and this may be caused by sendfile(2) failing due to some difference \
||||>||\
||||>||in
||||>||how the web server is setting up the output file descriptor. You may
| ...
|
|Looking at lighttpd commit history it seems he now uses splice(2)
|for CGI if possible.
On AlpineLinux with kernel 10.3 the unmodified cgit still fails.
I just want to note there is no kernel bugzilla entry regarding
sendfile and/or splice.
I assume the sendfile(2) failure fallback code path becomes
implemented and will unsubscribe again now.
Thanks.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2020-12-29 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 6:12 gs-cgit-lists.zx2c4.com
2020-12-22 13:55 ` Steffen Nurpmeso
2020-12-22 15:09 ` Steffen Nurpmeso
2020-12-22 21:22 ` Steffen Nurpmeso
2020-12-29 17:04 ` Steffen Nurpmeso [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-21 16:26 Steffen Nurpmeso
2020-12-21 17:57 ` John Keeping
2020-12-21 19:31 ` Steffen Nurpmeso
2020-12-21 22:23 ` Steffen Nurpmeso
2020-12-21 23:24 ` Steffen Nurpmeso
2021-01-02 18:38 ` Jon DeVree
2021-01-15 18:01 ` Jon DeVree
2021-01-15 21:51 ` Konstantin Ryabitsev
2021-01-15 22:41 ` Jon DeVree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201229170451.2ofYK%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=cgit@lists.zx2c4.com \
--cc=gs-cgit-lists.zx2c4.com@gluelogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).