Thank you all for all the information. By adding "host.local" to
/etc/hosts as follows:
127.0.0.1 localhost host.local
the problem disappears. (I added host.local where host is the name of
the machine.) Thank you again. It helped me very very much!
Sincerely,
--
Kenichi Asai
On Thu, Dec 20, 2018 at 02:47:51PM -0600, Derek Martin wrote:
You can also just set the hostname config variable in your muttrc, and
then it should skip the DNS lookup.
Actually the Hostname and Fqdn setting are done before any config files
are read in. I seem to recall there is some obscure
On Thu, Dec 20, 2018 at 10:05:30AM -0800, Kevin J. McCarthy wrote:
> On Thu, Dec 20, 2018 at 06:14:31PM +0900, Kenichi Asai wrote:
> >My guess is that mutt automatically checks some machine or network
> >configuration and wait 5 seconds for time out before starting. Does
> >mutt do such things?
I've seen this issue before on macOS. Specifically it happens if your
hostname has a dot. Here's an example program showing how long this can
take. https://gist.github.com/keith/86642ac3f695841b17906732c803fda3
I _believe_ I fixed this with:
`sudo scutil --set HostName name-without-dot`
--
On Thu, Dec 20, 2018 at 06:14:31PM +0900, Kenichi Asai wrote:
My guess is that mutt automatically checks some machine or network
configuration and wait 5 seconds for time out before starting. Does
mutt do such things? How can I learn about them?
In 1.6.0, mutt was changed to determine the
On 20181220, Kenichi Asai wrote:
> Why does it take so long time to start up? Have anybody had the same
> experience? What should I check?
Try starting it with "-d nnn" debugging; that might show you where it's pausing.
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
for decades, but this is the first time to
experience such slow startup.
Any help welcome. Thank you in advance.
Sincerely,
--
Kenichi Asai