[Dxspider-support] Sysop manual suggestion

[Ian J Maude]

On Sun, 2002-03-03 at 15:04, Colin wrote:
> Hi,
> 
> Ian , if there is in existence a 1.49 manual (sysop version) perhaps this is
> already addressed :-
1.49 does indeed exist Colin.
> 
> Based on my 1.48 sysop admin manual there is little to
> confirm correct handling of the various .issue files. Some
> important ones are covered like forward / aliases etc. My attention was
> drawn to this by a recent question regarding the startup file which on my
> setup is still in the startup.issue state.
Basically any file with the extension .issue is precisely that, a file
delivered as a default.  It is done this way so that any updates do not
overwrite working files.  With the exception of the badwords file, none
of these files will work unless you rename them to remove the .issue
extension.  The 1.49 manual has a section on startup in the scripts
section but it has been pointed out to me that it is not as informative
as it could be so it will be getting a little extra treatment.
> 
> Would it be prudent in a future sysop admin manual to include a section to
> fully describe all the *issue files , how they can be manipulated , to what
> level should they be chmod'd and which directory they should remain in or be
> copied to ?
No chmod'ing should be required as all the files are owned (or should
be) by sysop.spider and the altered files would normally be left in the
same directories.  I should maybe do a little work on this to explain
more fully the use of the local and local_cmd directories.
I hope that helps a little
Ian


-- 

 Ian Maude G0VGS Morecambe Lancs UK | ian at gb7mbc.net
 Sysop of GB7MBC, the Morecambe Bay Cluster
 Running Linux and DXSpider