[Server Feature] Admin list

[ic3y]

I dont know, how I can describe it.

Same like serverlocs but only one file where all listed who logged in.

So u must check the serverloc for people who logged in.
So its a bit easier

[lilb990]

Also, to see who is trying to login with a bad password. But anyways +1 for this one!

[jitspoe]

It should be pretty trivial to parse the logs for logins.  I don't really see why it would be necessary to have a separate file.  If you have trouble doing that, I'm sure somebody could write up a quick script or app to parse the lines out that matter and write them to a separate file.

[lilb990]

So is there going to be a feature vote or not?

[KnacK]

Doesn't look like it.

[jitspoe]

If you're on windows, just load up a command prompt, change to your paintball2/pball directory and type this:

type qconsole27910.log | Find "ADMIN:"

On linux:

grep "ADMIN:" qconsole27910.log

If you want, you can redirect to a file with >:

type qconsole27910.log | Find "ADMIN:" > adminlog.txt

[ic3y]

If you're on windows, just load up a command prompt, change to your paintball2/pball directory and type this:

type qconsole27910.log | Find "ADMIN:"

On linux:

grep "ADMIN:" qconsole27910.log

If you want, you can redirect to a file with >:

type qconsole27910.log | Find "ADMIN:" > adminlog.txt

I have a Suse V-Server and the logs are very big. It needs time to open a log. A seperate file is smaller.

type qconsole27910.log | Find "ADMIN:" > adminlog.txt

U get too:
xxxxx entered a bad password

And u get a file, where all "ADMINS:" lines stay.
One file where stay only, who logged in, were perfect.

ic3y; XYZ
homie; 123
..

[jitspoe]

If we get global login based admin, doesn't it make this kind of pointless?  And what good is it knowing who logged in without context?

[ic3y]

U can check faster who has maybe a login hacked.

ic3y; XYZ
homie; 123

etc

because after a time the logs are rly big and need a time to open.
But kk then me / we use the old slower way