Boot time

On Sun, 13 Apr 2008 20:21:29 -0500, Jolly Roger <jollyroger DeleteThis @pobox.com>
wrote:

>If you had done something that caused the system to have to rebuild
>system caches, then it's certainly within what I would consider to be an
>acceptable range.

How can I check this? This is getting old.
 >> Stay informed about: Boot time 

Howard Brazee <howard.RemoveThis@brazee.net> wrote:

> >If you had done something that caused the system to have to rebuild
> >system caches, then it's certainly within what I would consider to be an
> >acceptable range.
>
> How can I check this?

How can you check whether you've done something that caused the system
to have to rebuild caches? Well, for starters, how about telling us why
you rebooted your computer?

> This is getting old.

_What_ is getting old? You said you rebooted your computer once. Is
there an ongoing problem you expect us to somehow know about despite
your not having given any details?

Meanwhile, your subject line talks about boot time but your post itself
only talks about the clock. What exactly is the problem you want us to
help you with?

--
<http://designsbymike.net/shop/mac.cgi> Mac and geek T-shirts & gifts
<http://designsbymike.net/election.shtml> Election 2008 goods.
<http://designsbymike.net/shop/prius.cgi> Prius shirts/bumper stickers
<http://designsbymike.net/shop/greet.cgi> Holiday cards with attitude
 >> Stay informed about: Boot time 

On Mon, 14 Apr 2008 09:31:50 -0400, mikePOST DeleteThis @TOGROUPmacconsult.com
(Mike Rosenberg) wrote:

>> How can I check this?
>
>How can you check whether you've done something that caused the system
>to have to rebuild caches? Well, for starters, how about telling us why
>you rebooted your computer?

This time I rebooted my computer for the sole purpose of timing how
long it took to reboot. I knew its been taking a long time, but
thought I'd find out how long before asking about it.

So shortly after rebooting (trying to fix a problem connecting to the
internet), I rebooted again to find out how long it took.


>Meanwhile, your subject line talks about boot time but your post itself
>only talks about the clock. What exactly is the problem you want us to
>help you with?

I used the clock to determine how long it took to boot. I have a
feeling it didn't take that long to boot when the computer was new -
but I never timed it before. So I decided to time it and ask here if
a 6 minute boot time was reasonable.
 >> Stay informed about: Boot time 

In article <uug604dh593msb7bttl925og9oit7vqsju.DeleteThis@4ax.com>,
Howard Brazee <howard.DeleteThis@brazee.net> wrote:

> On Sun, 13 Apr 2008 20:21:29 -0500, Jolly Roger <jollyroger.DeleteThis@pobox.com>
> wrote:
>
> >If you had done something that caused the system to have to rebuild
> >system caches, then it's certainly within what I would consider to be an
> >acceptable range.
>
> How can I check this? This is getting old.

If it's happening over and over again, something's probably wrong.

Examine your console and system logs for errors, and report any errors
you find here for diagnosis.

Viewing Crash, Console, and System Logs

1. Open /Applications/Utilities/Console.

2. From the Console menu bar, select File > View System Log.

3. From the Console menu bar, select File > View Console Log.

The system log will usually give you an indication as to what is causing
startup issues. The console log can show issues you experience after you
are logged into your user account.

If a particular application is crashing, you may find a crash log in
/Library/Logs/CrashReporter/ or /Users/you/Library/Logs/CrashReporter/.

(Feel free to post the logs here if you need help understanding them.
I'll be glad to take a look and tell you what I see.)

--
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR
 >> Stay informed about: Boot time 

On Mon, 14 Apr 2008 18:22:40 -0500, Jolly Roger <jollyroger.DeleteThis@pobox.com>
wrote:

>1. Open /Applications/Utilities/Console.
>
>2. From the Console menu bar, select File > View System Log.
>
>3. From the Console menu bar, select File > View Console Log.

What's the best way to get authorization to read this log?
 >> Stay informed about: Boot time 

In article <iaea041704qsu3nsehmfdt9krp9esu1opb.TakeThisOut@4ax.com>,
Howard Brazee <howard.TakeThisOut@brazee.net> wrote:

> On Mon, 14 Apr 2008 18:22:40 -0500, Jolly Roger <jollyroger.TakeThisOut@pobox.com>
> wrote:
>
> >1. Open /Applications/Utilities/Console.
> >
> >2. From the Console menu bar, select File > View System Log.
> >
> >3. From the Console menu bar, select File > View Console Log.
>
> What's the best way to get authorization to read this log?

Which? You should be able to view the console log.

I'm not sure about the *best* wat, but to view the system log from a
non-administrator account, you can:

1. In a terminal window use 'su' to switch to an administrator account,
then view /var/log/system.log with command-line tools (cat, tail, more,
and so on).

2. In a terminal window use 'su' to switch to an administrator account,
then temporarily launch the Console application with elevated privileges
using this command:

sudo /Applications/Utilities/Console.app/Contents/MacOS/Console

I usually do #1, but I'm very familiar with, and used to, the command
line. YMMV.

--
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR
 >> Stay informed about: Boot time 

On Tue, 15 Apr 2008 20:00:26 -0500, Jolly Roger <jollyroger RemoveThis @pobox.com>
wrote:


>I'm not sure about the *best* wat, but to view the system log from a
>non-administrator account, you can:
>
>1. In a terminal window use 'su' to switch to an administrator account,
>then view /var/log/system.log with command-line tools (cat, tail, more,
>and so on).
>
>2. In a terminal window use 'su' to switch to an administrator account,
>then temporarily launch the Console application with elevated privileges
>using this command:
>
> sudo /Applications/Utilities/Console.app/Contents/MacOS/Console
>
>I usually do #1, but I'm very familiar with, and used to, the command
>line. YMMV.

I tried this:

Last login: Sun Apr 13 18:56:05 on console
Howard-Brazees-Computer:~ HBrazee$ sudo
/Applications/Utilities/Console.app/Contents/MacOS/Console
Password:
HBrazee is not in the sudoers file. This incident will be reported.
Howard-Brazees-Computer:~ HBrazee$ postdrop: warning: unable to look
up public/pickup: No such file or directory
 >> Stay informed about: Boot time 

In article <8aka04pvlteeci24aletitta768fvvnlg4 RemoveThis @4ax.com>,
Howard Brazee <howard RemoveThis @brazee.net> wrote:

> On Tue, 15 Apr 2008 20:00:26 -0500, Jolly Roger <jollyroger RemoveThis @pobox.com>
> wrote:
>
>
> >I'm not sure about the *best* wat, but to view the system log from a
> >non-administrator account, you can:
> >
> >1. In a terminal window use 'su' to switch to an administrator account,
> >then view /var/log/system.log with command-line tools (cat, tail, more,
> >and so on).
> >
> >2. In a terminal window use 'su' to switch to an administrator account,
> >then temporarily launch the Console application with elevated privileges
> >using this command:
> >
> > sudo /Applications/Utilities/Console.app/Contents/MacOS/Console
> >
> >I usually do #1, but I'm very familiar with, and used to, the command
> >line. YMMV.
>
> I tried this:
>
> Last login: Sun Apr 13 18:56:05 on console
> Howard-Brazees-Computer:~ HBrazee$ sudo
> /Applications/Utilities/Console.app/Contents/MacOS/Console
> Password:
> HBrazee is not in the sudoers file. This incident will be reported.
> Howard-Brazees-Computer:~ HBrazee$ postdrop: warning: unable to look
> up public/pickup: No such file or directory

The instructions were:

"In a terminal window use 'su' to switch to an administrator account,":

su admin_short_name

"then temporarily launch the Console application with elevated
privileges using this command:"

sudo /Applications/Utilities/Console.app/Contents/MacOS/Console

--
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR
 >> Stay informed about: Boot time 

On Tue, 15 Apr 2008 20:57:50 -0500, Jolly Roger <jollyroger DeleteThis @pobox.com>
wrote:

>The instructions were:
>
>"In a terminal window use 'su' to switch to an administrator account,":
>
> su admin_short_name
>
>"then temporarily launch the Console application with elevated
>privileges using this command:"
>
> sudo /Applications/Utilities/Console.app/Contents/MacOS/Console

Ahh, I understand now: (It asked for my password twice):

Last login: Tue Apr 15 19:37:30 on ttys000
Howard-Brazees-Computer:~ HBrazee$ su admin
Password:
bash-3.2$ sudo
/Applications/Utilities/Console.app/Contents/MacOS/Console

WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.

To proceed, enter your password, or type Ctrl-C to abort.

Password:


======
4/15/08 4:55:38 AM com.apple.backupd[96998] Found partially deleted
backup - trying again to delete: 2008-04-14-025540
4/15/08 5:41:55 AM [0x0-0x1dc1dc].com.parallels.desktop[3844]
QFSFileEngine::open: No file name specified
4/15/08 7:35:55 AM com.apple.launchd[1] (org.samba.smbd[3147]) Stray
process with PGID equal to this dead job: PID 3167 PPID 1 smbd
4/15/08 8:55:38 AM com.apple.backupd[31736] Found partially deleted
backup - trying again to delete: 2008-04-14-065551
4/15/08 11:02:02 AM Backup[49714] *** -[NSConditionLock dealloc]: lock
(<NSConditionLock: 0x5ca9f0> '(null)') deallocated while still in use
4/15/08 11:02:02 AM Backup[49714] *** Break on _NSLockError() to
debug.
4/15/08 11:02:07 AM Backup[49714] backup reference was nil for
(0x183ca280)
/Users/HBrazee/Library/Preferences/com.apple.iCal.helper.plist
4/15/08 1:55:37 PM com.apple.backupd[75008] Found partially deleted
backup - trying again to delete: 2008-04-14-115554
4/15/08 5:05:12 PM [0x0-0x262262].com.parallels.desktop[2545]
QFSFileEngine::open: No file name specified
4/15/08 5:05:28 PM SystemUIServer[2583] found device
4/15/08 6:04:00 PM [0x0-0x275275].com.parallels.desktop[11082]
QFSFileEngine::open: No file name specified
4/15/08 6:06:19 PM [0x0-0x279279].com.parallels.desktop[11408]
QFSFileEngine::open: No file name specified
4/15/08 6:45:31 PM [0x0-0x284284].com.parallels.desktop[17052]
QFSFileEngine::open: No file name specified
4/15/08 7:07:24 PM Spotlight[1125]
/SourceCache/Spotlight/Spotlight-398.7/menu/Application/../Models/MDQueryWorker.m
-[MDQueryWorker startQuery:withFlags:] Can't execute query '(* =
"t*"cdw || kMDItemTextContent = "t*"cdw)'
4/15/08 7:07:47 PM FileSyncAgent[1829] LOCK /.FileSync (FAILED),
httpStatusCode:-1, errorType:100 (domain=DMGeneralErrorDomain,
code=100), transactionState:5,
txnId:6604AF41-69A0-4040-8798-4CB39A447C2E, auto-retries=0,
manual-retries=0
 >> Stay informed about: Boot time