SourceRSC: Difference between revisions
From Rabbi Blog
(New page: Trying out 'SourceRSC' from [http://www.brainless.us Brainless] in order to keep the FoCA CounterStrike Source server up to date with the Fast Asset Download Server. =Installation= *Grabb...) |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 12: | Line 12: | ||
# linux-sourcersc.sh didn't work (even after renaming the target properly) | # linux-sourcersc.sh didn't work (even after renaming the target properly) | ||
## run the program manually with $ mono SourceRSC.exe | ## run the program manually with $ mono SourceRSC.exe | ||
# Had a map that just won't work, otherwise everything else was good. I should post to the author and relay the map for his testing. | |||
## deagle_crypt_dmw_b3.bsp - fails on the upload side | |||
=Thoughts= | =Thoughts= | ||
Line 23: | Line 25: | ||
[[Category:Gaming]] | [[Category:Gaming]] | ||
[[Category:CounterStrike]] | [[Category:CounterStrike]] | ||
[[Category:2007-11]] | [[Category:Weblog-2007-11]] | ||
[[Category:Linux]] | [[Category:Linux]] |
Latest revision as of 21:51, 11 August 2008
Trying out 'SourceRSC' from Brainless in order to keep the FoCA CounterStrike Source server up to date with the Fast Asset Download Server.
Installation
- Grabbed the download file and unzipped it on my Windows machine.
- Ran it once, generating the ini file
- Edited the ini file for accounts and paths between the two servers
- Moved everything over to the linux box
- Ran the program
Issues Dealt With
- Had to set both PASV entries to TRUE in the ini
- linux-sourcersc.sh didn't work (even after renaming the target properly)
- run the program manually with $ mono SourceRSC.exe
- Had a map that just won't work, otherwise everything else was good. I should post to the author and relay the map for his testing.
- deagle_crypt_dmw_b3.bsp - fails on the upload side
Thoughts
Right now I'm on 6 of 152 for syncing, however this looks pretty slick so far. I'll add the sv_downloadurl to the server.cfg after this is done.
Process
I'll CRON the job maybe at 2 a.m. and 11 a.m. (off peak hours). I'll also give directions on logging into the linux box and firing it off manually if needed.