Mike: What does the server show for the ghost slots when you check "rcon users" or "rcon status"? If by some snowball's chance in hell they not only show up, but also have a user id associated with them (since Valve nixed kicking by slot), you could use "rcon kickid #", where # is the user id. Assuming you've got admins who will be running things while you're gone, they could just kick the ghost slots as they appear if this works. More than likely, it won't, although it would be interesting to know if they show up in some way when you check users/status.
If it truly is a memory hole, until the problem itself gets figured out, a once-daily (depending on how quickly the ghost slots compound) server reset schedule would probably be your best bet, but you've already said that you'd like to avoid this. As for a command to drop the slots, "rcon map dod_whatever" will change the map and drop all players in the process, which would theoretically include the ghost players. Because it kicks all players though, I'm assuming that this isn't exactly what you're looking for... unless the reason you want to avoid a reset schedule is a matter of setup difficulty for one reason or another. If that's the case, you could use Mani's crontab list to inform players about it, then run this like a server reset, so that it would run the command on the first map load after a certain time of day. This of course would bring up the issue of how map changes only occur when there's a player in the game, etc... but at least it's an option. Finally, if you're certain that it's always caused by limited spawn custom maps, I'd recommend just pulling those maps from your server while you're gone and dealing with it when you get back. -Grant. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
