Re: [bitfolk] Wheezy

Thanks for that Ian. Just a quick question for the list - I'm going to upgrade in a short while - am I right in thinking that I can reboot the VPS at the end of the upgrade process (to load the new kernel) without rebooting the machine on which the VPS resides?

Thanks Barry On 21 May 2013 15:54, Ian &lt;ian(a)lovingboth.com&gt; wrote: > I've just done the upgrade on one VPS. I came across two issues. > > The first was that, although it doesn't seem to be in the Debian release > notes's list of obsolete packages, the list of packages that will be > removed because it's been dropped includes sysklogd. > > So if you use that for syslogd - and as I don't remember installing it, it > was probably in the initial Lenny VPS - you need to install > inetutils-syslogd instead. Before the upgrade is probably best but either > way.. > > apt-get install inetutils-syslogd > > .. will get a working syslogd. > > Keith Williams said: > > The whole Dovecot config set up has changed. But if, like me, you last >> set it up a couple or more years ago, you need to follow the HOWTOs on >> the web. It's very straight forward and you can infact forget the >> include files and just set up one straight forward conf file from scratch >> > > The relevant info is not quite as easy to find as it should be, but it > seems to come down to going to /etc/dovecot and.. > > .. moving the ssl certificates: > > /etc/dovecot# mv /etc/ssl/certs/dovecot.pam . > /etc/dovecot# mv /etc/ssl/private/dovecot.pam private/ > > (per the warning when apt-get fails to upgrade dovecot: > > Setting up dovecot-core (1:2.1.7-7) ... > You already have ssl certs for dovecot. > However you should move them out of /etc/ssl > and into /etc/dovecot and update the configuration > in /etc/dovecot/conf.d/10-ssl.**conf accordingly. > See /usr/share/doc/dovecot-core/**README.Debian.gz for details.) > > .. then upgrading the conf files: > > /etc/dovecot# mv dovecot.conf dovecot.conf.squeeze > /etc/dovecot# doveconf -n -c dovecot.conf.ucf-old >dovecot.conf > > That generates a series of warnings: > > doveconf: Warning: NOTE: You can get a new clean config file with: > doveconf -n > dovecot-new.conf > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:24: 'imaps' > protocol is no longer necessary, remove it > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:24: 'pop3s' > protocol is no longer necessary, remove it > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:101: > ssl_cert_file has been replaced by ssl_cert = <file > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:103: > ssl_key_file has been replaced by ssl_key = <file > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:665: protocol > managesieve {} has been replaced by protocol sieve { } > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:814: add auth_ > prefix to all settings inside auth {} and remove the auth {} section > completely > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:851: passdb > pam {} has been replaced by passdb { driver=pam } > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:888: userdb > passwd {} has been replaced by userdb { driver=passwd } > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:960: userdb > passwd {} has been replaced by userdb { driver=passwd } > doveconf: Warning: Obsolete setting in dovecot.conf.ucf-old:1023: > auth_user has been replaced by service auth { user } > > .. but the result is working. > > (The source for the last bit reckoned you also needed > > chmod 644 dovecot.conf > > too, but that's what it was.) > > If I've missed anything, do let me know. > > Ian > > ______________________________**_________________ > users mailing list > users(a)lists.bitfolk.com > https://lists.bitfolk.com/**mailman/listinfo/users<https://lists.bitfolk… >

_______________________________________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/users