Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #58342 > unrolled thread

Dock won't pop up

Back to article view | Back to comp.sys.mac.system

Contents

  Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-05 18:07 -0400
    Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-06 07:37 -0400
      Re: Dock won't pop up dorayme <do_ray_me@bigpond.com> - 2014-04-07 10:36 +1000
        Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 16:47 -0400
          Re: Dock won't pop up John McWilliams <jpmcw@comcast.net> - 2014-04-07 15:44 -0700
            Re: Dock won't pop up dorayme <do_ray_me@bigpond.com> - 2014-04-08 10:37 +1000
              Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:09 -0400
                Re: Dock won't pop up John McWilliams <jpmcw@comcast.net> - 2014-04-12 18:57 -0700
                  Re: Dock won't pop up dorayme <do_ray_me@bigpond.com> - 2014-04-13 13:07 +1000
                    Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 09:31 -0400
                  Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 09:31 -0400
                    Re: Dock won't pop up android <here@there.was> - 2014-04-13 16:58 +0200
                      Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 12:08 -0400
                        Re: Dock won't pop up android <here@there.was> - 2014-04-13 18:25 +0200
                          Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 12:28 -0400
                            Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 13:29 +0000
                              Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 17:10 -0400
                                Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-16 17:34 -0400
                                  Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 18:20 -0400
                                  Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 23:59 +0000
                                    Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-17 15:02 -0400
                                Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-16 17:37 -0400
                                  Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 18:20 -0400
                                  Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-17 00:01 +0000
                        Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-13 16:00 -0400
                        Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 13:28 +0000
                          Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 17:02 -0400
                      Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 13:26 +0000
            Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:08 -0400
              Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-09 14:46 +0000
                Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-09 20:59 -0400
    Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-06 10:10 -0400
      Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-06 11:07 -0400
        Re: Dock won't pop up billy@MIX.COM - 2014-04-06 15:23 +0000
          Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-06 11:46 -0400
            Re: Dock won't pop up billy@MIX.COM - 2014-04-07 01:54 +0000
              Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 16:47 -0400
          Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-07 09:01 +1200
        Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-06 16:40 -0400
          Re: Dock won't pop up David Ritz <dritz@mindspring.com> - 2014-04-06 17:24 -0500
      Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-06 17:20 +0000
        Re: Dock won't pop up Paul Sture <nospam@sture.ch> - 2014-04-06 20:16 +0200
          Re: Dock won't pop up doctor@doctor.nl2k.ab.ca (The Doctor) - 2014-04-06 20:29 +0000
          Re: Dock won't pop up billy@MIX.COM - 2014-04-07 01:57 +0000
            Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-07 16:05 +1200
              Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 16:50 -0400
            Re: Dock won't pop up russotto@grace.speakeasy.net (Matthew Russotto) - 2014-04-09 02:46 +0000
        Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-06 16:42 -0400
          Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-06 18:28 -0400
        Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-06 19:23 -0400
          Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-06 19:38 -0400
            Re: Dock won't pop up Paul Sture <nospam@sture.ch> - 2014-04-07 20:55 +0200
              Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-08 08:47 +1200
          Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-06 20:36 -0400
          Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-07 10:18 -0400
            Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 16:54 -0400
              Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-07 17:17 -0400
                Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-07 18:12 -0400
                  Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 18:38 -0400
                    Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-07 19:10 -0400
                      Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:09 -0400
              Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-07 19:45 -0400
                Re: Dock won't pop up Ted Lee <tmplee@gmail.com> - 2014-04-08 08:03 -0500
                  Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-09 09:03 +1200
                    Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:14 -0400
                Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:12 -0400
                  Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-09 10:18 -0400
                    Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-09 20:58 -0400
                      Re: Dock won't pop up Jolly Roger <jollyroger@pobox.com> - 2014-04-10 01:54 +0000
      Re: Dock won't pop up Barry OGrady <atheist@hotmail.com.au> - 2014-04-19 13:34 +1000
        Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-19 16:29 +1200
          Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 09:42 -0400
            Re: Dock won't pop up Michelle Steiner <michelle@michelle.org> - 2014-04-19 06:50 -0700
              Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 09:59 -0400
                Re: Dock won't pop up Michelle Steiner <michelle@michelle.org> - 2014-04-19 07:51 -0700
                  Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 11:00 -0400
              Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-19 10:12 -0400

Page 1 of 4  [1] 2 3 4  Next page →

#58342 — Dock won't pop up

I haven't seen this happen in a very long time - but my Dock froze 
(would not pop up).

After a bit of bumping around I CMD-Tabbed to Finder, did "About Finder" 
and then it worked.  (Nothing else did).

-- 
   Privacy has become an essential personal chore that most
   people are not trained to perform.
                  - Jaron Lanier, Scientific American, 2013.11.

[toc] | [next] | [standalone]

#58355

In article <hfCdnYJ-yqYx493OnZ2dnUVZ_q6dnZ2d@giganews.com>,
 Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:

> I haven't seen this happen in a very long time - but my Dock froze 
> (would not pop up).
> 
> After a bit of bumping around I CMD-Tabbed to Finder, did "About Finder" 
> and then it worked.  (Nothing else did).

This is a bit obscure, but when that happened to me once, it was because 
the mouse had lost the ability to "hover" (I'm assuming you mean that it 
wouldn't pop up when you moused over it). Unplugging and replugging the 
mouse fixed it. There were also other hover operations that I couldn't 
perform, but I disremember right now what they were.
-- 
Where's the Vangelis music?
Pris' tongue is sticking out in in the wide shot after Batty has kissed her.
They have put back more tits into the Zhora dressing  room scene.
  -- notes for Blade Runner

[toc] | [prev] | [next] | [standalone]

#58374

In article <53413c5d$0$46052$c3e8da3$88b277c5@news.astraweb.com>,
 Warren Oates <warren.oates@gmail.com> wrote:

> In article <hfCdnYJ-yqYx493OnZ2dnUVZ_q6dnZ2d@giganews.com>,
>  Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
> 
> > I haven't seen this happen in a very long time - but my Dock froze 
> > (would not pop up).
> > 
> > After a bit of bumping around I CMD-Tabbed to Finder, did "About Finder" 
> > and then it worked.  (Nothing else did).
> 
> This is a bit obscure, but when that happened to me once, it was because 
> the mouse had lost the ability to "hover" (I'm assuming you mean that it 
> wouldn't pop up when you moused over it). Unplugging and replugging the 
> mouse fixed it. There were also other hover operations that I couldn't 
> perform, but I disremember right now what they were.

I have had this problem now and then. A restart fixes generally.

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#58381

On 2014.04.06, 20:36 , dorayme wrote:
> In article <53413c5d$0$46052$c3e8da3$88b277c5@news.astraweb.com>,
>   Warren Oates <warren.oates@gmail.com> wrote:
>
>> In article <hfCdnYJ-yqYx493OnZ2dnUVZ_q6dnZ2d@giganews.com>,
>>   Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>>
>>> I haven't seen this happen in a very long time - but my Dock froze
>>> (would not pop up).
>>>
>>> After a bit of bumping around I CMD-Tabbed to Finder, did "About Finder"
>>> and then it worked.  (Nothing else did).
>>
>> This is a bit obscure, but when that happened to me once, it was because
>> the mouse had lost the ability to "hover" (I'm assuming you mean that it
>> wouldn't pop up when you moused over it). Unplugging and replugging the
>> mouse fixed it. There were also other hover operations that I couldn't
>> perform, but I disremember right now what they were.
>
> I have had this problem now and then. A restart fixes generally.

Not needed in this case.  As much as possible I avoid restarting my 
computer if there is a fix that will work.  The problem is finding the fix.

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58389

On 4/7/14   PDT, 1:47 PM, Alan Browne wrote:
> On 2014.04.06, 20:36 , dorayme wrote:
>> In article <53413c5d$0$46052$c3e8da3$88b277c5@news.astraweb.com>,
>>   Warren Oates <warren.oates@gmail.com> wrote:
>>
>>> In article <hfCdnYJ-yqYx493OnZ2dnUVZ_q6dnZ2d@giganews.com>,
>>>   Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>>>
>>>> I haven't seen this happen in a very long time - but my Dock froze
>>>> (would not pop up).
>>>>
>>>> After a bit of bumping around I CMD-Tabbed to Finder, did "About
>>>> Finder"
>>>> and then it worked.  (Nothing else did).
>>>
>>> This is a bit obscure, but when that happened to me once, it was because
>>> the mouse had lost the ability to "hover" (I'm assuming you mean that it
>>> wouldn't pop up when you moused over it). Unplugging and replugging the
>>> mouse fixed it. There were also other hover operations that I couldn't
>>> perform, but I disremember right now what they were.
>>
>> I have had this problem now and then. A restart fixes generally.
>
> Not needed in this case.  As much as possible I avoid restarting my
> computer if there is a fix that will work.  The problem is finding the fix.

What makes you take steps to avoid restarting a computer? Often enough a 
restart does good things.

[toc] | [prev] | [next] | [standalone]

#58392

In article <lhv9o0$hr8$1@dont-email.me>,
 John McWilliams <jpmcw@comcast.net> wrote:

> On 4/7/14   PDT, 1:47 PM, Alan Browne wrote:
> > On 2014.04.06, 20:36 , dorayme wrote:
> >> In article <53413c5d$0$46052$c3e8da3$88b277c5@news.astraweb.com>,
> >>   Warren Oates <warren.oates@gmail.com> wrote:
> >>
> >>> In article <hfCdnYJ-yqYx493OnZ2dnUVZ_q6dnZ2d@giganews.com>,
> >>>   Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
> >>>
> >>>> I haven't seen this happen in a very long time - but my Dock froze
> >>>> (would not pop up).
> >>>>
> >>>> After a bit of bumping around I CMD-Tabbed to Finder, did "About
> >>>> Finder"
> >>>> and then it worked.  (Nothing else did).
> >>>
> >>> This is a bit obscure, but when that happened to me once, it was because
> >>> the mouse had lost the ability to "hover" (I'm assuming you mean that it
> >>> wouldn't pop up when you moused over it). Unplugging and replugging the
> >>> mouse fixed it. There were also other hover operations that I couldn't
> >>> perform, but I disremember right now what they were.
> >>
> >> I have had this problem now and then. A restart fixes generally.
> >
> > Not needed in this case.  As much as possible I avoid restarting my
> > computer if there is a fix that will work.  The problem is finding the fix.
> 
> What makes you take steps to avoid restarting a computer? Often enough a 
> restart does good things.

Puzzled me too, a restart is like opening the window to a good breeze 
when someone has farted.

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#58406

On 2014.04.07, 20:37 , dorayme wrote:
> In article <lhv9o0$hr8$1@dont-email.me>,
>   John McWilliams <jpmcw@comcast.net> wrote:
>
>> On 4/7/14   PDT, 1:47 PM, Alan Browne wrote:
>>> On 2014.04.06, 20:36 , dorayme wrote:
>>>> In article <53413c5d$0$46052$c3e8da3$88b277c5@news.astraweb.com>,
>>>>    Warren Oates <warren.oates@gmail.com> wrote:
>>>>
>>>>> In article <hfCdnYJ-yqYx493OnZ2dnUVZ_q6dnZ2d@giganews.com>,
>>>>>    Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>>>>>
>>>>>> I haven't seen this happen in a very long time - but my Dock froze
>>>>>> (would not pop up).
>>>>>>
>>>>>> After a bit of bumping around I CMD-Tabbed to Finder, did "About
>>>>>> Finder"
>>>>>> and then it worked.  (Nothing else did).
>>>>>
>>>>> This is a bit obscure, but when that happened to me once, it was because
>>>>> the mouse had lost the ability to "hover" (I'm assuming you mean that it
>>>>> wouldn't pop up when you moused over it). Unplugging and repluggingthe
>>>>> mouse fixed it. There were also other hover operations that I couldn't
>>>>> perform, but I disremember right now what they were.
>>>>
>>>> I have had this problem now and then. A restart fixes generally.
>>>
>>> Not needed in this case.  As much as possible I avoid restarting my
>>> computer if there is a fix that will work.  The problem is finding the fix.
>>
>> What makes you take steps to avoid restarting a computer? Often enougha
>> restart does good things.
>
> Puzzled me too, a restart is like opening the window to a good breeze
> when someone has farted.

For MS Windows I agree.

OS' that need a reboot for "freshness" are flawed.

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58507

On 4/8/14   PDT, 2:09 PM, Alan Browne wrote:
> On 2014.04.07, 20:37 , dorayme wrote:
>> In article <lhv9o0$hr8$1@dont-email.me>,
>>>
>>> What makes you take steps to avoid restarting a computer? Often enough a
>>> restart does good things.
>>
>> Puzzled me too, a restart is like opening the window to a good breeze
>> when someone has farted.
>
> For MS Windows I agree.
>
> OS' that need a reboot for "freshness" are flawed.
>
Ah, so you're the Christian Scientist of Macdom!

[toc] | [prev] | [next] | [standalone]

#58508

In article <licqu6$rb9$1@dont-email.me>,
 John McWilliams <jpmcw@comcast.net> wrote:

> On 4/8/14   PDT, 2:09 PM, Alan Browne wrote:
> > On 2014.04.07, 20:37 , dorayme wrote:
> >> In article <lhv9o0$hr8$1@dont-email.me>,
> >>>
> >>> What makes you take steps to avoid restarting a computer? Often enough a
> >>> restart does good things.
> >>
> >> Puzzled me too, a restart is like opening the window to a good breeze
> >> when someone has farted.
> >
> > For MS Windows I agree.
> >
> > OS' that need a reboot for "freshness" are flawed.
> >
> Ah, so you're the Christian Scientist of Macdom!

Anyone who claims they have an OS that is not flawed, or a whole 
system that is not is almost certainly deluded.

(Just had to restart to get my Airport connection back... happens now 
and then... It is a *possibility* - unlikely - that whenever I do 
this, it would have come back anyway. The Ptolemy astronomical system 
was doggedly defended for years after its use by date had arrived.)

-- 
dorayme

[toc] | [prev] | [next] | [standalone]

#58517

On 2014.04.12, 23:07 , dorayme wrote:
> In article <licqu6$rb9$1@dont-email.me>,
>   John McWilliams <jpmcw@comcast.net> wrote:
>
>> On 4/8/14   PDT, 2:09 PM, Alan Browne wrote:
>>> On 2014.04.07, 20:37 , dorayme wrote:
>>>> In article <lhv9o0$hr8$1@dont-email.me>,
>>>>>
>>>>> What makes you take steps to avoid restarting a computer? Often enough a
>>>>> restart does good things.
>>>>
>>>> Puzzled me too, a restart is like opening the window to a good breeze
>>>> when someone has farted.
>>>
>>> For MS Windows I agree.
>>>
>>> OS' that need a reboot for "freshness" are flawed.
>>>
>> Ah, so you're the Christian Scientist of Macdom!
>
> Anyone who claims they have an OS that is not flawed, or a whole
> system that is not is almost certainly deluded.

Who claimed that?


-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58516

On 2014.04.12, 21:57 , John McWilliams wrote:
> On 4/8/14   PDT, 2:09 PM, Alan Browne wrote:
>> On 2014.04.07, 20:37 , dorayme wrote:
>>> In article <lhv9o0$hr8$1@dont-email.me>,
>>>>
>>>> What makes you take steps to avoid restarting a computer? Often
>>>> enough a
>>>> restart does good things.
>>>
>>> Puzzled me too, a restart is like opening the window to a good breeze
>>> when someone has farted.
>>
>> For MS Windows I agree.
>>
>> OS' that need a reboot for "freshness" are flawed.
>>
> Ah, so you're the Christian Scientist of Macdom!

I'm just a rational user who has a stable OS that runs w/o issues or 
memory leaks (that in part is I don't seem to have apps that leak much). 
  I'm certainly not the only one who does this.

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58519

In article <77KdncRtxpMCDNfOnZ2dnUVZ_hOdnZ2d@giganews.com>,
 Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:

> On 2014.04.12, 21:57 , John McWilliams wrote:
> > On 4/8/14   PDT, 2:09 PM, Alan Browne wrote:
> >> On 2014.04.07, 20:37 , dorayme wrote:
> >>> In article <lhv9o0$hr8$1@dont-email.me>,
> >>>>
> >>>> What makes you take steps to avoid restarting a computer? Often
> >>>> enough a
> >>>> restart does good things.
> >>>
> >>> Puzzled me too, a restart is like opening the window to a good breeze
> >>> when someone has farted.
> >>
> >> For MS Windows I agree.
> >>
> >> OS' that need a reboot for "freshness" are flawed.
> >>
> > Ah, so you're the Christian Scientist of Macdom!
> 
> I'm just a rational user who has a stable OS that runs w/o issues or 
> memory leaks (that in part is I don't seem to have apps that leak much). 
>   I'm certainly not the only one who does this.

I would agree since i sometimes only reboot the putter once a week or 
so, but...
If you've managed to generate a lot of swap then it' can be a good idea 
to reboot since the OSX do not eat back the swaps that promptly after 
the apps that craved them have been closed and the removal of those 
swaps seem to speed up things quite a bit. 
Oki, I'm on SL here and fresher cats and cattle might behave differently.
-- 
teleportation kills
http://tinyurl.com/androidphotography

[toc] | [prev] | [next] | [standalone]

#58521

On 2014.04.13, 10:58 , android wrote:
> In article <77KdncRtxpMCDNfOnZ2dnUVZ_hOdnZ2d@giganews.com>,
>   Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>
>> On 2014.04.12, 21:57 , John McWilliams wrote:
>>> On 4/8/14   PDT, 2:09 PM, Alan Browne wrote:
>>>> On 2014.04.07, 20:37 , dorayme wrote:
>>>>> In article <lhv9o0$hr8$1@dont-email.me>,
>>>>>>
>>>>>> What makes you take steps to avoid restarting a computer? Often
>>>>>> enough a
>>>>>> restart does good things.
>>>>>
>>>>> Puzzled me too, a restart is like opening the window to a good breeze
>>>>> when someone has farted.
>>>>
>>>> For MS Windows I agree.
>>>>
>>>> OS' that need a reboot for "freshness" are flawed.
>>>>
>>> Ah, so you're the Christian Scientist of Macdom!
>>
>> I'm just a rational user who has a stable OS that runs w/o issues or
>> memory leaks (that in part is I don't seem to have apps that leak much).
>>    I'm certainly not the only one who does this.
>
> I would agree since i sometimes only reboot the putter once a week or
> so, but...
> If you've managed to generate a lot of swap then it' can be a good idea
> to reboot since the OSX do not eat back the swaps that promptly after
> the apps that craved them have been closed and the removal of those
> swaps seem to speed up things quite a bit.

Even on my 6 GB iMac I would go weeks between boots - and it did swap 
regularly - but I kept an eye on the memory (using MenuMeters) and when 
I saw the "rest memory" (when I would unload all but my "baseline" apps 
(Mail, browser, calendar) be too high (over ~2 GB) then I'd reboot.  But 
more often I would have to restart for some other reason.  (S/w install 
or resetting something that demanded a restart).

> Oki, I'm on SL here and fresher cats and cattle might behave differently.

I now have an iMac with 24 GB of RAM that the OS greedily takes 
advantage of but still leaves much more available than I need by far - 
but I still watch the memory state - just much less often.

Ironically while I've installed luxury levels of memory, Mavericks 
introduced new, more efficient memory management.  And compression that 
I would just as soon turn off on this iMac - yes, it's CPU efficient, 
but I don't really need it at all.  (Currently @ 2.1 MB - less than 
1/100 of a percent of installed memory).

So, just before I posted this, I went into interwebverse and found a way 
to turn off memory compression.  Other post with details posted.

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58522

In article <hrWdnZHK8t0UK9fOnZ2dnUVZ_hsAAAAA@giganews.com>,
 Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:

> Ironically while I've installed luxury levels of memory, Mavericks 
> introduced new, more efficient memory management.  And compression that 
> I would just as soon turn off on this iMac - yes, it's CPU efficient, 
> but I don't really need it at all.  (Currently @ 2.1 MB - less than 
> 1/100 of a percent of installed memory).
> 
> So, just before I posted this, I went into interwebverse and found a way 
> to turn off memory compression.  Other post with details posted.

Yeah, I saw that post. Good to know stuff...
-- 
teleportation kills
http://tinyurl.com/androidphotography

[toc] | [prev] | [next] | [standalone]

#58523

On 2014.04.13, 12:25 , android wrote:
> In article <hrWdnZHK8t0UK9fOnZ2dnUVZ_hsAAAAA@giganews.com>,
>   Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>
>> Ironically while I've installed luxury levels of memory, Mavericks
>> introduced new, more efficient memory management.  And compression that
>> I would just as soon turn off on this iMac - yes, it's CPU efficient,
>> but I don't really need it at all.  (Currently @ 2.1 MB - less than
>> 1/100 of a percent of installed memory).
>>
>> So, just before I posted this, I went into interwebverse and found a way
>> to turn off memory compression.  Other post with details posted.
>
> Yeah, I saw that post. Good to know stuff...

(I've turned off timer-coalescing as well - this is not a "boot time" 
setting like the mem-compression - it takes immediate effect):

	sudo sysctl -w kern.timer.coalescing_enabled=0

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58567

In message <k-ednS7bUqqpJtfOnZ2dnUVZ_vWdnZ2d@giganews.com> 
  Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
> On 2014.04.13, 12:25 , android wrote:
>> In article <hrWdnZHK8t0UK9fOnZ2dnUVZ_hsAAAAA@giganews.com>,
>>   Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>>
>>> Ironically while I've installed luxury levels of memory, Mavericks
>>> introduced new, more efficient memory management.  And compression that
>>> I would just as soon turn off on this iMac - yes, it's CPU efficient,
>>> but I don't really need it at all.  (Currently @ 2.1 MB - less than
>>> 1/100 of a percent of installed memory).
>>>
>>> So, just before I posted this, I went into interwebverse and found a way
>>> to turn off memory compression.  Other post with details posted.
>>
>> Yeah, I saw that post. Good to know stuff...

> (I've turned off timer-coalescing as well - this is not a "boot time" 
> setting like the mem-compression - it takes immediate effect):

> 	sudo sysctl -w kern.timer.coalescing_enabled=0

So you want your computer to work harder than it needs to, draw more
power, and generate more heat.

That's just stupid.

-- 
'Oh, I never play to win.' She smiled. 'But I do play not to lose.'

[toc] | [prev] | [next] | [standalone]

#58576

On 2014.04.16, 09:29 , Lewis wrote:
> In message <k-ednS7bUqqpJtfOnZ2dnUVZ_vWdnZ2d@giganews.com>
>    Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>> On 2014.04.13, 12:25 , android wrote:
>>> In article <hrWdnZHK8t0UK9fOnZ2dnUVZ_hsAAAAA@giganews.com>,
>>>    Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>>>
>>>> Ironically while I've installed luxury levels of memory, Mavericks
>>>> introduced new, more efficient memory management.  And compression that
>>>> I would just as soon turn off on this iMac - yes, it's CPU efficient,
>>>> but I don't really need it at all.  (Currently @ 2.1 MB - less than
>>>> 1/100 of a percent of installed memory).
>>>>
>>>> So, just before I posted this, I went into interwebverse and found away
>>>> to turn off memory compression.  Other post with details posted.
>>>
>>> Yeah, I saw that post. Good to know stuff...
>
>> (I've turned off timer-coalescing as well - this is not a "boot time"
>> setting like the mem-compression - it takes immediate effect):
>
>> 	sudo sysctl -w kern.timer.coalescing_enabled=0
>
> So you want your computer to work harder than it needs to, draw more
> power, and generate more heat.

All timer coalescing does is group time based events into a coarser 
schedule to reduce the number of idle2wake transitions.  This is 
beneficial in terms of power draw at a level that is important for 
battery driven laptops but hardly significant to a desktop machine.

Turning it off will use a little more power in the end (negligible for a 
desktop) but even that negligible amount of heat goes to heating the 
house 6 months of the year.

>
> That's just stupid.

No.  But your reply is just kneejerk - as usual.

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58578

On 14-04-16 17:10, Alan Browne wrote:

> All timer coalescing does is group time based events into a coarser 
> schedule to reduce the number of idle2wake transitions.  This is 
> beneficial in terms of power draw at a level that is important for 
> battery driven laptops but hardly significant to a desktop machine.


It also depends on what type of aplications you run. If you are running
a real time collection of data or controlling machinery, you don't want
the OS to delay delivery of any timed events.  But if you are doing word
processing, you don't care if the clock skips a second because one timer
event was "coalesced" and by the time it was delivered, another second
had passed.

[toc] | [prev] | [next] | [standalone]

#58582

On 2014.04.16, 17:34 , JF Mezei wrote:
> On 14-04-16 17:10, Alan Browne wrote:
>
>> All timer coalescing does is group time based events into a coarser
>> schedule to reduce the number of idle2wake transitions.  This is
>> beneficial in terms of power draw at a level that is important for
>> battery driven laptops but hardly significant to a desktop machine.
>
>
> It also depends on what type of aplications you run. If you are running
> a real time collection of data or controlling machinery, you don't want
> the OS to delay delivery of any timed events.  But if you are doing word
> processing, you don't care if the clock skips a second because one timer
> event was "coalesced" and by the time it was delivered, another second
> had passed.

In a real time system (and there are various strategies) you either have 
"guaranteed to run on time" where coalescing probably doesn't matter 
because tasks can be prioritized and IAC will execute very soon after a 
timer has updated or is guaranteed to run on time due to pre-emption; or 
"guaranteed not to run before" so even if the task starts a little late, 
it should not matter.  In the later case it's usual to have hardware 
that is a little over spec (eg: if a 200 MHz clock will do it, then put 
in a 400 MHz clock instead and be sure).

And of course it can be turned off - because while OS X _can_ do real 
time, it is not a real time OS.  If the system is critical and 
especially if there are safety considerations, then the control should 
be on a dedicated system with an appropriate RT OS (or no "OS" at all) 
system - and indeed certified if needed (nuclear, aviation, etc.).

-- 
"Big data can reduce anything to a single number,
  but you shouldn’t be fooled by the appearance of exactitude."
      -Gary Marcus and Ernest Davis, NYT, 2014.04.07

[toc] | [prev] | [next] | [standalone]

#58584

In message <534ef778$0$17053$c3e8da3$dd9697d2@news.astraweb.com> 
  JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 14-04-16 17:10, Alan Browne wrote:

>> All timer coalescing does is group time based events into a coarser 
>> schedule to reduce the number of idle2wake transitions.  This is 
>> beneficial in terms of power draw at a level that is important for 
>> battery driven laptops but hardly significant to a desktop machine.


> It also depends on what type of aplications you run. If you are running
> a real time collection of data or controlling machinery, you don't want
> the OS to delay delivery of any timed events.  But if you are doing word
> processing, you don't care if the clock skips a second because one timer
> event was "coalesced" and by the time it was delivered, another second
> had passed.

This might be an issue if it was a second. It's not, it's 1/1000th of a
second or maybe 1/100th of a second.

-- 
"Oh damn", said Maladict.

[toc] | [prev] | [next] | [standalone]

Page 1 of 4  [1] 2 3 4  Next page →

Back to top | Article view | comp.sys.mac.system

csiph-web