Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi All!
I have been tryng to get apache working with virtual hosts and screwed up my apache2.conf file, so I thought no problem I will uninstall it!
So I did and I removed it using apt-get --purge remove for apache2 & apache2-common, but it has left all my files still there, and if also if I run /etc/init.d/apache2 start it tries to start but complains there is no apache2.conf file!
I just don't get it, why has apt not removed it all lock stock ect. What I am trying to do is start from scratch with apache.
So are my options?
1, wipe the box and start again (but that defeats the object of running linux to me)
2, or is there a way to totaly remove/trash apache2 and start again?
Hi, thanks for the reply, the first command generated nothing but the second generated the following;
jibend:/etc/apache2# aptitude search ~c | grep apache
jibend:/etc/apache2# aptitude search ~i | grep apache
i apache2-doc - documentation for apache2
i apache2-mpm-prefork - Traditional model for Apache HTTPD 2.1
i A apache2-utils - utility programs for webservers
i A apache2.2-common - Next generation, scalable, extendable web
i libapache2-mod-perl2 - Integration of perl with the Apache2 web s
i libapache2-mod-php5 - server-side, HTML-embedded scripting langu
i libapache2-mod-python - Apache 2 module that embeds Python within
aptitude purge apache2 would have been a better choice, but we can still work with this.
the search using ~c shows config files that are left behind. according to that output the apache confgs have not been removed..
aptitude purge ~c
that should remove ALL leftover config files from packages that have been removed from your system. surprise you will probably see a list a LOT larger than just those apache items. I just discovered this the other day and found I had leftovr config files form 150 odd packages on my system that had been automatically removed..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.