> On Oct 14, 2016, at 7:37 PM, Clemens Lang wrote:
> - On 15 Oct, 2016, at 01:05, Fred Wright f...@fwright.net wrote:
> ...
>> One can also accomplish this via:
>>
>> sudo touch /opt/local/var/macports/build/.metadata_never_index
>>
>> Though I don't know if this works across all OS ver
Hi,
- On 15 Oct, 2016, at 01:05, Fred Wright f...@fwright.net wrote:
> By default, this isn't possible via the GUI, due to the macports
> directory's being hidden.
Use cmd+shift+g in the file chooser.
> One can also accomplish this via:
>
> sudo touch /opt/local/var/macports/build/.
On Fri, 14 Oct 2016, Ryan Schmidt wrote:
> On Oct 14, 2016, at 09:50, Ken Cunningham
> wrote:
> > Oh, one more similar question while I'm at it.
> >
> > I notice mdworker seems to go nuts during these long builds, often
> > appearing to soak up lots of cycles. I assume it's trying to index
> >
Thanks, all — good advice.
K
> On Oct 14, 2016, at 8:14 AM, Joshua Root wrote:
>
> On 2016-10-15 01:50 , Ken Cunningham wrote:
>>
>> I notice mdworker seems to go nuts during these long builds, often appearing
>> to soak up lots of cycles. I assume it’s trying to index all the build
>> fil
On 2016-10-15 01:50 , Ken Cunningham wrote:
I notice mdworker seems to go nuts during these long builds, often appearing to
soak up lots of cycles. I assume it’s trying to index all the build files, etc
is it easy to sleep that function and then re-enable it after the compile is
done?
Not s
> On Oct 14, 2016, at 10:50 AM, Ken Cunningham
> wrote:
>
> I notice mdworker seems to go nuts during these long builds, often appearing
> to soak up lots of cycles. I assume it’s trying to index all the build files,
> etc
>
> is it easy to sleep that function and then re-enable it after the
On Oct 14, 2016, at 09:50, Ken Cunningham
wrote:
>
>
>> On Oct 14, 2016, at 7:30 AM, Ken Cunningham
>> wrote:
>>
>> Some advice appreciated …
I use screen for this.
> Oh, one more similar question while I’m at it.
>
> I notice mdworker seems to go nuts during these long builds, often ap
> On Oct 14, 2016, at 10:30 AM, Ken Cunningham
> wrote:
>
> long compiles can take hours
>
> i can ssh into the machine and get it started
>
> sudo port -v install gcc48 gcc5 gcc6 gcc7
>
> that, for example, might take several days to finish (if it does
> finish)
>
> then I control-Z to paus
On Fri, Oct 14, 2016 at 10:30 AM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
> how exactly do I best find that process to "fg" it again? If I just log
> back in and "fg" it, it is not found. but top shows the process is humming
> away in the background, as expected
>
You can't; it's
Hi Ken,
I would really use screen instead and disconnect it and reconnect it later.
David
On Fri, Oct 14, 2016 at 4:30 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
> Some advice appreciated ...
>
>
> long compiles can take hours
>
> i can ssh into the machine and get it started
> On Oct 14, 2016, at 7:30 AM, Ken Cunningham
> wrote:
>
> Some advice appreciated …
>
Oh, one more similar question while I’m at it.
I notice mdworker seems to go nuts during these long builds, often appearing to
soak up lots of cycles. I assume it’s trying to index all the build files, et
Some advice appreciated ...
long compiles can take hours
i can ssh into the machine and get it started
sudo port -v install gcc48 gcc5 gcc6 gcc7
that, for example, might take several days to finish (if it does finish)
then I control-Z to pause it, and "bg" to throw it into the background
the
12 matches
Mail list logo
