Thanks everyone for your help with this problem. It was indeed a DNS problem, due to my not specifying a fully-qualified host name. I now have separate network files with appropriate host+domain names for the different laptop environments I'm in, and sendmail starts up quickly. On a related note, the reason I left the domain off was because I thought it was retrieved automatically from the DHCP server (this appears to happen on Mac and Windoze systems). Setting "require domain-name;" in /etc/dhclient-eth0.conf didn't do anything useful (although I still got a lease). Copying config files for different wireless environment works, but it should be easier than this. Tom On Tue, 2003-08-05 at 02:05, John Haxby wrote: > Tom Ball wrote: > > >When /etc/init.d/sendmail starts, it waits for a long time on the > >/usr/bin/newaliases command. According to the documentation, this > >command is needed to recompile the /etc/aliases file, which I've never > >changed. Is there a reason the default one takes so long to recompile > >(or why its last-modified date isn't checked)? > > > > > A _very_ slow newaliases is almost certainly as a result of the DNS not > functioning. (A moderately slow one is usually something else :-)) > > If you can fix your DNS problems then you won't have a problem with > newaliases. Having said that fixing the DNS problem might be rather hard. > > Alternatively, put > > test /etc/aliases.db -nt /etc/aliases && > > in front of the newaliases command in the sendmail start-up script. I > haven't tested this, but it should be OK. It's also not perfect -- the > contents of /etc/aliases.db actually depends upon the sendmail > configuration as well as the contents of /etc/aliases, albeit in a > fairly subtle way. I suppose really that the invocation of newaliases > should be after the make/makemap stuff. > > jch > > jch > -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
