PlaneShift

Support => Linux Specific Issues => Topic started by: dr.adrian on September 19, 2006, 04:09:50 pm

Title: Slow updater solution (maybe?)
Post by: dr.adrian on September 19, 2006, 04:09:50 pm
 :detective: Has anyone tried to use the auto flag with the updater (a la "./updater -auto")? Worked for me.
Title: Re: Slow updater solution (maybe?)
Post by: ag0ny on September 19, 2006, 04:58:11 pm
I experienced the not at all working updater as well.

Coincidentally i found out that only data is downloaded and the gui updated shortly after the window was made visible again, as brought back in the foreground or i switched back to the workspace the updater ran on from another workspace. It also helped to move another window over the updater and close the window there.

As i am an extremly lazy person and i am using gnome i opened a gnome-terminal an executed the following command (without leading and following quotation marks):

"for i in /dev/; do for i in /dev/; do gnome-terminal -e exit; sleep 1; done; done;"

This will open a gnome-terminal automaticaly every second and automaticaly close it again. If you now make sure the gnome-terminal appears above the updater window the updater will update his gui and keep downloading and therefor updateing. Also this is a very ugly workaround it worked like a charm for me.  :D

Hope this helps anyone...
Title: Re: Slow updater solution (maybe?)
Post by: Kaleriss on September 21, 2006, 12:27:04 am
Heh.  I updated by clicking furiously on the updater in the task bar, minimizing and unminimizing, until it was complete.  Hello carpal tunnel. =P
Title: Re: Slow updater solution (maybe?)
Post by: fozner on September 22, 2006, 12:29:06 am
I believe the updater keeps going if you leave it alone. It just doesn't update the screen frequently. Seems like it completed when I left it running as I went to the discount barn.
Title: Re: Slow updater solution (maybe?)
Post by: ag0ny on September 22, 2006, 02:47:53 pm
I believe the updater keeps going if you leave it alone. It just doesn't update the screen frequently. Seems like it completed when I left it running as I went to the discount barn.

I thought so too, but then i started the network traffic tool and there was no traffic at all when i left the updater alone.
Title: Re: Slow updater solution (maybe?)
Post by: Murtok on September 22, 2006, 05:02:14 pm
./updater -auto

Funktioniert doch super! Warum so viel aufwand?
Title: Re: Slow updater solution (maybe?)
Post by: Ravolt on November 26, 2006, 06:50:59 pm
Heh.  I updated by clicking furiously on the updater in the task bar, minimizing and unminimizing, until it was complete.  Hello carpal tunnel. =P

Yep same here  :'(
Title: Re: Slow updater solution (maybe?)
Post by: Henza on November 27, 2006, 01:16:14 am
I just kept hitting alt + tab...  :)

I remembered that there was something like that updater -auto, but I am lazy, so I thought that was easier...
Title: Re: Slow updater solution (maybe?)
Post by: Peacer on November 27, 2006, 12:37:08 pm
I experienced the not at all working updater as well.

Coincidentally i found out that only data is downloaded and the gui updated shortly after the window was made visible again, as brought back in the foreground or i switched back to the workspace the updater ran on from another workspace. It also helped to move another window over the updater and close the window there.

As i am an extremly lazy person and i am using gnome i opened a gnome-terminal an executed the following command (without leading and following quotation marks):

"for i in /dev/; do for i in /dev/; do gnome-terminal -e exit; sleep 1; done; done;"

This will open a gnome-terminal automaticaly every second and automaticaly close it again. If you now make sure the gnome-terminal appears above the updater window the updater will update his gui and keep downloading and therefor updateing. Also this is a very ugly workaround it worked like a charm for me.  :D

Hope this helps anyone...

distro sir?

amd of I'm not using gnome terminal is there any way to know what to write and how to find out what to write (termianl -v or something)?