does anybody got trouble with drop on DODS ? on my css its ok, sometimes
when oponent is killed drop appear but never on my dods :/
any idea ?
2011/12/16 Eli Witt <eliw...@gmail.com>
> I ran the update manually on my servers and it worked, properly, the first
> time. No segfaults, no crashes, no nothing. I quit the server, updated and
> relaunched as expected and the server was 32/32 within 5 minutes, and it
> still running juuuust fine.
>
> On Fri, Dec 16, 2011 at 8:57 AM, <gamead...@127001.org> wrote:
>
> > No idea what's up then; by contrast I have literally never had the issues
> > you describe, which means it's not a problem with valve's update content,
> > at least (of course it might still be a problem with their content
> delivery
> > system...)
> >
> > PharaohsPaw <listac...@lvwnet.com> wrote:
> >
> > >
> > > Regarding the update failures, what was $?
> > >
> > > That is, did the updater exit 0, or something else?
> > >
> > > My auto-update script checks to make sure that I get exit 0 from steam,
> > > or else it runs again up to four times before it gives up. It is very
> > > common that it runs twice.
> > >
> > > I don't use nemrun myself, but I seem to remember his script doing a
> > > similar exit code check and re-running the update as necessary.
> > >
> > > If steam didn't exit 0, it didn't update. If you don't know, then you
> > > should!
> > >
> > > Just do "echo $?" immediately and only immediately after the steam
> > > command finishes to find out the exit code. If it's 0, that's good. if
> > > it's something else, re-run the update.
> >
> > nemrun DOES re-check. The scripts are out there for anybody to look at,
> > including Valve and anyone else who wants to suggest it is doing
> something
> > wrong as an explanation for the problem.
> >
> > I would imagine a lot of people on this list actually DO know about bash
> > using $? to store the return code from the last command. I do and have
> > for a long time. Here's a snip from one of my simpler "older days" update
> > scripts:
> >
> > --------
> > # update game function definition
> > game_update() {
> >
> > ./steam -command update -game "tf" -dir . -verify_all -retry
> >
> > }
> >
> > cd ~/tf2
> >
> >
> > # run update function once in case we get a zero return value on 1st try:
> > game_update
> >
> > #echo "Return Code: $?"
> >
> > ## loop - we should keep doing this until we get a zero return
> > #
> > until [ $? -eq 0 ] ; do
> >
> > game_update
> > done
> > --------
> >
> > The problem isn't that our scripts are doing the wrong thing.
> >
> >
> >
> >
> >
> > >
> > > --
> > >
> > > This isn't the best bash, but whatever. This is a snip, may be
> > > incomplete.
> > >
> > > while [ /bin/true ] ; do
> > > ./steam -command update -game $GAME -dir ./$GAMEDIR -retry
> > > UPDATEEXIT=$?
> > > UPDATECOUNTER=$(( $UPDATECOUNTER + 1)) # counter increment
> > > echo ""
> > > echo "./steam update exit code was $UPDATEEXIT"
> > > if [ "$UPDATEEXIT" = 0 ] ; then
> > > echo ""
> > > echo "Update completed. Please start server if desired."
> > > break
> > > else
> > > echo ""
> > > echo "Update did not succeed."
> > > if [ "$UPDATECOUNTER" -lt "5" ] ; then
> > > echo "Try $UPDATECOUNTER failed, will try again..."
> > > sleep 1
> > > continue
> > > fi
> > > if [ "$UPDATECOUNTER" -eq "5" ] ; then
> > > echo "Tried $UPDATECOUNTER times already. Will not try again."
> > > break
> > > fi
> > > fi
> > > done
> > >
> > >
> > >
> > >
> > > John Schoenick wrote:
> > >> nemrun just calls hldsupdatetool with normal options.
> > >>
> > >> Your princess is in another castle.
> > >>
> > >> On 12/15/2011 08:32 PM, Fletcher Dunn wrote:
> > >>> PatchVersion=1.1.8.9
> > >>> ProductName=tf
> > >>> appID=440
> > >>>
> > >>> The file was definitely updated in the depots. I don't know why some
> > >>> people are not able to get it. You know there *is* something else
> that
> > >>> has changed other than our update: many of you are using a new
> > >>> up-to-date check script. Nothing on our end has changed with regard
> to
> > >>> how we distribute this file. None of the Valve dedicated servers had
> a
> > >>> problem receiving it.
> > >>>
> > >>> It looks like there is a problem where old servers are still allowed
> > >>> to be listed, if they were logged in before the update. That may be
> > >>> adding to the confusion.
> > >>>
> > >>> - Fletch
> > >
> > > --
> > > # Jesse Molina
> > > # Mail = je...@opendreams.net
> > > # Page = page-je...@opendreams.net
> > > # Cell = 1.602.323.7608
> > > # Web = http://www.opendreams.net/jesse/
> > >
> > >
> > >
> > >_____________________________________________
> >
> > > To unsubscribe, edit your list preferences, or view the list archives,
> > > please visit:
> > > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
> > >
> >
> >
> > _____________________________________________
> >
> > To unsubscribe, edit your list preferences, or view the list archives,
> > please visit:
> > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
> >
> > _______________________________________________
> > To unsubscribe, edit your list preferences, or view the list archives,
> > please visit:
> > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
> >
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
