DebianThis forum is for the discussion of Debian Linux.
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.
You can get rid of it but you'll miss some local mail reports from unauthorized sudo, snort mails and some such.
Don't know which mta you have though but "dpkg -l |grep mta" might tell. Could be exim if I'll take a guess.
A standard install is going to come with exim, so that's probably what you've got.
I've never noticed exim taking up much time on my system. Maybe run eximconfig (wait, on Woody it was eximconfig, now it's dpkg-reconfigure exim I believe) and make sure it's only set up for local delivery... That *may* affect startup time (let us know).
Don't try removing exim unless you know what you're doing, and are probably familiar with the equivs package.
I don't actually want it back, but if I should decide to disable something else (apache2, or other things I don't have a use for at this time), I just wanted to know if there was a way to get them back in case I wanted them later.
Originally posted by RodWC "Starting MTA" takes an inordinately long time and I was wondering if I could bypass it? It would cut boot time by more than half!
I have two systems with Sarge 3.1r0a installed. One, like yours, experiences a long pause when starting MTA. The other does not (I don't know why).
Being more old school Unix and not up on the newest configuration widgets that are available with a modern Linux distribution (still a Linux Newbie)...
As root I just cd'ed to /etc/rc2.d and renamed S20exim4 to s20exim4 (note the uppercase to lowercase change for the first letter). Ditto for the same file in /etc/rc3.d, rc4.d, and rc5.d Then I manually killed the exim that was currently running with "/etc/init.d/exim4 stop".
Location: 1st hop-NYC/NewJersey shore,north....2nd hop-upstate....3rd hop-texas...4th hop-southdakota(sturgis)...5th hop-san diego.....6th hop-atlantic ocean! Final hop-resting in dreamland dreamwalking and meeting new people from past lives...gd' night.
Distribution: Siduction, the only way to do Debian Unstable
You could just do sudo rcconf and untick exim,apache,cups,etc and whatever else you do not need now and it wont start at boot time.If you need it in the future just rcconf again and tick it,exit,reboot.
"Starting MTA" takes an inordinately long time and I was wondering if I could bypass it? It would cut boot time by more than half!
This is a common question. It's typically related to an unsuccessful reverse DNS lookup that the Mail Transfer Agent tried to do. Usually - I've figured out -, this is caused by incorrect information in /etc/resolv.conf.
For example, if you're not planning to use (outgoing) mail at all on your server you would set up exim4 (the default MTA on Debian) such that it delivers mail locally only. You can configure this with:
# dpkg-reconfigure exim4-config
The main point to resolve the issue, however, is /etc/resolv.conf. For local delivery it should look like this:
For "real" domains (and local delivery) I've seen it works fine also when you simply omit the nameserver, e.g: