We run L4D, L4D2, CSS and TF2 servers on the same machine and VAC works fine on 64bit Debian.
I had issue like you had once but it was related to screen being "stuck" and VAC didn't go on at a CSS server untill i killed the old screen session. This usually happens if you run a CSS server on screen, then kill the server, leave screen on and start another screen session and run the CSS server with same ip and port on new screen. For some reason, VAC won't go on untill you kill the previous screen. Atleast that was the case back then. -ics 8.2.2010 15:22, [email protected] kirjoitti: > This is a Steam based issue where CS:S and L4D2 servers loose their VAC > secure status after a while, or not even start secure. > > Having CS:S and L4D2 servers on same machine causes the above issue. Could > Valve possibly fix this issue? > > Currently you cannot host those servers on same machine which is very > annoying. The problem goes away when you shutdown all L4D2 servers and > restart CS:S servers. > > I did not had this issue with L4D/CS:S servers on same machine... > > Problem persists with all of my ten 32/64bit machines. > > Best regards > Tapio Niemelä > GameFrame.net CEO > > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
