bad command 'mdns'off'

Message

mjh74 · Post by **mjh74** » Sun Oct 31, 2004 12:25 am

Hi all,

Could anyone tell me what I can do to cure this error other than to just comment the line out in host.conf. On bootup I get the following..

/etc/host.conf: line 24: bad command 'mdns off'

The line in /etc/host.conf is just mdns off.

This only occurred since my last system update. Is it ok just to leave the line commented out?

TIA

Mark.

Merlin-TC · Post by **Merlin-TC** » Sun Oct 31, 2004 12:36 am

I am having the same problem.
I haven't found a fix yet because I am not sure what actually causes the error.
The command should be known by the system.
Do you know which package caused it?
I suspect the baselayout or glibc.
I also noticed that in the rc.conf the timezone setting is missing.
So I had to enter it myself again: CLOCK=local

Does anyone know why it was removed?

mjh74 · Post by **mjh74** » Sun Oct 31, 2004 12:57 am

I'm almost certain it was glibc yes...

chi · Post by **chi** » Sun Oct 31, 2004 5:20 am

The "CLOCK=local" is in /etc/conf.d/clock now.

Merlin-TC · Post by **Merlin-TC** » Sun Oct 31, 2004 5:33 am

Ah thanks

mjh74 · Post by **mjh74** » Sun Oct 31, 2004 11:01 am

And for the mdns problem? Any thoughts anyone?

apache · Post by **apache** » Mon Nov 01, 2004 1:41 pm

I think it's safe to comment it out, it should be the same as 'mdns off' and I think the most people do not need MultiCast DNS.

infion · Post by **infion** » Mon Nov 01, 2004 6:22 pm

For me the problem with

/etc/host.conf: line 24: bad command 'mdns off'

was solved after I recompiled glibc

mjh74 · Post by **mjh74** » Mon Nov 01, 2004 7:21 pm

Hmmm I tried that and still the same. I will just comment the line out.

ensonic · Post by **ensonic** » Wed Nov 03, 2004 9:04 pm

I am having the problem too. And I suspect that this causes problems with network resolution. My dnsdomainname is in fact 'local' and therefore
mdns needs to be off.

I am not sure if this is linked, but when I try 'hostname -f' (or -s or -d') I always get 'hostname: Unknown host'

apache · Post by **apache** » Sun Nov 07, 2004 1:33 pm

A few days ago a new version of glibc appeared in portage. After upgrading to this version (2.3.4.20041102, ACCEPT_KEYWORDS="~x86"), the problem disappeared.

richard.scott · Post by **richard.scott** » Fri Apr 01, 2005 11:54 am

I had this problem after an upgrade of glibc to 2.3.4.20041102-r1.

After lost of head scratching and shouting "yet again upgrading glibc as broken stuff" I rebooted my system and all seems to be fixed.

I've got to go and check the console now, but I think its all ok.

EDIT: ok, cancel that, its still broken

stebo0728 · Post by **stebo0728** » Fri May 05, 2006 2:19 am

run the command

#etc-update

when it asks about config files, choose the "-5" option, then reboot, it should fix this, it worked for me

bunder · Post by **bunder** » Fri May 05, 2006 4:20 am

stebo0728 wrote:run the command

#etc-update

when it asks about config files, choose the "-5" option, then reboot, it should fix this, it worked for me

you shouldn't even have to reboot. after the etc-update (in which host.conf will need to be updated), the error will simply disappear.

HeXiLeD · Post by **HeXiLeD** » Sat May 06, 2006 2:48 pm

Same problem here in 2 boxes. ( was a fresh install )
#dispatch-conf to update the config files and then #emerge -Duav world downgraded glibc.

After that the issue was solved.

Bones McCracker · Post by **Bones McCracker** » Sun May 07, 2006 12:06 am

running etc-update you will note the mdns line is removed

Dr. Strangelove · Post by **Dr. Strangelove** » Sun May 07, 2006 10:02 am

BoneKracker wrote:running etc-update you will note the mdns line is removed

Yes, and just do simple

Code: Select all

# man host.conf

for wondering about (non-)existence of 'mdns' lines.
Good Luck!

bad command 'mdns'off'

bad command 'mdns'off'

run this command

Re: run this command