Kjetil brinchmann Halvorsen:
> On Fri, Nov 26, 2010 at 12:56, Jochen Schulz wrote:
>> Kjetil brinchmann Halvorsen:
>>>
>>> This si my shell (bash) script:
>>>
>>> # shell script to install all the packages in ~/R/allpackages,
>>> # to ~/R/allinstall . Should be run from ~/R/Recommend .
By the w
Jochen Schulz wrote:
> Looks like you are uncompressing and extracting your 3700 tar.gz files
> in parallel. You are probably stressing CPU and hard disk at the same
> time.
...which in this instance will also be considerably LESS efficient than
running these jobs serially.
Chris
--
To UNSUBS
see below.
On Fri, Nov 26, 2010 at 12:56, Jochen Schulz wrote:
> Kjetil brinchmann Halvorsen:
>>
>> This si my shell (bash) script:
>>
>> # shell script to install all the packages in ~/R/allpackages,
>> # to ~/R/allinstall . Should be run from ~/R/Recommend .
>> #
>> for FILE in ~/R/allpackages
Kjetil brinchmann Halvorsen:
>
> This si my shell (bash) script:
>
> # shell script to install all the packages in ~/R/allpackages,
> # to ~/R/allinstall . Should be run from ~/R/Recommend .
> #
> for FILE in ~/R/allpackages/*z
> do
> if [ -f $FILE ]
> then
>nice R CMD INSTALL
see below.
On Fri, Nov 26, 2010 at 07:58, Jochen Schulz wrote:
> Kjetil brinchmann Halvorsen:
>>
>> At 16.10 this afternoon I started a process via a shell script which
>> is nso resource-hungry
> …
>> (In the script, I am loopìng over the about 3700 tar.gz files in one
>> directory. For e ach o
Kjetil brinchmann Halvorsen:
>
> At 16.10 this afternoon I started a process via a shell script which
> is nso resource-hungry
…
> (In the script, I am loopìng over the about 3700 tar.gz files in one
> directory. For e ach of them, I am spawning a
> sub-shell (using &) doing some installation wo
On Fri, Nov 26, 2010 at 1:42 AM, Kjetil brinchmann Halvorsen
wrote:
> At 16.10 this afternoon I started a process via a shell script which
> is nso resource-hungry
> that absolutely nothing else on the computer (amd64 laptop, cpu with
> two cores) got done .
> Even the clock stands frozen at 16.
At 16.10 this afternoon I started a process via a shell script which
is nso resource-hungry
that absolutely nothing else on the computer (amd64 laptop, cpu with
two cores) got done .
Even the clock stands frozen at 16.10 for many hours!
I thought that with a modern, time-sharing OS like linux t
8 matches
Mail list logo