Yeah that makes sense from a GSP perspective, or specifically, one that rents or hires boxes to customers. However for those that don't need ultra-customisation usually running all out of the one installation is fine. SM can be enabled/disabled on a per-cfg basis, for example. And yeah, not having to update a million servers individually is kind of a plus too (although that being said, theres nothing that SSH and RSYNC can't fix :P
[email protected] wrote: > The main technical issue with doing that is you have to shutdown all servers > when an update comes out. On the other hand, it also means you only have > one thing to update... > > Sourcemod's website insists you only run one instance from the one place, > but you can copy the files and use sm_basepath on the commend-line to point > each instance at a separate directory > > The other main reason people run them separately is for sandboxing of > different users on a shared host. And we run them from separate installs > just to make the configs easier > > >> -----Original Message----- >> From: [email protected] [mailto:hlds- >> [email protected]] On Behalf Of Shane Arnold >> Sent: 23 November 2009 14:07 >> To: [email protected]; Half-Life dedicated Win32 server mailing list >> Subject: Re: [hlds] TF2 Arena Configs - mapcyclefile >> >> I run 2 or 3 instances of TF2 srcds on any occasion from the same >> installation. The only reason I can see for needing to run a seperate >> installation for each instance is when you are dealing with a mod that >> makes extensive changes to the files or the way in which the >> installation runs. >> >> [email protected] wrote: >> >>> Just a general question regarding this.... Is this common practice >>> >> to run more than one server from one install? I have an instance for >> every server. >> >>> Sent via BlackBerry from T-Mobile >>> >>> -----Original Message----- >>> From: "Charles Mabbott" <[email protected]> >>> Date: Mon, 23 Nov 2009 08:39:15 >>> To: 'Half-Life dedicated Win32 server mailing >>> >> list'<[email protected]> >> >>> Subject: Re: [hlds] TF2 Arena Configs - mapcyclefile >>> >>> Run SRCDS as a specific user account (not System which is default and >>> >> not a >> >>> recommendation anyways) and deny rights to that particular user to >>> >> any >> >>> file/directory you don't want the process to read or change. >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Shane >>> >> Arnold >> >>> Sent: Monday, November 23, 2009 4:34 AM >>> To: Half-Life dedicated Win32 server mailing list >>> Subject: Re: [hlds] TF2 Arena Configs - mapcyclefile >>> >>> chmod 444? Unless of course you are actually using Windows for it, in >>> which case I have no idea (security in Windows? That's unpossible!). >>> >>> Nick Turner wrote: >>> >>> >>>> srcds recreates the file with the default config >>>> >>>> -----Original Message----- >>>> From: [email protected] >>>> >>>> >>> [mailto:[email protected]] On Behalf Of Shane >>> >> Arnold >> >>>> Sent: Monday, November 23, 2009 5:08 PM >>>> To: Half-Life dedicated Win32 server mailing list >>>> Subject: Re: [hlds] TF2 Arena Configs - mapcyclefile >>>> >>>> Remove/rename config_arena.cfg? If it's empty you don't need it >>>> >> anyway. >> >>>> Nick Turner wrote: >>>> >>>> >>>> >>>>> How does one run multiple Arena servers from a single install >>>>> >> directory? >> >>>>> When I comment out the mapcyclefile entry in config_arena.cfg the >>>>> >> server >> >>> loads arena_mapcycle.txt no matter what. >>> >>> >>>>> I have mapcyclefile specified on the command line, and in the >>>>> >> custom >> >>> server config I'm specifying (on the command line) but the server >>> >> executes >> >>> config_arena.cfg after map load and - even if that file is completely >>> >> empty >> >>> - changes the mapcyclefile to the arena one. >>> >>> >>>>> If I specify a mapcyclefile inside config_arena.cfg then that one >>>>> >> is >> >>> loaded correctly, but this means I can only have 1 arena maplist per >>> >> SRCDS >> >>> install directory. >>> >>> >>>>> _______________________________________________ >>>>> To unsubscribe, edit your list preferences, or view the list >>>>> >> archives, >> >>> please visit: >>> >>> >>>>> http://list.valvesoftware.com/mailman/listinfo/hlds >>>>> >>>>> >>>>> >>>>> >>>> _______________________________________________ >>>> To unsubscribe, edit your list preferences, or view the list >>>> >> archives, >> >>> please visit: >>> >>> >>>> http://list.valvesoftware.com/mailman/listinfo/hlds >>>> >>>> _______________________________________________ >>>> To unsubscribe, edit your list preferences, or view the list >>>> >> archives, >> >>> please visit: >>> >>> >>>> http://list.valvesoftware.com/mailman/listinfo/hlds >>>> >>>> >>>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list >>> >> archives, >> >>> please visit: >>> http://list.valvesoftware.com/mailman/listinfo/hlds >>> >>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list >>> >> archives, please visit: >> >>> http://list.valvesoftware.com/mailman/listinfo/hlds >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list >>> >> archives, please visit: >> >>> http://list.valvesoftware.com/mailman/listinfo/hlds >>> >>> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds >> > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
