List for cgit developers and users
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: John Keeping <john@keeping.me.uk>, cgit@lists.zx2c4.com
Subject: Re: cgit 1.2.3: lighttpd 1.4.57, AlpineLinux [edge]: using cache breaks delivery
Date: Tue, 22 Dec 2020 00:24:40 +0100	[thread overview]
Message-ID: <20201221232440.CAN3r%steffen@sdaoden.eu> (raw)
In-Reply-To: <20201221222300.z9Vio%steffen@sdaoden.eu>

Steffen Nurpmeso wrote in
 <20201221222300.z9Vio%steffen@sdaoden.eu>:
 |Steffen Nurpmeso wrote in
 | <20201221193127.zbZeP%steffen@sdaoden.eu>:
 ||John Keeping wrote in
 || <X+DiDgGaPaynnocI@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
 |||> 
 |||>   <div class='error'>Error processing page: Invalid argument (22)</div>
 ...
 |||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
 |||want to rebuild CGit without HAVE_LINUX_SENDFILE and see if that works.
 |
 |So i build it with
 ...
 |  -       CGIT_CFLAGS += -DHAVE_LINUX_SENDFILE
 |  +       #CGIT_CFLAGS += -DHAVE_LINUX_SENDFILE
 ...
 |and
 |
 |  make NO_LUA=y NO_ICONV=y NO_GETTEXT=y NO_TCLTK=y NO_PERL=1 \
 |    NO_PYTHON=1 NO_SVN_TESTS=y NO_REGEX=NeedsStartEnd prefix=/usr
 |
 |and .. it works.
 |
 |Thank you, i will open an AlpineLinux bug report.  And lighttpd.

Did that.  Though redmine lighttpd threw me out after password
reset, i posted in #lighttpd irc.freenode.net a few minutes ago.
FreeBSD also has a sendfile by the way, had that already twenty
years ago, and worked great!  Slightly different semantics though.
But doable (by then).  The guys from nginx strive for tweaking the
last little thing out of that btw.  Just last week iirc they added
NUMA specific ioctls to be able to gain more locality.

I think i will go again soon, now that this is worked out :)
Thanks,
Ciao and greetings from Germany,

--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)

  reply	other threads:[~2020-12-21 23:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
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

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=20201221232440.CAN3r%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=cgit@lists.zx2c4.com \
    --cc=john@keeping.me.uk \
    /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).