[GRASS5] [bug #3298] (grass) GUI stop/continue button

[Maciek Sieczka]

Hamish

Thank you for this workaround. However, if possible, having stop/cont button
back would be very handy - one click instead of "top" and 4 keyboard
pressings (7 pressings alltogether) or "renice +19 -p $$" (17 pressings)
each time. Also modifying grass .grass.bashrc according to your listing will
be likely beyond knowledge of average Grass user, while everybody is capable
of using mouse.

I understand you wanted to help me and I'll make use of your suggestion,
thanks. However it would be wrong to take this as an ultimate solution for
all.

Maciek

From: "Hamish" <hamish_nospam at yahoo.com>
>> In 5.4 there was a handy button for stopping/continuing operation of a
>> module. Could it be ported to 6.1? I found it very practical - say
>> there is a v.surf.rst working which eats whole my CPU time and it is
>> going to work whole day long, while I need full power just for 15
>> minutes for another Grass program.
>>
>> I bet this could be done with some unix commands, but having that
>> stop/continue button was very usefull, easy and quick in use.
>
>
> fyi, the UNIX commands you speak of:
>
> top
>
> then hit "r" and type in PID of process eating 99% of the CPU. Set in
> the range of 1-19, where 19 means the lowest priority.
> Then "q" to quit.
>
>
> or before starting the run reset the current shell's priority:
>
> renice +19 -p $$
>
>
>
> I add this to .grass.bashrc so GRASS always runs at semi-low priority:
>
> GRASS_PROC="`pgrep Init.sh`"
> if [ -n "$GRASS_PROC" ] ; then
>   renice +15 -p $$
> fi
>
>
> (the pgrep test isn't really needed)
>
>
> Hamish