Mojo (DayZ)

No, it's not. It's the root of a completely separate problem that has nothing to do with this thread other than being mentioned as a problem rocket was having that was causing him as much frustration as server hosts were experiencing due to problems unrelated to that which are coincidentally what the thread is actually dealing with.

As far as this goes from my end' date=' and perhaps rocket can confirm this, but the (in-game) time is a variable in the DayZ code (something like _time or _date) that, after the local server (ie: the one you actually play on) successfully handshakes and authenticates with the parent server (ie: the one that saves all your data), culls the local time from the local server system (using jaynus' library, aka jayarma2lib or jayarma2lib_new if you're using the beta) and sets that as the time. From this -- again please don't break everything based on my guesswork until somebody confirms this -- logic would dictate that so long as the master server doesn't have any expectations for what the local time should be (and it shouldn't, since the Arma series is known for introducing time dilation effects when server frames drop), then the following would hold to be true: 1. Altering the in-game mission time by altering the external time it culls itself from is SAFE AND SANITARY. That is to say, if you want to play at noon when it's midnight, go into your actual Windows 2008 R2 server and set Windows system time to noon. 2. Altering the in-game mission time by altering the mission file itself is UNSAFE AND UNSANITYARY AND BREAKS FUCKING EVERYTHING AND DO NOT DO IT. ***Again [b']disclaimer this is entirely guesswork on my part I am not staff or a dev etc and so forth.

They likely aren't trying to deliberately abuse it. There's a correct way to do what rocket's talking about that is utterly transparent and an incorrect way to do it that a lot of semi-experienced or experienced ArmA2 hosters might be familiar with' date=' but who have never had to deal with a back-end that relies on a hook and an off-site SQL server. The way they're doing it, and this is cobbled together entirely from deductive guess-work from simply knowing that the method they're using writes corrupted data to the SQL server, desanitizes the code in ways that if I had to (again) guess is [i']at minimum altering the offsets.

Goons being goons. We're either the scum of the Earth or the salt of it. For what it's worth, we discovered a dupe glitch on our server. We took steps to reproduce it (to ensure it wasn't a fluke), verified the methodology, and then I promptly emailed the dev team, and let everybody that helped verify it (it requires multiple people) know that if I ever found them using it, they would be banned without hesitation or possibility of appeal: (Methodology blacked out for obvious reasons) Responsible goons, irresponsible goons. We aren't all shit, I swear. An alpha is there to discover, isolate, reproduce and report. It is not there to exploit.

*DING DING DING DING DING DING DING* ArmA 2 Memory Leak. It's been a persistent problem since ArmA 1, and continues right into OA. Couple that with the fact that the missions (and the virtual machine that execute the scripts) have absolutely no native garbage collection whatsoever, that the virtual machine has really odd inheritance redundancies, etc., and what you get is serious memory bloating. Your post title really says it all: Out of memory, just a matter of time.

As much as that may be true' date=' Legacy, it seems that this server application is being forced on administrators such as myself (& Owl) and cm. (& Freeborne) who do know how to use FireDaemon, who [i']want to use FireDaemon, and who have already paid for FireDaemon. I don't have a problem with an alternative to FireDaemon, because choice is good. I have a problem with a replacement for FireDaemon. Because choice is good. I tried that and it didn't seem to work' date=' it showed all of the processes as "Running" even though they were clearly shut down [/quote'] What you were most likely doing was attempting to run the batch files as the service. The batch files launch the server in Session 0 (the services session) so that adds another layer. When you were shutting down the services, you were shutting down the batch file. The server the batch file launched, on the other hand, kept right on running. Here's the right way to set up FireDaemon:

Dear God, this right here. I don't mind an auto-updater -- in fact Owl offered to code a deployment system with delta patching two weeks ago and received no reply -- but I want to control the server we pay for out of our pockets the way I want to control it. I want to set core and thread masks how I want to set them. I want to load balance how I want to load balance. I want to monitor how I want to monitor. I want trusted moderators to have the ability to restart the server without needing RDP access. I'm not going to lie, hearing rumours of this server monitor honestly makes me consider pulling the plug.

After some frustration we have finally gotten Chicago 1 up and running nicely, after going through the person doing all the work on Arma on our server (me) going through the service subscriber (Owl) to the dev (rocket). Telephone is a fun game to play when working with Win Server 2008! After a brief hiccup where RCon decided that connecting to the server meant crashing the server, we got it up and running nice and stable. If all goes well, we're considering setting more servers. We're a couple of laid back guys, if you can't tell by the idiotic name of our server: Yevgeny's Unexpected Pregnancy. It's a nice box though, eight cores, eight gigs of RAM, and a good, solidly reliable connection. That said, if any of you guys encounter hiccups, persistent desync, anything like that, please, please send me a PM here on the forums -- we're going to fine tune this server until its running at the best possible performance for you. We were able to welcome many new players to our servers tonight, with quite a few of you guys making your first character with us. Nice. Enjoy DayZ, guys. Soon it will be you griping about the desync as fifty people try to make new accounts after navigating the hazards of setting up Arma 2 Combined Ops. We chose Chicago as a nice, central location for all players in North America, so that we can give an equitable play experience to the entire player base. DONATIONS! DONATIONS! I'm surprised at actually making this section, but quite a few players expressed interest in offering us donations, which we truly do appreciate (it would also incentivize us to get a second central server up quicker). That said, Owl's the poor bugger that actually gets charged for this stuff, so I've cajoled the donation link out of him. Here it is: Donations! With that out of the way, let's go over a few of the rules that will get you removed: 1. Spamming VON, especially with music. I like Peter Gabriel as much as the next guy. What I don't like is trying to listen to Solsbury Hill over my grandmother's rotary phone while her bichon frise repeatedly runs into her record player, causing it to skip over and over. Other things I don't like hearing in the background: Your dog barking. Your wife or girlfriend asking if you're playing "that zombie thing" with "your little friends". Every cough or breath you take -- keep it up, asthma guy, and you won't be picked for DayZ any more than you're picked for kickball. 2a. Blatant racism/sexism/homophobia/other, more esoteric forms of discrimination. We do not pay server bills so we can act like your Kleagle uncle's basement. Please keep any fantasies involving nooses or dragging people behind pick-up trucks to your own warped little head. 2b. As a nice segue, pedestrian racism. Just because you're not trying to recruit for the KKK doesn't mean anybody wants to hear your random musings on how America could elect a black man. (There's only one thing .)3. Blatant cheating. Really, I shouldn't need to say this, but some tit is going to appeal a ban sooner or later saying "but I didn't know it was against the server rules to send spoofed key files to the server to inject malicious PBO controls into my game." But it is against the rules. 4. Gaming the system. Did you just disconnect from the server after getting attacked to try to reposition yourself? Guess what's going to happen when you try to reconnect to the server. 5. Acting 2kool4skool. Persistent whining and childish behaviour angers me. I'm old and curmudgeonly and my life is fading before my eyes as I cry myself to sleep every night in a pool of my own tears and failure. One thing I don't have time for, especially when trying to enjoy myself as some sort of marauding anti-hero of the apocalypse in a fantasy world I've wholly embraced to soothe my tattered dreams, is your shit. If you're going to act like you're at an age where you need a time-out, you're going to get a time-out. We all get frustrated. We all smack talk. More importantly, we all know when to stop. 6. Absurdly high pings over a long period of time. Latency spikes happen, and we know that. You'll be asked politely to make sure your network is relatively clear of 50 torrent files running in the background. Please take the time to actually ask your girlfriend if she really, really needs all the episodes with Vampire Bill talking in a rough, gravelly voice tonight, or if she can wait until you're done playing that zombie thing with your little friends. If we can all agree that everybody much prefers playing on servers without rampant dehumanization of your fellow man, other players, etc., then you're welcome to join us. If you can't follow those rules, well, I feel sorry for you. Most of these are no brainers, and the ones that seem a little unfair -- like high pings or getting a little hot-blooded -- don't carry anywhere near the gravity of, say, making me reboot my server. That stuff's just to get your attention. Things we don't care about and would sincerely appreciate you not caring about, or out least not caring about out loud, to us: 1. PvP/PK'ing. It's there, it's in the game, and it's a fundamental mechanic. 2. People swearing, using profanity, or using obscenities. You're playing a game based around shooting people in the face. Priorities! 3. That thing where the person ArmA 2 decides to designate as the group leader that causes him to repeatedly order others back into formation. The person doing it has no control over it, and it's a side effect of ArmA 2's grouping system. Please be aware of the fact that the player that appears to be issuing these orders has no more control over it than you, and we will not penalize other players for this. Lastly, please take the time to be helpful towards your fellow players. For example, don't just spam STFU! in response to VON spam. Explain to them why it's happening, and what they can do to fix it. A player isn't a problem player until they know they're causing a problem and persist in doing it anyway. I'd much rather have the newbie that listens attentively to how he can make a small effort to make the other 49 people's play experience better, than ten pro-skillz players who act entitled without first considering how they can help solve the problem. It usually takes just as long to type out useful advice as it does to scream at a person. Only one of those will actually solve anything.

Ok, but still, do you have any evidence that Person X is the guy on the Darwin List? What you're doing is like saying "My next door neighbour, Bob Smith, is a Nazi war criminal. He's had plastic surgery done, has a different name, but he's totally Amon Goeth!" And then somebody goes, "do you have proof that Bob Smith is Amon Goeth?" And then you go, "lol read a history book retard." You have given us an email -- to what? A forum account, here? -- and assured us that this email (in some vague way) links to a cheater. You rely on evidence that the cheater is a cheater -- a tautology -- and claim that that proves that this person is that cheater. What, exactly, would you like people to do with this email account? Ban the forum account I can only assume it's registered under, but whose name you won't supply? That's fair enough, I suppose, but you don't need an email account to play Combined Ops or any of its mods, including DayZ, and even then you've only gone on to say that so-and-so made a new account with this email without a shred of proof that that email is the person you allege it to be. I mean I realize I'm repeating myself here but the problem with your claim isn't that it's necessarily false, it's that you make it in such a bizarre, hectoring manner that I don't even 0892q509u5ij3qwk6j43u6 fuck it I give up trying to explain what you need to do, it seems obvious to me and everybody else here.

Wasn't going to reply beyond marveling at the slapfight but I gotta say, I 100% ban for ghosting too. Don't have an open TeamSpeak? Sorry hoss, but the rules to my TeamSpeak are posted in multiple locations, including the TeamSpeak server itself. One of those rules is no ghosting. The server is hosted on a physical machine, making it chattel property, and provided as a service, making it subject to terms of service. Both of those alone are sufficient for any person charged with administrating that server to invoke the principle of informed consent: By connecting to the server, you agree to the terms of service for the service provided and to occupy a connection to chattel property, be it leased or owned. One of the conditions of informed consent is that you know, or reasonably ought to know, the consequences for violating either principle of the overarching agreement. If you do not agree with that agreement, you may leave. Private property is not a public square and you do not have the right to civil disobedience in my private property. Put more briefly: Fuck around, get banned.

As fun as it might be to actually have somebody with a ridiculous amount of RAM and then set them up with a ram disk, unless you know how to off the hop, I'd recommend not bothering. Go out and get a solid SSD or stripe a couple of 10,000 RPM mag drives. Either of those options is going to be cheaper than a new GPU or even the stupid amount of RAM (and the motherboard needed to support it) to set up a ram disk.

Eh, it's basically middle of the road stuff. nVidia GPU chip, 460 series OC'd, 8gb RAM, 1x phys 4x logical AMD that's stock 3.41 but pushing something or other right now, with a 240 gig Sata 2 SSD with a SandForce controller. Stock air cooling kept in check with regular cleaning.