In the past I stored my DTF and IDX files on a machine with a fast hard drive and used windows networking and drive mapping to string it all together. This took very little specialized knowledge and was relatively simple to maintain. Looking down the road just a little bit I realize that for me to utilize the power of sesame in a multi user environment I will need to start re-thinking my networking setup. These changes may involve hardware and operating system changes and new system maintenance and operations to learn.  This brings up numerous questions in which experienced networking users can really save us some headaches.

What server software is best to use with Sesame or in general. (Windows, Red Hat Linux, free BSD or ??)

What forms of daily maintenance besides backups would you suggest needs to be performed with Sesame and the server software?

What could you tell a newbie about the process of migrating to this type of server setup that will save us grief?

Has anyone used a managed Dedicated or co-located Server Hosting service to maintain the server hardware and eliminate the server part of the equation?

All thoughts and comments on this subject will be greatly appreciated. This will surely be the next logical step many Sesame users and developers will need to take after becoming proficient in the use of Sesame software.

Thanks

It seems that Sesame should have a "max log size" option so that the Log file will not continue to grow to an exhorbitant size.

I intend to load Sesame as a "service" on a server, and hope that Sesame will not require much maintanance. I guess I could have a shortcut to the log file on a client machine to get quick access to delete the file when it grows too large.

Just a thought.

Steve in Texas

Thanks! Mark said Sesame will want its log deleted every now and then, but 10,000 lines doesnt sound too bad.