From: devet@win.tue.nl (Arjan de Vet)
Newsgroups: comp.infosystems.gopher
Subject: Re: Two questions about running gopher
Date: 27 Aug 92 06:19:00 GMT
Reply-To: devet@win.tue.nl (Arjan de Vet)
Followup-To: comp.infosystems.gopher
Organization: Eindhoven University of Technology, the Netherlands


In article <leo.714837666@galaxy> leo@ph.tn.tudelft.nl writes:

|Two questions from a novice gopherd user. I have looked through docs,
|FAQ, and archived articles, but I couldn't find anything to help me.
|Nonetheless it's all pretty basic newbie stuff, I think.
|
|- Does the -s option work? If I give the command:
|
|   gopherd -s /usr/partool/lib/gopher.security -c
|
|and gopherd obligingly says:
|
|    Using Security file /usr/partool/lib/gopher.security
|
|and /usr/partool/lib/gopher.security consists of one single line:
|
|    !*
|
|then why am I still allowed to access gopher from everywhere??

There are some serious BUGS in the securityfile code, don't rely on it (yet).
I posted these securityfile problems a few days ago on
comp.infosystems.gopher and send mail to gopher@boombox.micro.umn.edu but
didn't get any reaction/acknowledgement so far.

|- If I change anything in a Link description in the .Links file (e.g. just 
|one character in the name field), then the next time I start up gopher *all*
|entries will be duplicated (and the pair for the entry I changed will be
|one correctly changed, one still the old entry).
|
|This freaks me no end: I know that gopher must still be storing that old
|information *somewhere* but I just cannot find it, let alone get rid
|of it (at one point I had deleted *every* file in the gopher home-directory,
|including .Links itself, and *still* I got those ghost-entries).

Let me guess: you use an editor which makes backups. All .xxxxxx files are
used for finding links, so .Links~ is used too!

|Leo Breebaart  (leo @ ph.tn.tudelft.nl)

Arjan
Newsgroups: comp.infosystems.gopher
From: devet@win.tue.nl (Arjan de Vet)
Subject: Re: Two questions about running gopher
Followup-To: comp.infosystems.gopher
Distribution: 
Keywords: 
Reply-To: devet@win.tue.nl (Arjan de Vet)
Organization: Eindhoven University of Technology, the Netherlands

In article <leo.714837666@galaxy| leo@ph.tn.tudelft.nl writes:

|Two questions from a novice gopherd user. I have looked through docs,
|FAQ, and archived articles, but I couldn't find anything to help me.
|Nonetheless it's all pretty basic newbie stuff, I think.
|
|- Does the -s option work? If I give the command:
|
|   gopherd -s /usr/partool/lib/gopher.security -c
|
|and gopherd obligingly says:
|
|    Using Security file /usr/partool/lib/gopher.security
|
|and /usr/partool/lib/gopher.security consists of one single line:
|
|    !*
|
|then why am I still allowed to access gopher from everywhere??

There are some serious BUGS in the securityfile code, don't rely on it (yet).
I posted these securityfile problems a few days ago on
comp.infosystems.gopher and send mail to gopher@boombox.micro.umn.edu but
didn't get any reaction/acknowledgement so far.

|- If I change anything in a Link description in the .Links file (e.g. just 
|one character in the name field), then the next time I start up gopher *all*
|entries will be duplicated (and the pair for the entry I changed will be
|one correctly changed, one still the old entry).
|
|This freaks me no end: I know that gopher must still be storing that old
|information *somewhere* but I just cannot find it, let alone get rid
|of it (at one point I had deleted *every* file in the gopher home-directory,
|including .Links itself, and *still* I got those ghost-entries).

Let me guess: you use an editor which makes backups. All .xxxxxx files are
used for finding links, so .Links~ is used too!

|Leo Breebaart  (leo @ ph.tn.tudelft.nl)

Arjan
Newsgroups: comp.infosystems.gopher