headers
Hal & Arlene | 1 Sep 2006 05:07
Picon

client being quit to desktop

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I am a server admin, I am constantly having people adding me to there
friends list, until now I have thought it rude to block, or refuse them.  I
have a player who is a bit disruptive, during gaming sessions, but
manageable. He IM's me in friends and says "wanna see something cool", and
proceeds to shut my game down to the desktop.  I knew an admin could do
this, while you were connected to the server the admin was managing, and he
had appropriate permissions.  I did not know it could be done through a
friend's connection, when he did it I was not connected to a server, just
friends.

We have been having people being crashed to the desktop, during game play.
I had first thought it was an errant error in a configuration file, but now
I am starting to suspect foul play, because most of the people that were
being crashed have that player in their friends list.  The question then, is
there a way to block this, or is my only option to tell the regulars to turn
off friends.  Removing him from friends is easy enough to do, but it would
be a simple matter for him to come in under a new name, and/or id.  The
first best choice is to block this ability to quit a client to the desktop.

I am new to this thread; feel free to educate me on structure, format, or
verbosity

--
Permalink | Reply | 3 comments |
headers
Matt Albiniak | 1 Sep 2006 05:17
Picon

Re: client being quit to desktop

The only time I've seen clients quit to the desktop were:

1) forcing a cexec with mani to cause the user to quit (dunno if other
mods have this "feature").
2) running zBlock/Cvar-x (or whatever its called) with mani and
redirects enabled. users who are redirected crash because the var
blockers prohibit the wait; command mani uses on redirects.

There have to be other ways, but not knowing your cfg, mods, etc makes
it a long list of guessing.

On 8/31/06, Hal & Arlene <linc3 <at> comcast.net> wrote:
> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> I am a server admin, I am constantly having people adding me to there
> friends list, until now I have thought it rude to block, or refuse them.  I
> have a player who is a bit disruptive, during gaming sessions, but
> manageable. He IM's me in friends and says "wanna see something cool", and
> proceeds to shut my game down to the desktop.  I knew an admin could do
> this, while you were connected to the server the admin was managing, and he
> had appropriate permissions.  I did not know it could be done through a
> friend's connection, when he did it I was not connected to a server, just
> friends.
>
>
>
> We have been having people being crashed to the desktop, during game play.
> I had first thought it was an errant error in a configuration file, but now
> I am starting to suspect foul play, because most of the people that were
(Continue reading)

Permalink | Reply | 2 comments |
headers
ValeX Valex | 1 Sep 2006 07:05
Picon
Favicon

Redirecting clients.

Hey guys. Some of you may have encountered one of those game servers, where
you attempt to join it, but it's full so it redirects you to a secondary
server set up by the same people. I would like to do this, using 2 different
servers on different parts of the continent. How do I do it? If we can't
trigger it to forward clients only when the first server is full, how about
sending clients to alternating servers, one here, one there, type deal.

Help?

ValeX

_________________________________________________________________
Click here to pick out the perfect PC for work or play
http://shopping.sympatico.msn.ca/content/shp/?ctId=507,ptnrid=176,ptnrdata=081802
Permalink | Reply | 1 comment |
headers
Radar DA-UK | 1 Sep 2006 07:19
Picon

Re: Redirecting clients.

I think its only Manimod that can do thins.

http://www.mani-admin-plugin.com/

mani_reserve_slots_redirect "***.***.***.***:27015"

Radar....

----- Original Message -----
From: "ValeX Valex" <h2_valex <at> hotmail.com>
To: <hlds_linux <at> list.valvesoftware.com>
Sent: Friday, September 01, 2006 6:05 AM
Subject: [hlds_linux] Redirecting clients.

> Hey guys. Some of you may have encountered one of those game servers,
> where
> you attempt to join it, but it's full so it redirects you to a secondary
> server set up by the same people. I would like to do this, using 2
> different
> servers on different parts of the continent. How do I do it? If we can't
> trigger it to forward clients only when the first server is full, how
> about
> sending clients to alternating servers, one here, one there, type deal.
>
> Help?
>
> ValeX
>
> _________________________________________________________________
> Click here to pick out the perfect PC for work or play
(Continue reading)

Permalink | Reply | 0 comments |
headers
Regime | 1 Sep 2006 11:18

Re: client being quit to desktop

There has been a report made on this list at some point, saying that it
was possible for someone to send a message through steam friends of a
certain length (very long probably) that has this effect. I have no idea
how and if this (still) works though. Never tried it.
So yea.. Turning it off, or blocking the person crashing your game seems
the obvious and only solutions for now.
---
Regime

Matt Albiniak wrote:
> The only time I've seen clients quit to the desktop were:
>
> 1) forcing a cexec with mani to cause the user to quit (dunno if other
> mods have this "feature").
> 2) running zBlock/Cvar-x (or whatever its called) with mani and
> redirects enabled. users who are redirected crash because the var
> blockers prohibit the wait; command mani uses on redirects.
>
> There have to be other ways, but not knowing your cfg, mods, etc makes
> it a long list of guessing.
>
> On 8/31/06, Hal & Arlene <linc3 <at> comcast.net> wrote:
>> This is a multi-part message in MIME format.
>> --
>> [ Picked text/plain from multipart/alternative ]
>> I am a server admin, I am constantly having people adding me to there
>> friends list, until now I have thought it rude to block, or refuse
>> them.  I
>> have a player who is a bit disruptive, during gaming sessions, but
>> manageable. He IM's me in friends and says "wanna see something
(Continue reading)

Permalink | Reply | 1 comment |
headers
fishy | 1 Sep 2006 11:18
Picon

Re: hlds crashes

Suns grid software. Is there a seperate server image to be run on each
node? or does it share the images and deliver them to whichever node
requires them, as such perhaps running the same image on different nodes
with different ips or hardware ids could be causing the glitch, it is
likely that there is some unique identifier contained in the
clientregistry.blob.

hows about a dirty hack to get it working temporarily?
add a line to your server initiating script to remove
clientregistry.blob before the server starts ;).

As to server crashes, bad maps and plugins often cause hlds to crash
unexpectedly and i have not run into any issues when restarting the
server, either scripted or manually, however i have no experience
running the same server image on different boxes.

Jonathan wrote:
> AFAIK they are all clean halflife installations with only cs running (this
> is not hl2 with cs source)
>
> The strange thing is that it all works fine for a few times if i delete
> the clientregistry.blob file, but then after a while the crashes start
> appearing again..
>
> The way my system works is that a user on my web site "books" a server for
> a certain period of time. When that is done, a column is added to an sql
> database. A cron script on the master cluster server reads that sql table,
> and if there is a new booking to be made, launches a server on one of the
> nodes as a job submitted to the cluster. If the booking time for the
> server has went out, the server is shut down by the master server, ie, it
(Continue reading)

Permalink | Reply | 6 comments |
headers
kama | 1 Sep 2006 11:31
Picon
Favicon

Re: hlds crashes


I have noticed that in a few occations that (.so) files get corrupted and
I need to overwrite them with new ones. Thats even with a graceful
shutdown. 95%+ of the time its a .so in amxmod that gets corrupted, only a
few times its a binary from the hlds package.

I believe it has todo with that I share the .so's over a couple of servers
and that I shut them down at the same time. (my stop_all_servers.sh
script)

/Bjorn

On Thu, 31 Aug 2006, Jonathan wrote:

> AFAIK they are all clean halflife installations with only cs running (this
> is not hl2 with cs source)
>
> The strange thing is that it all works fine for a few times if i delete
> the clientregistry.blob file, but then after a while the crashes start
> appearing again..
>
> The way my system works is that a user on my web site "books" a server for
> a certain period of time. When that is done, a column is added to an sql
> database. A cron script on the master cluster server reads that sql table,
> and if there is a new booking to be made, launches a server on one of the
> nodes as a job submitted to the cluster. If the booking time for the
> server has went out, the server is shut down by the master server, ie, it
> terminates the submitted job. Does the hlds server need to quit gracefully
> in order for it to work properly the next time it's started? I mean, does
> hlds recover badly from crashes?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jonathan | 1 Sep 2006 11:52
Picon

Re: hlds crashes

Yes, the nodes share images. However, i gave the nodes their own ~/.steam
directory, so it's always the same machine that writes the
clientregistry.blob file. Sure, i could remove it each time a server is
fired up, but it feels like a very ugly hack. :/

The .so files i have in the image directories are:

core_i386.so
engine_amd.so
engine_amd64.so
engine_i486.so
engine_i686.so
filesystem_stdio_amd64.so
filesystem_stdio_i386.so
libSteamValidateUserIDTickets_amd64.so
libSteamValidateUserIDTickets_i386.so
proxy_i386.so
steam_api_i486.so
steamclient_i486.so
test1.so
test2.so
test3.so
tier0_s_i486.so
vstdlib_s_i486.so

I have no idea what those test*.so files are and if they're supposed to be
there or not.

> Suns grid software. Is there a seperate server image to be run on each
> node? or does it share the images and deliver them to whichever node
(Continue reading)

Permalink | Reply | 5 comments |
headers
fishy | 1 Sep 2006 12:27
Picon

Re: hlds crashes

ok, does the issue still occur if the servers do not auto update?

Jonathan wrote:
> Yes, the nodes share images. However, i gave the nodes their own ~/.steam
> directory, so it's always the same machine that writes the
> clientregistry.blob file. Sure, i could remove it each time a server is
> fired up, but it feels like a very ugly hack. :/
>
> The .so files i have in the image directories are:
>
> core_i386.so
> engine_amd.so
> engine_amd64.so
> engine_i486.so
> engine_i686.so
> filesystem_stdio_amd64.so
> filesystem_stdio_i386.so
> libSteamValidateUserIDTickets_amd64.so
> libSteamValidateUserIDTickets_i386.so
> proxy_i386.so
> steam_api_i486.so
> steamclient_i486.so
> test1.so
> test2.so
> test3.so
> tier0_s_i486.so
> vstdlib_s_i486.so
>
> I have no idea what those test*.so files are and if they're supposed to be
> there or not.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jonathan | 1 Sep 2006 12:47
Picon

Re: hlds crashes

I'm not sure, and i'm also not sure what the issue is exactly. People
claim that servers go down just like that when they're playing on them,
but i can't find anything in any of the logs or so, so it's hard for me to
trace the problem.

> ok, does the issue still occur if the servers do not auto update?
>
>
> Jonathan wrote:
>> Yes, the nodes share images. However, i gave the nodes their own
>> ~/.steam
>> directory, so it's always the same machine that writes the
>> clientregistry.blob file. Sure, i could remove it each time a server is
>> fired up, but it feels like a very ugly hack. :/
>>
>> The .so files i have in the image directories are:
>>
>> core_i386.so
>> engine_amd.so
>> engine_amd64.so
>> engine_i486.so
>> engine_i686.so
>> filesystem_stdio_amd64.so
>> filesystem_stdio_i386.so
>> libSteamValidateUserIDTickets_amd64.so
>> libSteamValidateUserIDTickets_i386.so
>> proxy_i386.so
>> steam_api_i486.so
>> steamclient_i486.so
>> test1.so
(Continue reading)

Permalink | Reply | 3 comments |

Gmane