[cod] Strange PB Issue

[Michael Runcieman]

Glad I could help :)

Todd Chamberlain wrote:
> Thank you very much, that did the trick!  Now it started kicking people 
> for md5 mismatch pakb.pk3.  I'm assuming that's because they don't have 
> CoD 1.5 patch?  Is there any way to disable this one md5 check?
> 
> -Todd
> 
> Michael Runcieman wrote:
> 
>> You should just have to do:
>>
>> chmod +x pbweb.x86
>> ./pbweb.x86
>>
>> That should be it.
>>
>> M.
>>
>> Todd Chamberlain wrote:
>>
>>> Alright,
>>>
>>> I tried to do a /rcon pb_sv_update ... but it doesn't seem to work 
>>> (shows first 3 lines of doing something, but then pb restarts?)
>>>
>>> I'm now trying to update via pbweb.x86, but I can't seem to execute 
>>> the binary.  Can anyone give an explanation on how to get it to run?  
>>> I've tried a bunch of commands, but am somewhat of a linux noob.
>>>
>>> Thanks,
>>> Todd
>>>
>>> Jay Vasallo wrote:
>>>
>>>> Do you have an upated pbsvuser.cfg? If the config is still checking 
>>>> for the old files, I could see this being part of the problem. Did 
>>>> you update your pb files after you patched the server?
>>>>
>>>>     ----- Original Message -----
>>>>     *From:* Todd Chamberlain <mailto:togg at rochester.rr.com>
>>>>     *To:* cod at icculus.org <mailto:cod at icculus.org>
>>>>     *Sent:* Tuesday, December 21, 2004 4:57 PM
>>>>     *Subject:* Re: [cod] Strange PB Issue
>>>>
>>>>     PB is restarting itself over and over.  Before the patch was
>>>>     applied, we were up to 9 log files.  Now we're up to 1000, or
>>>>     whatever the ceiling is.  Anyone know why it would be doing this
>>>>     after the patch, but not before?
>>>>
>>>>     Thanks.
>>>>
>>>>     Robert Mount wrote:
>>>>
>>>>>>> PB keep spamming "PB kicks for non standard characters and pb all
>>>>>>> restrictions on this server" every 20seconds. Anyone else having 
>>>>>>> this
>>>>>>> problem and know how to stop it?
>>>>>>>     
>>>>>>
>>>>>
>>>>> You get that message when PB restarts, or when you first connect to a
>>>>> server.  So PB could be restarting itself over and over...
>>>>>
>>>>>  
>>>>>
>>
>>