Date: Tue, 6 Aug 2002 13:57:09 -0500
To: gopher@complete.org
Subject: [gopher] Process question
Message-ID: <20020806135709.A6583@pongonova.net>
Mime-Version: 1.0
Content-type: text/plain
Content-Disposition: inline
User-Agent: Mutt/1.3.19i
From: Brian <brian-keyword-gopher.6f04ff@pongonova.net>
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

I have a process question about gopher, and gophermap specifically.  I'm tempted to
automagically generate a new gophermap whenever I add new files/dirs to my gopher
root dir.  From what I can tell, gophermap is an all-or-nothing deal:  If you use
it, then everything you want accessible has to be part of gophermap.  If you don't,
then everything in the gopher root is accessible.

Since I'm opting to use a gophermap file (in each dir), I'll need to keep it updated
with new additions.  

Is my understanding correct?  If not, I'd appreciate some pointers as to how you go
about keeping your gopher server healthy and well-fed.

  --Brian

-- Attached file included as plaintext by Ecartis --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9UBwF3ghB5mCv328RAowLAJwKcmRzokBJcyEQ3gaxeK8wwC4qvQCgjaDX
Ao3rMZ17R4IgeKd45fb9boo=
=fj0Q
-----END PGP SIGNATURE-----