• Cleanup Util

    From BRIAN CAOUETTE@1:124/5013 to All on Thursday, January 31, 2019 19:10:38
    Date: Tue, 26 Nov 2002 11:50:10 -0400
    From: BRIAN CAOUETTE
    To: ALL
    Subject: Cleanup Util
    Newsgroups: win.server.wish.list
    Message-ID: <1038329799.33.0@winserver.com>
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 11

    Hector, I been thinking how about some type of utility that will process all files in wc5 including subdirs and print out a list of files that are not
    stock files? Perhaps even version analysis were possible to help prevent and eliminate potential problems? With current version we are not able to place *wcx files in their own directories so the root of wc5 has become cluttered with useless and potentially problem causing *wcx's. Perhaps a cleanup
    utility of some sort would go a LONG way in helping to organize the mess.
    Are custom paths for wcx's in the near future?


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CHRIS CRANFORD@1:124/5013 to All on Thursday, January 31, 2019 19:10:38
    Date: Wed, 27 Nov 2002 09:54:05 -0400
    From: CHRIS CRANFORD
    To: BRIAN CAOUETTE
    Subject: Re: Cleanup Util
    Newsgroups: win.server.wish.list
    Message-ID: <1038409286.33.1038329799@winserver.com>
    References: <1038329799.33.0@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 52

    I think it would be useful to provide custom paths for things such as:

    + Logs (activity.*, *.log)
    + WCX (*.wcx)

    The following suggestion would require sysops to rewrite/modify batch files; however for those of us who would like to clean up our installation
    directory much easier, maybe offering a way to set these paths if we wish to use them for seperate directories; otherwise default them to the standard
    \wc5 directory.

    + Executables (*.exe, *.hlp, *.cnt, *.chm) put in \wc5\bin
    + Library Files (*.dll) put in \wc5\lib

    I'm not sure what Hector's plans are for the wcLISTSERVE data files when the wcLISTSERVE is moved to using an ODBC type connection instead of using the current data file format. Maybe the wcLISTSERVE data files and mailing list files could be moved from the \wc5 directory to either \wc5\config or
    \wc5\data along with the other data/config files for Wildcat! (same could
    be applied to wcnews configuration too being moved to \wc5\config) ...

    I'm just used to having an application folder that really don't contain much
    of anything and all parts of a program are seperated into their component
    type directories (binary files in \bin, library files in \lib, etc); however making such a change like this would potentially mean a large architectural change to Wildcat! which isn't all too important at the moment based on some
    of the other things I'd like to see available (such as multi-web virtual
    domain support and other HTTP/1.1 compatible functionality).

    But I'm sure that over time Hector's going to continue to move us in the
    right direction in order to keep Wildcat! on top :-)

    Chris

    <BRIAN CAOUETTE> wrote in message news:1038329799.33.0@winserver.com...
    Hector, I been thinking how about some type of utility that will process
    all
    files in wc5 including subdirs and print out a list of files that are not stock files? Perhaps even version analysis were possible to help prevent
    and
    eliminate potential problems? With current version we are not able to
    place
    *wcx files in their own directories so the root of wc5 has become
    cluttered
    with useless and potentially problem causing *wcx's. Perhaps a cleanup utility of some sort would go a LONG way in helping to organize the mess.
    Are custom paths for wcx's in the near future?




    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From BRIAN CAOUETTE@1:124/5013 to All on Thursday, January 31, 2019 19:10:38
    Date: Wed, 27 Nov 2002 19:33:49 -0400
    From: BRIAN CAOUETTE
    To: CHRIS CRANFORD
    Subject: Re: Cleanup Util
    Newsgroups: win.server.wish.list
    Message-ID: <1038444022.33.1038409286@winserver.com>
    References: <1038409286.33.1038329799@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 69

    My concern is I'm more of an ISP so it would be easier to dump all the games and other files that aren't being used any longer. Basically signal anything that is non WINS and if it is confirm versions against aup to make sure
    there aren't any dups or version mismatches. I suppose I could do a clean reinstall to another machine and compare dirs but that could be time
    consuming.

    <CHRIS CRANFORD> wrote in message news:1038409286.33.1038329799@winserver.com...
    I think it would be useful to provide custom paths for things such as:

    + Logs (activity.*, *.log)
    + WCX (*.wcx)

    The following suggestion would require sysops to rewrite/modify batch
    files;
    however for those of us who would like to clean up our installation
    directory much easier, maybe offering a way to set these paths if we wish
    to
    use them for seperate directories; otherwise default them to the standard \wc5 directory.

    + Executables (*.exe, *.hlp, *.cnt, *.chm) put in \wc5\bin
    + Library Files (*.dll) put in \wc5\lib

    I agree. Perhaps even protected dirs for Wins so nothing but Wins can be put
    in them. Just another way to help safegaurd the install.

    I'm just used to having an application folder that really don't contain
    much
    of anything and all parts of a program are seperated into their component type directories (binary files in \bin, library files in \lib, etc);
    however
    making such a change like this would potentially mean a large
    architectural
    change to Wildcat! which isn't all too important at the moment based on
    some
    of the other things I'd like to see available (such as multi-web virtual domain support and other HTTP/1.1 compatible functionality).

    I agree. I would LOVE to see host header support built in. Pushing this
    issue even further when a user FTP's into the system they would be in there virtual web server directory were they can manage their domain. Right now
    i'm using IIS and WARTFPD to do this. Also wouldn't mind seeing some type of load balancing so we can specify which domains are servered of each
    computer. Example

    Computer 1. Main Server
    Computer 2. Business Web Pages. (www.theirdomain.com)
    Computer 3. Personal Web Pages. (userpages.mydomain.com/customer)
    Computer 4. Radius / SMTP / POP3

    Etc...

    Also ability to go into maintenance mode were ALL pages/domains would say
    down for maintenance try again later. And release the lock on files so they could be backed up. And while on the subject of maintenance mode perhaps a standalone wcSMTP that would accept mail for ALL domain while the system was
    in maintenance mode and forward when it was back up.

    But I'm sure that over time Hector's going to continue to move us in the right direction in order to keep Wildcat! on top :-)

    I'm sure he will. Things have come a long way but there is still allot more
    to be done.

    Boy this message got a little lengthy.

    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)