From: Mel Hatzis <hatzis@juniper.net>
To: Chad Walstrom <chewie@wookimus.net>
Cc: help-gnats@gnu.org
Subject: Re: Restoring GNATS database
Date: Fri, 16 Apr 2004 20:56:00 -0000 [thread overview]
Message-ID: <40801DA8.90700@juniper.net> (raw)
In-Reply-To: <20040415155650.GC12267@wookimus.net>
On 04/15/2004 08:56 AM, Chad Walstrom submitted:
> On Thu, Apr 15, 2004 at 04:09:48PM +0200, Yngve Svendsen wrote:
>
>>>>Yes, GNATS normally run as a specially created "gnats" user.
>>>>However, I think that root access was required to administer that
>>>>GNATS and Gnatsweb installation.
>>>>
>>>>
I believe 'root' access isn't necessary for GNATS provided you have the
following things setup prior to installation:
- (x)inetd
- a 'gnats' user/group on the server
- an install directory owned by gnats:gnats
>>
>>If we get a properly maintained Debian package, as looks likely now,
>>with Chad's efforts, that would be the way to do it. I am still pretty
>>sure we would need root access, though.
>
>
> There's nothing magical about root with respect to gnatsweb or gnats.
> Without Mel's patches, gnatsd runs from (x)inetd, and gnatsweb runs as
> the apache user (www-data on Debian). gnatsweb-site.pl can be linked
> into /usr/lib/cgi-bin from anywhere and given any permissions we need.
Indeed....and even with my patches, you can still run GNATS this way,
both for the flat-file backend as well as the database backend.
[ Running gnatsd via (x)inetd with a database backend though isn't
advisable, given the database connection cost for each client request. ]
>
> Additionally, fencepost admins can give us sudo access for those
> components we need access to.
Agreed.
>
>>I think we ought to push hard to get this on fencepost, because that
>>is really where this belongs. If that proves hard, I should be able to
>>host it on one of the Debian boxes in my own basement. It is currently
>>hooked up to a 1600/512 ADSL connection with a fixed IP address.
>
>
> Likewise. I'm gearing up an older Ultrasparc 5 to be my 'Net server to
> be colocated in a friend's basement (with a dedicated DSL connection).
> Additionally, I have a friend who's hosting my current domains and
> wouldn't have any problem with hosting a gnats database. (I need to
> donate a bit for his new server anyway.)
>
> In other words, we shouldn't resort to paying some virtual hosting
> services just yet. Between Yngve, myself, and FSF there should be
> plenty of network resources to leverage.
>
Sounds good.
-Mel
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2004-04-16 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 14:32 Andrew Gray
2004-04-15 16:01 ` Yngve Svendsen
2004-04-15 17:08 ` Chad Walstrom
2004-04-15 17:57 ` [OT] CC'ing and the list Chad Walstrom
2004-04-16 20:56 ` Mel Hatzis [this message]
2004-04-16 8:18 ` Restoring GNATS database Andrew Gray
2004-04-15 16:20 ` Chad Walstrom
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=40801DA8.90700@juniper.net \
--to=hatzis@juniper.net \
--cc=chewie@wookimus.net \
--cc=help-gnats@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).