From: maht <maht-9fans@maht0x0r.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] httpd
Date: Wed, 20 Jan 2010 18:12:17 +0000 [thread overview]
Message-ID: <4B574781.7080301@maht0x0r.net> (raw)
Hi,
I updated http://plan9.bell-labs.com/sources/contrib/maht/httpd/* to
sync with current source
/n/sources/contrib/maht/httpd/*
It adds -N option to stop it dropping to none which you have to be the
hostowner to kill
and logs any 404's to /sys/log/httpd/log
I tried to see if it's in patch already but that's taking too long
(patch/list has been sat there 30 mins now)
Matt
next reply other threads:[~2010-01-20 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 18:12 maht [this message]
2010-01-20 19:05 ` maht
-- strict thread matches above, loose matches on Subject: below --
2005-10-10 15:31 Skip Tavakkolian
2005-10-10 15:35 ` Russ Cox
2005-10-10 19:27 ` Ronald G Minnich
2005-10-10 20:14 ` Skip Tavakkolian
2005-10-14 13:51 ` sam ducksworth
2005-10-18 10:06 ` Charles Forsyth
2005-10-18 17:24 ` Skip Tavakkolian
2005-10-18 17:35 ` Uriel
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=4B574781.7080301@maht0x0r.net \
--to=maht-9fans@maht0x0r.net \
--cc=9fans@9fans.net \
/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).