[cod] couldn't exec *.cfg

[Glanzer]

Yeah, those errors have always existed.  Apparently CoD automatically looks
for those and executes them if they exist.

BTW, never name your server's .cfg file "server.cfg" because CoD will ignore
it when you try to exec it.  For more info see:

http://www.codadmin.com/nuke/modules.php?name=Forums&file=viewtopic&t=2824

I'm sure all this is documented somewhere....

--Glanzer
(Moderator of http://www.codboards.com)


----- Original Message ----- 
From: "John Kennington" <john.kennington at buzzcard.gatech.edu>
To: <cod at icculus.org>
Sent: Thursday, September 23, 2004 6:38 AM
Subject: RE: [cod] couldn't exec *.cfg


> If the server runs, just ignore it.  Those are pretty normal messages.
>
> John Kennington
> Assistant Director - Operations
> BuzzCard Center
> Georgia Institute of Technology
> 350 Ferst Dr. NW
> Houston Bookstore Mall
> Atlanta, GA  30332
> 404-385-2961
> 678-283-3385 Cell
> 404-894-2049 FAX
> http://www.buzzcard.gatech.edu/
> BuzzCard FAQs:  http://www.buzzcard.gatech.edu/faqs/index.htm
> -----Original Message-----
> From: Vye Wilson [mailto:gentoolover at gmail.com]
> Sent: Thursday, September 23, 2004 1:11 AM
> To: cod at icculus.org
> Subject: [cod] couldn't exec *.cfg
>
> when I startup the server it says:
>
> 53159 files in pk3 files
> execing default_mp.cfg
> couldn't exec language.cfg
> couldn't exec uoconfig_mp_server.cfg
> couldn't exec autoexec_mp.cfg
> Hunk_Clear: reset the hunk ok
> Opening IP socket: localhost:28960
>
>
> What can I do to fix the couldn't exec *.cfg files?
>