Upgrade from Etch to Lenny finished, but what about ISPConfig?

Discussion in 'Installation/Configuration' started by danf.1979, Jul 10, 2010.

  1. danf.1979

    danf.1979 ISPConfig Developer ISPConfig Developer

    Hi folks, I just finished upgrading Etch to Lenny, but I don't if I have to do anything to ISPConfig for it to know it is working in Lenny. I haven't touch ISPconfig, just upgraded everything else. A lot of config files have changed their structure, for example apache2.conf and named.conf. Regarding bind9, stuff in named.conf should be now in named.conf.local, and it is using named.conf.options too, so I made those changes manually. Now ISPConfig is off, and I don't want to turn it on until I know if it will try to overwrite the new updated config files with old etch config system.

    So, is there anything to worry about?
     
  2. danf.1979

    danf.1979 ISPConfig Developer ISPConfig Developer

    Uhm, I am reinstalling ISPConfig, I guess that is what I have to do.
     
  3. oriongr

    oriongr Member

    The best option was to leave the conf file untouched...
    This is what I did the other day when I upgraded to lenny... and ISPconfig works fine...
     
  4. danf.1979

    danf.1979 ISPConfig Developer ISPConfig Developer

    I made a local backup of the server, and then I installed all the new versions of the config files when upgrading the server. Then, I made all needed changed in maybe 2 hours, so it was not too much work. Anyway, I had to undo the changes to named.conf, since ISPConfig does not use named.conf.local, or named.conf.options.
     

Share This Page