Hey Filezilla supports uploading files over ssh (sftp), which you no doubt already have set up and running. It's more secure than ftp and I've found it less error prone when transferring large sets of files. Hope that helps, M _______________________________________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/users

Hi Barry, On Fri, Oct 04, 2013 at 07:56:42PM +0100, Barry Watson wrote: find The /etc/apache2/apache2.conf file as shipped by Debian squeeze includes this: # Include all the user configurations: Include /etc/apache2/httpd.conf and the /etc/apache2/httpd.conf file as shipped by Debian squeeze merely contains: # This is here for backwards compatability reasons and to support # installing 3rd party modules directly via apxs2, rather than # through the /etc/apache2/mods-{available,enabled} mechanism. # #LoadModule mod_placeholder /usr/lib/apache2/modules/mod_placeholder.so i.e. nothing. The /etc/apache2/apache2.conf file is owned by the package apache2.2-common: $ dpkg -S /etc/apache2/apache2.conf apache2.2-common: /etc/apache2/apache2.conf It is treated as a Conffile by this package: $ dpkg-query -W -f='${Conffiles}\n' apache2.2-common | grep 'apache2\.conf' /etc/apache2/apache2.conf 95c489c44ce638dca8c44be18ebc8353 which means that, when you come to upgrade the apache2.2-common package, if your /etc/apache2/apache2.conf file is unmodified from what was shipped in the package then it will give you the new version of the file without asking. However if your file has been changed (e.g. by you configuring something in there) then it will instead ask you if you wish to have the new version, keep the old version, or take a few other actions like inspect a diff, etc. So, I suspect what happened is that your /etc/apache2/apache2.conf was previously modified by you, then you were asked if you wanted to replace it during upgrade but you said no, so you kept the version from Debian squeeze which refers to httpd.conf. Also that you have at some point deleted /etc/apache2/httpd.conf. Possibly the upgrade procedure deleted it if was never changed. If that suspicion is correct then you will probably have an /etc/apache2/apache2.conf.dpkg-dist lying about which would be the new file that it wanted to install. Some more info about Debian Conffile handling: http://raphaelhertzog.com/2010/09/21/debian-conffile-configuration-file-man… Personally where possible I find it worth going out of my way to avoid editing the Conffiles that .deb packages install, and instead putting my edits into separate files. Many packages have facilities for doing that. This reduces the number of decisions that need to be made during a package upgrade. Cheers, Andy -- http://bitfolk.com/ -- No-nonsense VPS hosting _______________________________________________ users mailing list users(a)lists.bitfolk.com https://lists.bitfolk.com/mailman/listinfo/users