Re: [Server-devel] config file mess
On Thu, Aug 21, 2008 at 3:39 AM, Joshua N Pritikin [EMAIL PROTECTED] wrote: I accidentally upgraded from XS_165 to a new xs-config (maybe 0.3.1?). The upgrade got stuck halfway through, and I cancelled it. What is the proper way to fix config files? Copy foo.conf to foo-xs.conf? I already fixed named and squid. What other services do I need to check? Ouch. That will be a big disaster, I am just fixing the bugs around that at the moment. Two options - reinstall the most recent xs-config you can get from the testing repo. That will leave just a couple of broken bits that I am fixing today hopefully - reinstall 165 from scratch Seriously. Any manual attempt to fix 165's xs-config will take a few days :-/ cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] config file mess
On Thu, Aug 21, 2008 at 09:07:02AM +1200, Martin Langhoff wrote: On Thu, Aug 21, 2008 at 3:39 AM, Joshua N Pritikin [EMAIL PROTECTED] wrote: I accidentally upgraded from XS_165 to a new xs-config (maybe 0.3.1?). Ouch. That will be a big disaster, I am just fixing the bugs around that at the moment. Two options - reinstall the most recent xs-config you can get from the testing repo. That will leave just a couple of broken bits that I am fixing today hopefully I updated to testing. The GIT stuff is great. However, why is xs-commit-change so slow? ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] config file mess
On Thu, Aug 21, 2008 at 4:11 PM, Joshua N Pritikin [EMAIL PROTECTED] wrote: I updated to testing. The GIT stuff is great. Did your configuration survive? Any _broken_ symlinks? Things still work? However, why is xs-commit-change so slow? It's not slow for me -- in relative terms. Definitely ~1s each call here. If you are used to git's normal blazing speeds, a couple of things get in the way... - /etc is a large directory. git is optimised to keep track of all or most of the files it sees... - The ops will mostly be on cold-cache. - The python wrapper imposes ~1s startup costs... I did draft it in shell, but a shell metachar escapes are safer/saner in python, and I'm not out to win a speed race with this, so... Let me know if you see it significantly slower than ~1s m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
