From: SMTP%"VMSGopher-L@trln.lib.unc.edu" 8-NOV-1994 16:47:23.91 To: EVERHART CC: Subj: Re: New query, build_index, walker X-ListName: Gopher for VMS implementation and testing Warnings-To: <> Errors-To: owner-vmsgopher-l@trln.lib.unc.edu Sender: owner-vmsgopher-l@trln.lib.unc.edu Date: Tue, 08 Nov 1994 13:09:29 -0700 (PDT) From: Bruce Tanner Reply-To: VMSGopher-L@trln.lib.unc.edu Subject: Re: New query, build_index, walker To: VMSGopher-L@trln.lib.unc.edu Message-ID: <01HJ8KLKC390IA09D4@Cerritos.edu> X-VMS-To: IN%"VMSGopher-L@trln.lib.unc.edu" X-VMS-Cc: TANNER MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > Everything I tried WORKED, except my appended walker.ctl control > file (even though it conforms to the robot-control-file standards of the > WWW no-robots working group, June 30, 1994 8-). You are absolutely right. I saw a mention of it here in August, but I didn't understand how it worked, so I pretty much ignored it. I'm probably not the only one who needs a tutorial on the care and feeding of robots. Can you give me a pointer to the standards? For instance: #----------------- SAMPLE walker.ctl FILE ------------------------- # File "walker.ctl". # Comment line; optional. # Install this file at one of these paths in your gopher server's # data heirarchy: # # walker.ctl or 0walker.ctl or 0/walker.ctl or 0/etc/walker.ctl # ** or ** # veronica.ctl or 0veronica.ctl or 0/veronica.ctl or 0/etc/veronica.ctl # ** or ** # robots.txt or 0robots.txt or 0/robots.txt or 0/etc/robots.txt # # Test it, to be sure your gopher can return the file. I don't see how the VMS Gopher would return any of those files; they're not legal... -Bruce -- Bruce Tanner (310) 860-2451 x 2164 Tanner@Cerritos.edu Cerritos College Norwalk, CA