+ Responder Tópico
  1. #1
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Sep 2002
    Mensagens
    20
    Verdinhas
    0

    Server DOD/linux

    Alguém ja teve sucesso ao tentar montar um server dedicado de HL/DOD no linux.
    Ta dando uns erros podres e o tempo ta curto para correr atrás de faqs procurando explicações. Se alguém tiver uma 'receita de bolo' ou puder dar uma mão.





    .:[C4]:. Kraft (OwP) (Véio, para de mudar teu nick)
    .:[C4]:. Slayer
    .:[C4]:. BikerAD
    .:[C4]:. Slex
    .:[C4]:. LuckLike (OwP)

  2. # Publicidade
    Publicidade

  3. #2
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Dec 2001
    Mensagens
    2.666
    Verdinhas
    1

    Re: Server DOD/linux

    Originalmente enviada por LuckLike
    Alguém ja teve sucesso ao tentar montar um server dedicado de HL/DOD no linux.
    Ta dando uns erros podres e o tempo ta curto para correr atrás de faqs procurando explicações. Se alguém tiver uma 'receita de bolo' ou puder dar uma mão.

    qual o erro ?

  4. #3
    Membro
    Autor do tópico
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Sep 2002
    Mensagens
    20
    Verdinhas
    0

    es_invalid_addr

  5. #4
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Dec 2001
    Mensagens
    2.666
    Verdinhas
    1

    Originalmente enviada por LuckLike
    es_invalid_addr
    quando q acontece isso .. e como vc instalou

  6. #5
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Apr 2002
    Mensagens
    2.199
    Verdinhas
    0

    Re: Server DOD/linux

    Originalmente enviada por LuckLike
    Alguém ja teve sucesso ao tentar montar um server dedicado de HL/DOD no linux.
    Ta dando uns erros podres e o tempo ta curto para correr atrás de faqs procurando explicações. Se alguém tiver uma 'receita de bolo' ou puder dar uma mão.





    .:[C4]:. Kraft (OwP) (Véio, para de mudar teu nick)
    .:[C4]:. Slayer
    .:[C4]:. BikerAD
    .:[C4]:. Slex
    .:[C4]:. LuckLike (OwP)

    Mandrackinhu é o rei dos servers... ele monta servers até com as duas maos nas costas... d:-) digitando com o nariz d:-) ajuda Eles MandracKinhuu mauu ! d:-)))

  7. #6
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Dec 2001
    Mensagens
    2.666
    Verdinhas
    1

    Re: Re: Server DOD/linux

    Originalmente enviada por CHEVSKY



    Mandrackinhu é o rei dos servers... ele monta servers até com as duas maos nas costas... d:-) digitando com o nariz d:-) ajuda Eles MandracKinhuu mauu ! d:-)))
    eheheheh nem eh assim ;P

    mas linux/*nix eh minha house ...

  8. #7
    Membro
    Autor do tópico
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Sep 2002
    Mensagens
    20
    Verdinhas
    0

    Instalei da seguinte forma:

    baixei o hlds_l_3109_full.bin e o dod_v31_full.tar
    descompactei o primeiro no /usr/local/games/halflife/
    e o segundo no /usr/local/games/halflife/hlds_l/ (onde ele criou /dod)


    agora num sei se o comando ta certo (naum consegui muita documentação) mas o que acontece é o seguinte:

    [[email protected] hlds_l]# ./hlds_run dod
    Auto-restarting the server on crash
    Host_Init
    Added packfile /usr/local/games/halflife/hlds_l/valve/pak0.pak (985 files)
    Protocol version 46
    Exe version 3.1.1.0
    Exe build: 14:46:34 Jun 11 2002 (2056)
    Auth Server
    Server IP address 127.0.0.1:27015

    [[email protected] hlds_l]#



    dúvida: ta funcando e o IP do server é o 127.0.0.1:27015


    OBS: só que agora eu executei para pegar o erro e te passar e ele num deu mais o erro.
    Quero botar rodar na Net, pro pessoal do clan se encontrar.

  9. #8
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Aug 2002
    Mensagens
    610
    Verdinhas
    0

    q zica! kra, eu admito q não entendo porra nenhuma de server nem de linux... mas isso aki talvez ti ajude
    -----------------------------------------

    DOD Server Guide. The Basics.

    This article is targeted for people who are interested in getting started with DoD servers. This will cover the basics of server info, system requirements, and server setups. I have left out a great deal of technical information, simply because i am targeting people who are new at the whole process of getting started.
    This was written primarily by me, but Boogie gets the credit for the Linux info, and Kanikilu for the Links. [CosaN]Viper also contributed.

    Basic Information

    Setting up a server is fairly easy. Once you have the basic setup information down, and your server running, the true challenge of tweaking the variables begins.
    There are basically 2 ways to run a server. The easiest kind, a listenserver is created when a player uses the "create game" feature in the DoD GUI to make a server. With this kind of server, you can have all the functionality of a regular server, the diffrence being that it is only "temporary". When you disconnect, the server ceases to exist. Most settings for a listenserver can be set thru the in-game GUI, but it will also use any configuration you have set in the listenserver.cfg. a listenserver can be configured just like a regular server.
    The other type of server is a dedicated server. A dedicated server makes use of the Half Life Dedicated Server system to run a server without actually starting the game itself. A dedicated server will run faster than a listenserver, since it dedicates the computers resources to running the server, and doesnt use any to make the game itself. A dedicated server also has the added benefit of being "permanent", i.e it will be up all the time, whether you're in it or not. The only possible drawback is that running a dedicated server from your machine will generally make it impossible for you to play on the same machine. (it is possible, with some manipulation, but not recommended). A good dedicated server will also attract "regulars", thus allways providing targets for your fragging pleasure. I have made some very good friends over the years, from regulars on my servers.
    The following information will center on setting up a dedicated server. This information can also be used to set up a listenserver, simply by substituting "listenserver.cfg" in the place of "server.cfg"

    System Requirements

    What do i need to set up a basic server, you ask? Well, in theory, its very simple.

    Connection
    a good connection is the key to a good server. Since most things in-game, such as damage, death, respawns, etc are controlled by the server itself, and sent to the players (also refered to as clients), a server requires a large ammount of upload speed. Generally, a good server requires something like a T1 connection or better. Those of you who are interested in running servers from your cable/dsl connection... sorry to disapoint you, but generally, broadband connections do not have enough upload speed to support more than 8 - 10 players at best. (there will be more on this when we go into maxplayers). Your connection, in the end, will determine how many players you can have on your server, and what their pings will be like. Generally, the stronger your connection, the more people you can have, from a wider range. Hardware is also a factor in this, but you can have the fastest, strongest server machine in the world, and be hamstrung by a slow connection. A good connection will allow just about any hardware configuration. Most of the "Big Boys" like Recongamer, Griffin Run, ilan, etc operate off of no less than an T3 connection with massive bandwidth support. (btw, for those of you who say T1 connection? can i get that in my house?... the answer is yes, for @ $1000 US per month)
    A good tool for figuring bandwidth usage can be found Here (if you made this, please tell me, so i can credit you!)

    Computer Specs
    Half-Life was released in the late 1990s, when a "high end" system was in the general range of 500 - 600 MHz, and Windows98 was the "mainstream" operating system. Therefore, you can run a server off of just about any computer out there. I have even run a small server from a PII 350Mhz. However, as with everything else computer related... more is better. Half-Life Does support the Linux platform very well. Many talented individuals and groups have contributed to the HL/Linux product that exists today. As a result, the stability, performance and maintenance is, arguably, better than on a Windows box. Granted, this is dependant upon the person installing, admin’ing and maintaining the server. Minimum system requirements for a "Good" server are somewhere around:
    CPU: generally, anything around 800Mhz or higher. You can work with less, but slower PCs will affect things like maxplayers and pings.
    RAM: what can be said about RAM except get alot of it. 128MB at the least.
    Operating System: The best OS for running a server is probably Linux. Linux uses less resources and handles memory better. That does NOT mean you can't run a server from Windows. Windows 2000 is an excellent OS for running servers, as in WinNT. You can even run a server from Windows 98. Keep in mind, however, that the Windows OS's will generally dedicate more resources to running the system, thus pulling more from your server. The solution is to have lots of memory and proccessor available.
    As a general rule, I try to keep this in mind when setting up a server: On an uncapped connection, (i.e Bandwidth/connection speed is not an issue) an 800Mhz computer will support 20 - 24 players and use 128MB ram. That means if you only have 128MB of ram, you will have to drop your maxplayers since the system will use memory too.
    Software
    You do not need to have a licensed copy of Half-Life installed on your machine to run a server. HLDS is a free software package available from Valve, and the stand-alone server package can be downloaded from the Planet Half-Life Files Section. (you will not, however, be able to play from this.) Simply download it, run the installer, and specify your directory. You will need to install the latest version of DoD to this, as DoD is not natively packaged in the installer. The stand alone version is probably the best way to run a server. However, to simplify things, i will be tailoring everything after this to read as if the server was being set up under a normal player HL/DoD setup, for windows (i'll leave the linux setup stuff to the more experienced)


    Getting Started

    Windows Version

    OK, So you have an uber 1337 T3 connection, and a computer that kicks the bejesus out of anything on the market... so now you're ready to go!
    As stated before, A server runs from a program included in Half-Life called HLDS.exe. Now, before you go find it on your computer, and double click it to run, you will need to set a few things up. (simply running HLDS.exe will start a generic Half-Life Deathmatch server). To make this a DoD server, you will need to set up a shortcut. Go to your desktop, right click anywhere on the screen that doesnt have an icon, and select New/Shortcut from the menu that pops up. Point the shortcut to HLDS.exe, found in c:\sierra\half-life . For those of you using Counter-Strike retail, i believe the path is C:\Sierra\Cstrike (someone verify this for me and i will edit) Name the shortcut anything you want... Like "DoD Server" (immagine that)
    Find your new shortcut on the desktop and right click on it. In the "Target" line, you will need to specify what game to play, and some other important information. Here is an example of a basic DoD server shortcut:

    quote:
    --------------------------------------------------------------------------------
    C:\Sierra\Half-Life\hlds.exe -game dod +ip 205.247.175.149 -port 27015 -heapsize 512000 -noipx +maxplayers 22 +map dod_ramelle
    --------------------------------------------------------------------------------


    -game dod will cause HLDS to operate from the files found in your DoD directory.
    -port 27015[/port] this is somewhat unnecessary. This refers to the number after the : in a server IP. (ex 205.247.175.149[b]:27015. By default, all Halflife servers and players operate from port 27015. Some of you may have noticed that if you connect to a server that is on port 27015 thru the game console, you can simply type the IP without the port, and DoD will default to that port. You would change this number only if you needed to run off a diffrent port for security/firewall reasons, or you wanted to run more than one server from the same IP. (doing this will use more resources from your machine, so be sure you plan for it). You can also use the port feature to play on your server from the same machine. setting the server to -port 27016 will allow you to play from the HL default port of 27015, and connect to the server from 27016. Doing this will put massive strain on your systems resources, causing heavy lag in many cases, and is not recomended.
    -heapsize 512000 This specifies the ammount of RAM to dedicate to the server. generally, set this number to the ammount of RAM on your machine, and the server will try to use as much of it as possible.
    -noipx This tells the server not to use IPX protocols.
    +maxplayers 22 This sets the total number of players on your server
    +IP 205.247.175.149 This specifies your IP. unnecessary if you only have 1
    +map dod_ramelle This sets the map to start with. If you don't specify the map here, the server will default to the first map in the mapcycle, or may fail to start.
    Most of these variables (except -game dod) can be placed in a file called autoexec.cfg rather than the command line. The drawback to this is that if you play dod from the same machine, your autoexec.cfg will also run when you play, causing conflicts.

  10. #9
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Aug 2002
    Mensagens
    610
    Verdinhas
    0

    2ª parte

    Linux Version

    We are going to assume that the reader knows SQUAT about Linux or HL/DoD. So, this may be painfully obvious to most of you, but we were all noobies at some point. This is for their benefit. Please bear with me…

    I’m starting at a point just after the OS install. The major assumptions here are that we are using Red Hat Linux (works for any other flavor, though) and that you’ve never installed HL/DoD on this machine. OK, first, as root, you need to create the directory to install the HL server. Again, staying generic, let’s select /usr/local/. Copy your downloaded copy of hlds_l_3110_full.bin to that directory. Make the file executable and run the installer w/:

    chmod 500 hlds_l_3110_full.bin && hlds_l_3110_full.bin

    The auto extractor will ask you to comply w/ the license. Type ‘yes’.

    Next, you can unzip and decompress the tarball in one command:

    tar –vxzf hlds_l_3110_full.bin

    Now you have a new directory filled with the joy that is Half Life dedicated server! Settle down Sparky, we’ve got a way to go yet.
    DoD is the next on the menu. Copy the file, dod_v21_full.tar.gz, to the hlds_l directory and unzip like above:

    tar –vxzf dod_v21_full.tar.gz

    About access rights
    I have serious reservations making any specific recommendations about access rights. Each system is unique and the decision falls on the shoulders of the owner/admin. I have found several threads discussing the potential security issues surrounding the execution of HL server as Root. The bottom line? Don’t do it. Change the access rights to the hlds_l directory to allow execution by local users (anyone other than root). That can be done by running the command from the prior directory /usr/local/.

    cd /usr/local/
    chmod 755 –R hlds_l/
    THIS SETTING MAY NOT BE RIGHT FOR YOU!! Please determine the best access rights for your application and adjust accordingly.

    Common Steps
    The next step is to set up all the server related files found in your dod directory.

    motd.txt This is the message of the day file that you players see when they first get in the server... put whatever you want in it.
    mapcycle.txt This is the map rotation for your server... maps will change in this order, depending on your timelimit.
    server.cfg This is the big one.this controls all the variables in your server. When you install DoD, a basic server.cfg is included in the install. Here is what all the stuff means:

    hostname "My Server" //This is what you call your server. This is the name that will appear in the server lists.
    //sv_password "yourpasshere" //This is the server's password. If you want people to have a password to connect to your server, uncomment this line (remove the //) and pick a password
    //sv_spectator_password "yourpasshere" //This is how you would password protect spectators.
    rcon_password "yourpasshere" //You MUST set this variable if you want any control over your server. you can change any variable on the server from in-game if you have this set. more on use below
    mp_autocrosshair 0 //sets whether to use the DoD crosshairs, or the HL ones. leave at 0
    mp_flashlight 1 //Toggles use of flashlights. setting to 0 will not allow flashlights
    //mp_teamplay 11 //This controls things like falling damage, etc. more on this can be found here As a general rule, leave this commented out, until you know what you are doing
    mp_friendlyfire 0 //Turns off and on friendly fire 1=on 0=off
    mp_fraglimit 0 //changes the map when a certain number of frags has been reached. if you set this to 100, the map will change as soon as someone gets 100 points
    mp_teamlimit 2 // The number of ‘extra’ players a team will be allowed. (Uneven teams) Default of 0.
    mp_timelimit 45 //amount of time in minutes to play the map
    mp_allowspectators 1 //1= allow people to spectate 0=no spectators. This must be set to 1 if you plan on using HLTV
    sv_minrate 0 //See below for more on this
    sv_maxrate 6500 //See below for more on this
    sv_allowdownload 0 //Will allow/prevent people from downloading maps and such from your server. If you are playing a custom map, and someone connecting doesnt have it, if this is set to 1, they will be able to download it directly. set to 0 if lag becomes a problem
    sv_allowupload 1 //allow/prevent players from using custom logos
    sv_cheats 0 //No, this isn't allow/prevent h4x.. this is the HL cheats, like noclip, and impulse 101.
    sv_maxspectators 4 //Maximum number of spectators allowed
    decalfrequency 30 //time in seconds before you can spray your logo again
    log on //this logs all events happening on your server. Stats programs need this set to on. Logs can be found in \dod\logs
    fakelag 0 //setting this above 0 will add ping to your players... a player who pings your server at 50, if you add fakelag 50, will cause that player to ping at 100. If you do this, you are cruel.
    fakeloss 0 //similar to fakelag... simulates packet loss... again, only for the unusually cruel
    pausable 0 //allows/prevents players from pausing your server. if set to 1, every jerk with an attitude can pause the game for everyone
    sv_accelerate 10 //number in seconds it takes a player to go from stop to full speed
    sv_aim 0 //This toggles the use of HL's "auto aiming" system. if a player has autoaim set to 1, the game will provide some help with shooting. This is not a cheat, merely a way of helping n00bs out. it doesnt help very much
    sv_airaccelerate 10 //This affects what air does to a person. setting lower makes air "thick" and hard to move in, and higher makes people move like superman thru the air
    sv_airmove 1 //this controls whether the player can turn and look etc while in midair
    sv_friction 4 //another movement setting
    sv_gravity 800 //standard gravity is 800. set to 100 or so for low grav fun!
    sv_bounce 1 //more of an HL feature, this controls those bouncepad thingys in HL
    sv_clienttrace 3.5 //this controls "hitablity" dont mess with it, or you will deal with all kinds of "hes haxing" stuff
    sv_clipmode 0 //controls wether players can block stuff. if you have a problem with "door blockers", set this to 1, and people can just walk thru them.
    sv_stepsize 18 //controls what angles are climbable. if this is set high, players would be able to walk up walls
    sv_stopspeed 100 //how long it takes you to go from full speed to stop after you let go of the movement key
    sv_maxspeed 500 //controls how fast people move. setting higher or lower affects speed. 650 is @ average
    sv_wateraccelerate 10 //same as accelerate, but in water
    sv_waterfriction 1 //same as friction but with water
    edgefriction 2 //sets friction against solid objects
    mp_falldamage 1 //turn off/on fall damage. off means players wont die when falling from too high
    mp_footsteps 1 //turns on and off footstep sounds
    sv_unlag 1 //definitely leave this set to 1...it is the toggle for the netcode. set to 0 if you run lan only
    traceroffset 100 //
    tracerlength 0.45 //
    tracerred 1.3 //
    tracerblue 0.1 //These are all tracer settings. Just leave them be..LOL
    tracergreen 0.7 //
    traceralpha 0.45 //
    tracerspeed 6250 //
    mp_bulletwhizz 0 //turn on/off the whiz sound for bullets. could help with lag
    mp_deathmsg 1 // Kill icons/messages in top right corner of screen. (1 = yes, 0 = no)
    mp_chatmsg 1 //Allow standard HL chat messsages. (1 = yes, 2 = no)
    mp_dod_showcutscenes 1 //1 will show cutscenes on a server. 0 will never show cutscenes.
    mp_pararoundtime 120 //sets the round time between spawns with the para system. (thanks, [CosaN]Viper)
    //DoD Clan Settings
    mp_clan_match 1 //Turns on the clan system.Once done, several other variables can be used to tweak the clan round system:
    mp_clan_timer 20 // This sets the number of seconds to start a clan match. When the mp_clan_restartround setting is envoked, it will rely on this timer. A message will come up with the countdown so that everyone in the server has time to prepare. At the end of this time, the round will reset, the map will reset, and the player scores will reset.
    mp_clan_voice 1 // A setting of 1 will allow clan members to use the HL voice system anywhere on the map. A setting of 0 will use the standard DoD voice system based on distance.
    mp_clan_respawntime 10 // This is the classic DoD respawn timer variable. Not available anymore in standard multiplayer matches – this will allow clan’s to use the ‘old’ system if they wish.
    mp_clan_showcutscenes 1 // If mp_clan_match is on, then this setting will become available. It will allow clans to turn cutscenes on and off.
    exec banned.cfg //loads the ban list, so people you banned stay banned


    SV_MINRATE / SV_MAXRATE
    These are probably the single most important variables in your whole server. This controls the rates that your clients gather information from the server. you can play with these to tailor your server to specific clients. if you have a large number of bandwidth hogging broadband users, sv_maxrate will only allow them to download at a specific rate. 5500 - 6500 is recomended.. setting this too high or leaving it out all together will cause people to use all the bandwidth available to them. the first effect of this will be to cause lower speed connections lag. a large number of bandwidth hogs will take up ALL of your bandwidth, and lag everyone. sv_maxrate 6500 is more than adequate to make everyone happy
    sv_minrate has the opposite effect. setting this above zero causes

  11. #10
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Aug 2002
    Mensagens
    610
    Verdinhas
    0

    people with slower connections to get server info at the specified rate... example would be a 56ker who connects with a rate of 1000 or so..to a server set to sv_minrate 2000.. would force the player to be bombarded with server info, causing him to lag horribly
    playing with these variables can tailor your server for what you want. if you want to play with lpb's only, set a higher minrate. if you want to allow broadband and 56k to exist in harmony, leave the minrate low, and set a higher maxrate. If you only want 56k'ers, set the maxrate very low. if you want to conserve bandwidth, set the maxrate to an acceptable level
    It is a common misconception to say that 56ker lag a server. setting these rates properly will allow all users to use your bandwidth appropriately.

    That is the basic server configuration. When you have your connection set up, your PC up and running, and your files all set and ready, you are ready to start the server!

    Starting The Server

    When you are ready, double click the shortcut you made, and if all is set up right, a DOS window will open and your server will start loading.

    you will need to look for a few things:
    make sure the first few lines reflect the proper protocol and .exe versions (the current release of Half-Life)
    make sure you see the "won auth server". This means the server successfully connected to the WON servers and will show up in the server lists. If you don't get this, or it just says WON server... than you either have an older version of half-life, or something else is wrong
    you will then see the pak0.pak load, and the map as well. then you will see 3 lines stating that your server was added to the won master server list. your server is ready to play on!


    Using rcon

    when you get on your server, you will, at some point, want to change things about it. you will also want your friends to have this ability, and, while you can change any of the above variables right from the server console itself, simply by typing new ones in (ie sv_password xxx ), you may not allways be able to get to the console, so you will need to do it remotely.
    you accomplish this by entering the rcon password like so:
    rcon_password xxxxx
    please note, if you run your server from any port besides 27015, you will need to enter:
    rcon_port xxxxx
    rcon_password xxxxx
    once you enter your rcon password, you should not have to do it again, as long as you stay connected.
    you can place these in a cfg file and execute from console if it suits you.

    to change variables on the server, simply type rcon variable. for example, to turn friendlyfire on, you would enter your rcon password as above, and type in console:
    rcon mp_friendlyfire 1
    now you can TK all your friends.

    some other things you can do with rcon:
    rcon say //speaks from the server console...
    rcon changelevel mapname //changes the map
    rcon users //lists players on the server
    rcon kick #
    rcon banid time userid
    rcon mp_clan_match 1 // starts the clan system
    rcon mp_clan_retstartround 1 // this will start the timer to restart the round.

    for kicking and banning, you will need to know a player is identified by the server. The server assigns each player a "userid" (a number generated by the server) and a "wonid" that is unique to every cd key. To find these id's for a player, type "users" into the console. you will see something like:
    userid : uniqueid: name
    1 123456789 JoeBlow
    2 1248879 ZippyDaChimp

    the userid is the server generated number, and the uniqueid is the wonid
    to kick JoeBlow from the server, you would simply type:
    rcon kick # 1 (use the #) and joeblow will be greeted by his console screen.
    to ban someone, the process is slightly more involved. since the userids and names can change, you will need to ban either by wonid, or IP. wonid is your best bet, because IPs can be faked fairly easy, it costs 30 bucks for a new cd key
    to ban by wonid, type:
    rcon banid 30 123456789
    this will ban JoeBlow from the server for 30 minutes. setting the number to 0 = a permanent ban
    you will then have to make sure he stays banned thru map changes. to do this, type
    rcon writeid
    this will put his ID in banned.cfg, and will be reloaded every time the map changes.
    to ban by IP is a bit more complex:
    type "rcon status" in console... this will list players with IPs as well as wonid
    then you simply type:
    rcon banip 30 xxx.xxx.xxx.xxx
    rcon writeip

    I am not going to spend much time on the ethics of kicking and banning. Please be responsible with it. There is nothing worse in this game than people who are powertrippy admins who kick because they can, or because you play better or diffrently than they do. remember that if you want people to come back to your server, you need to treat them with respect.

    Other Stuffby Kanikilu
    I allways recomend that people get a server restart tool. sometimes, servers crash for no reason, or will crash on a bad map, or some jerk crashes them. I use ServerDoc. If my server crashes, it automatically restarts without my even having to be in the building. Linux servers have a restarter built in.


    STATS

    -Psychostats (http://www.psychostats.com) -- I've used this for almost a year now, and doubt I will ever switch. It's written in Perl, and can run on your Linux or Win32 server. It has several pre-packaged "themes" including one for DoD. It uses a set of configurations files that are fairly easy to use and get used to. Depending on how many logs you need to go through, this can take a few minutes, and can severely eat up the resources of the machine while it's running. So, while there is no problem on my part-time server...it may not be perfectly suited for everyone (although there are a few different "products" offered at psychostats.com, and one may fit your needs).

    -HLstats (http://www.hlstats.org) -- Some people swear by this, and it's log parsing does seem somewhat more efficient (I don't think it goes through all the logs *every* time like Psychostats does). I, however, have never used it...so...can't offer much in terms of a recommendation.

    REMOTE MONITORING

    -HLSW (http://www.hlsw.net) -- In my opinion, the end all, be all of remote monitoring. There are other products around, but if you are monitoring from a Win32 machine...I can't see you needing anything more than this.

    -Halfd (http://www.halfd.org) -- This is a multi-purpose tool, and a must (so I'm told) for Linux admins, but does include a remote monitoring capability.

    SERVER MANAGEMENT/ADMINNING

    -Metamod (http://www.metamod.org) -- Just about everything in this section is built upon Metamod...it is a must for any serious admin, IMO. Check out the webpage for the list of available plugins.

    -Adminmod (http://www.adminmod.org) -- This is a Metamod plugin, and with what is already built into it, as well as available plugins, it provides functionality for just about anything you can think of...again, a must in my opinion and experience.

    -LogD (http://logd.sourceforge.net) -- This is also a Metamod plugin, and has some nice plugins available to it...the only reason I use it, is for the TK management plugins (of which there are several to choose from). This is not a "must", but is certainly helpful if your server is going to have full or even partial (grenade) FF on.

    -Halfd -- See above.

    -ClanMod (http://http://www.unitedadmins.com/ClanMod.aspx) -- This is a product similar in functionality to Adminmod, with some clan-specific needs built in. I have never use this...so...if you have questions, I'm sure their website and forums should be able to help you out -- not to mention I'm sure there are some people here with some experience with it.

    -FireDaemon (http://www.firedaemon.com/) -- If you run your server on WinNT/2K/XP, you can use this to make your DoD server a Service (where you can also tell it to restart it if it crashes).

    MISC. TOOLS
    ...in here I'll put links and descriptions to tools that I've often been asked about...

    -Ever been on a server where you point at a player and their name and health comes up in nice pretty letters (instead of HL default)? That is a Metamod plugin, written by Jussi Kivilinna called playername_mm. His page is at http://hullu.xtragaming.com/

    -Heard people referring to a "ping-booster"? The original (LINUX ONLY) program is by Udpsoft (http://www.udpsoft.com/booster/). Since then, Jussi Kivilinna has written a ping-booster Metamod plugin, and his includes support for both Win32 and Linux servers. His website is at http://hullu.xtragaming.com/

    -HLGuard (formerly CSGuard) is now maintained by UA (http://www.unitedadmins.com). Visit their website for forums, downloads and more.
    -Cheating-Death (http://www.cheating-death.com) is also a great cheat detection tool.
    I also recommend playing with all the variables, maxplayers, connection variables, and everything your server uses. The more work you put into a server, the smoother it will run.

    Remember, Admin’ing isn’t just a job, it’s an adventure!

  12. #11
    Membro
    Info Conteúdo e Citações Jogos Mensageiros
    Registro
    Jul 2002
    Mensagens
    2.081
    Verdinhas
    0

    calma ai ....q ja to lendu !!! huauauha ..meu ....linux deve c um traste

+ Responder Tópico Ir para o Fórum

Assuntos do tópico

Compartilhar

Permissões