Old CB1.2 values in new CB 2.0?

[Richard G]

I upgraded a server from CB 1.2 to CB 2.0 last night via the instructions.
So by starting first with mv custombuild to custombuild_1.x and so on.

Now everything is working ok but I have these old CB 1.2 values in the CB 2.0 options.conf and I don't know how they got there.

proftpd=no
pureftpd=yes
jail=no
mailman=no
secure_htaccess=no
old_apr_util=no
default_php=5
php5_cli=yes
php5_cgi=no
php5_ver=5.3
php6_cli=no
php6_cgi=no
mail-header-patch=no
atmail=no
uebimiau=no
new_zlib=no
new_xml2=no
new_suphp=no

As you can see for example it says php_ver 5.3 but it's running version 5.5.x so it seems CB 2.0 does not look at these values anymore.
Can they be safely removed from the options.conf?

 

[BBM]

I believe I encountered this too when I first started with my VPS.
Mixed new and old settings in the new options-file.

That lead me pleading for help because my server went down about a week later just after adding a user. Something got messed in my case.

 

[smtalk]

CustomBuild 2.0 does not add these lines, so it might be that you still had an old binary. It's safe to remove the lines.

 

[Richard G]

Wel I moved the complete custombuild directory as was stated in the instructions, so if something mixed up the options file it must have been DA itself.

Or like Smtalk says an old binary left over somewhere.
Anyway if it's safe to remove them I'll do that at once and will delete the custombuild_1.x directory too. Thank you.