[bf1942] How to test high ping kicker is working

"Einar S. Idsø" esi at itk.ntnu.no
Mon Jun 27 07:16:49 EDT 2005


Sorry, those were not very good instructions... The file itself should
be pointed to, not a dir. The dir has to exist and have the correct
permissions so that the user which owns the bf2 serverprocess can make a
file in there.
bfno.debugLogFile "/path/to/logfile.log"

Einar

Einar S. Idsø wrote:
> The location of the logfile is specified in adminsettings.con:
> bfno.debugLogFile "/path/to/logfile/"
> 
> Make sure it exists and has the right permissions.
> 
> Einar
> 
> 
> Andrew Armstrong wrote:
> 
>>Where would this log file be? Im still not seeing it, after reverting all
>>ping kicker and noadmin script back to their originals.
>>
>>Guess ill have to look at it again tomorrow, wish stuff would just work
>>without making me want to shoot it :)
>>
>>- Plasma
>>
>>----- Original Message -----
>>From: "Einar S. Idsø" <esi at itk.ntnu.no>
>>To: <bf1942 at icculus.org>
>>Sent: Monday, June 27, 2005 8:10 PM
>>Subject: Re: [bf1942] How to test high ping kicker is working
>>
>>
>>
>>
>>>Yes, put bfno.py right next to default.py in the admin directory in the
>>>main server install dir. The code in bfno.py will use the argument you
>>>provide with +maplist to determine where it should look for
>>>adminsettings.con.
>>>
>>>In serversettings.con:
>>>sv.adminScript "bfno"
>>>
>>>Einar
>>>
>>>Andrew Armstrong wrote:
>>>
>>>
>>>>So with the layout given below (settings/[port]/serversettings.con /
>>>>adminsettings / maplist)
>>>>Where is the bfno python script placed? still in /admin/bfno.py ?
>>>>
>>>>Do you then still have in the server config, 'adminscript' as 'bfno', or
>>>>'settings/[port]/bfno.py'?
>>>>
>>>>
>>>>----- Original Message -----
>>>>From: "Einar S. Idsø" <esi at itk.ntnu.no>
>>>>To: <bf1942 at icculus.org>
>>>>Sent: Monday, June 27, 2005 7:16 PM
>>>>Subject: Re: [bf1942] How to test high ping kicker is working
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Agreed, and that is exactly what it does :)
>>>>>
>>>>>./start.sh +config /path/to/serversettings.con +mapList
>>>>
>>>>/path/to/maplist.con
>>>>
>>>>
>>>>
>>>>>adminsettings.con is assumed to be located in the same dir as
>>
>>maplist.con.
>>
>>
>>>>>Einar
>>>>>
>>>>>Paul Bowsher wrote:
>>>>>
>>>>>
>>>>>
>>>>>>much better is to have:
>>>>>>settings/16567/seversettings.con, adminsettings.con, maplist.con
>>>>>>settings/16667/seversettings.con, adminsettings.con, maplist.con
>>>>>>
>>>>>>etc.
>>>>
>>>>
>>>>
>>
> 
> 



More information about the Bf1942 mailing list