wiki.mbirth.de/know-how/software/linux/_posts/2008-08-13-mc-startup-delay.md

---
title: MC Startup Delay
layout: default
created: 2008-08-13 22:36:06 +0200
updated: 2008-08-13 22:36:06 +0200
toc: false
tags:
  - know-how
  - software
  - linux
  - mc
---
If Midnight Commander needs several seconds to startup, check the `interfaces` line in your `smb.conf`. According to [this page](http://osdir.com/ml/gnome.apps.mc.general/2006-09/msg00057.html),
the built-in Samba code of *mc* is outdated and doesn't recognize device names like `eth0` or `lo` as the newer
*smbclient* does. So it tries to resolve those into IPs which takes ages until they time out.

Replace the devices by their respective netmasks (e.g. `192.168.1.0/24`) and *mc* will startup instantly.
Added various pages. 2015-03-29 20:32:35 +01:00			`---`
			`title: MC Startup Delay`
			`layout: default`
			`created: 2008-08-13 22:36:06 +0200`
			`updated: 2008-08-13 22:36:06 +0200`
			`toc: false`
			`tags:`
			`- know-how`
			`- software`
			`- linux`
			`- mc`
			`---`
Fixed backticks. 2015-03-29 21:05:46 +01:00			If Midnight Commander needs several seconds to startup, check the `interfaces` line in your `smb.conf`. According to [this page](http://osdir.com/ml/gnome.apps.mc.general/2006-09/msg00057.html),
			the built-in Samba code of mc is outdated and doesn't recognize device names like `eth0` or `lo` as the newer
Added various pages. 2015-03-29 20:32:35 +01:00			`smbclient does. So it tries to resolve those into IPs which takes ages until they time out.`

Fixed backticks. 2015-03-29 21:05:46 +01:00			Replace the devices by their respective netmasks (e.g. `192.168.1.0/24`) and mc will startup instantly.