At 6:25 PM -0500 9/8/98, Rich Roth wrote: >I could see creating a mimimum configuration of Apache for this -- which >is what Stronghold does -- BUT I have enug trouble keeping my Apache >binaries current and still have the CPU load issue. > >Using SSH and a mini-httpd in perl running off of inetd (I suppose the >maint Apache could do that too, duh <g>) would give a trusted and >reliable-euf for maint commands server.
Of course, if the maintenance engine had its own source tree, it wouldn't be necessarily be required to always keep its binaries current at the same rate as the main server. I like the idea of using inetd for this, I think - I'm not sure of the impact on security etc. though. I'm willing to wait a few seconds for a lightweight server to start. I still like using a minimal Apache (as you noted :) I might not even keep the sources for the minimal one on the server, for security reasons. Another approach which allows a continuous session is the distributed Java method - I think in the long run this is probably the approach that will provide the most live interconnect. Byte magazine (I think?) recently had a distributed spreadsheet application in Java that might serve as a model for a live control panel. Again, all the data transfer can occur via SSL, SSH, or whatever. Just to throw another pot in the soup:) I've been playing with CVS again - 1.10 is now independent of RCS and other external things, and there are several GUI clients (Netscape and a couple others have Mac clients.), even a Web-based client interface. We're thinking of using it for user HTML document upload, and server system file maintenance. (I think Netscape uses it to maintain their web site, but I'm not sure.) It's not directly applicable to the maintenance engine, but has a very good version control method. I wonder if there is a potential for marriage here, to support tracking of configuration changes. Gary E. Bickford, [EMAIL PROTECTED] Sr. Systems Administrator, Connect Schlumberger http://www.connect.slb.com
