/usr/sbin/update VS. auto sleep

Hi all,
After having tried ALL (believe me...) hints first I finally discovered the reason my iMac G5 (10.4.4) refuses to autosleep after inactivity. Well, sort of.
There is a process "update", started by "initd" via the file "/etc/rc" which contains the line "/usr/sbin/update". (See man pages for details on that.) Using "fs_usage" I discovered it repeatedly killed writes data to the disk which prevents autosleep. With the update process my system can sleep now.
However, the question is now "Why does update have to write at all?" In one session I disabled almost everything I found, and update still would prevent the system from autosleep. "update" is there for a reason, and I feel a little bit uncomfortable with disabling it. Is it a change in Mac OS X or is other software in my system the culprit? Any other hints?
Regards, Uwe

Hi V.K.,
in the recent days I tried a lot of things (there are also other threads about the auto sleep problem where differnt reasons are being discussed).
I don't think there exists "the one and only" reason for Macs' insomnia. But it looks like in most cases running processes disturb the auto sleep.
I recognized my Mac's problem is user-indepedent. Therefore a "global process" must have been the trouble maker.
It might be the case that the ntpd settings have been corrupted (is that possible? To be honest, I don't know.) It might also have been a problem with Little Snitch. I reset LS's rules recently and had to allow the ntpd access again. In this time period I recognized the auto sleep problems but I don't know if there is a correlation between these processes.
Nevertheless De- and Reactivation of ntpd solved the issue for me.
BR
bruegge

Similar Messages

/usr/sbin/update Lossage After 10.4.3 install

I just moved from 10.3.9 to 10.4.3 on my G5 (dual, 2.0ghz; I used CCC to clone my 10.3.9 boot disk to a firewire drive and did a clean install. I migrated applications and user settings only. The install was of 10.4 and I immediately did a software update to 10.4.3 using the Combo update. Relatively immediately, my console started to get this message:
Jan 1 17:42:43 Duende /usr/sbin/update: FIXME: IOUnserialize has detected a string that is not valid UTF-8, " C˚^?¸?¸?¸?˝_¸/¯'‡ ".
This repeats every 30 seconds because this (update) is the daemon that writes the internal file system cache back to memory (every 30 seconds). Looking at the string by copying and pasting to the terminal, it is:
" C\313\232^?\302\270?\302\270?\302\270?\313\235_\302\270/\302\257'\342\200\241 "
(I'm supposing this is some unicode string, but I don't know whether it's supposed to be a file name or some internal structure or what.)
My PB running 10.4.3 with roughly a clone of the above system doesn't have the problem.
I did the usual:
* disk utility
* fsck -fy (from safe-mode boot)
Initially, Disk Utility reported 2 "illegal names" which it fixed when booted from the install DVD. (I even tried the idea I read of it being wacky file names in the Adobe CS2 Legal directories and deleting the wacky ones).
The system appears to run ok otherwise, so the real problem I guess is the size of the logs and the messiness of looking for other stuff in them.
Any ideas?
-rpg-
Dual G5 2ghz Mac OS X (10.4.3) 8gb ram, 2 250 gb ATA drives
Dual G5 2ghz Mac OS X (10.4.3) 8gb ram, 2 250 gb ATA drives

When the Migration Assistant (which I think is what the Setup Assistant uses) asked me on first boot in 10.4 whether I wanted to migrate from an existing computer, it found the firewire disk I had cloned to. As best I know, Target Disk Mode just makes the other computer a firewire drive.
Also, since your note, I booted from the firewire clone of 10.3.9 and it worked just fine. So, I think this is not the problem.
I think it would be easier to somehow figure out where the bad string is coming from. I'm guessing it's a unicode filename that is not UTF-8, just like it says. There seems to be a lot of non-Roman file names around, and I've seen threads where Adobe CS2 has created some some have caused problems for Tiger, so I'm guess it's a similar thing.
The logs give a hint, the string is this:
C˚^?¸?¸?¸?˝_¸/¯'‡
But this is a mapping from what the string really is to what can be represented in the log.
However, if after a while I can't figure it out, I'll do another erase and install and reload things by hand. What makes me hesitate is that I have a wiki which is kind of a mess to install afresh.

Different /bin /sbin /usr/sbin update issue

Someone on IRC just brought this one up. He needs to update a VPS image from 2012.07; it's past the lib->usr/lib update. It needs to update glibc, but glibc currently requires filesystem >= 2013.01. Since filesystem is ignored, this is a problem. Only suggestion I could come up with is to use the ARM to update to a version in Feb or Mar, then update from there. Anyone have a better idea?

Okay, I give no guarantees, but this may or may not work:
pacman -Su -d --ignore filesystem
This will leave the system in a somewhat unusable state, because the newer glibc needs the /lib symlink in filesystem. In particular, most (if not all) post_install scripts will fail during this update, so look out for manually fixing breakage (I omitted the --ignore bash, since the glibc update will break bash anyway) - especially your initramfs will need to be regenerated once you are finished. You can then run
/usr/lib/ld-2.17.so pacman -Su
to upgrade filesystem. Beware that calling the dynamic loader is the only way to run any binaries in this situation.
The suggested solution of upgrading filesystem to 2013.03.something seems cleaner than mine in any case.
Last edited by brain0 (2013-06-04 14:08:39)

Auto-sleep won't work when web pages auto-refresh

Dear Apple,
Around 4 years ago, I noticed that my computer stopped going to sleep. I first noticed it shortly after adopting Gmail for my email platform and was subsequently able to isolate the issue down to Gmail and other websites, such as Huffington Post, which auto-refresh. Apparently, any website that auto-refreshes at shorter intervals than the auto-sleep is set to kick in, prevent the computer's auto-sleep function from activating.
I have spoken at length with AppleCare about this issue and understand that this is "by design." For instance, we wouldn't want the computer to constantly go to sleep while watching a movie or downloading and conversely, if we are actively working at our computers it's nice that Gmail auto-refreshes and keeps us appraised of incoming mail. However, since the vast majority of users now leave their browsers with multiple tabs open and due to the fact that more and more websites now auto-refresh, the auto-sleep function has become outdated and non-functional. While users can always manually put their computers to sleep, everyone at some time or another forgets to do so. This is exactly why computers are supposed to auto-sleep in the first place. Aggregated across millions of users, this results in a huge waste of electricity.
I've been writing/calling Apple (through AppleCare and the online feedback form) about this issue for 4 years now. I keep hoping that with each operating system release, some sort of "smart auto-sleep" function will be incorporated that will recognize when websites auto-refresh and still allow auto-sleep to kick in. Unfortunately, this does not appear to be the case in Lion.
I work in the energy efficiency field, specifically in lighting, and care deeply about this issue. I consider Apple to be an industry leader on this issue as well. I'm not familiar with the technical side of this issue, but I assume that with the right type of programming, the operating system could override a webpage's auto-update feature and activate auto-sleep, while not interfering with functions where a user would not want the computer to go to sleep, such as watching a movie. With Lion, Apple has focused its energy on making the computer adjust to the user,rather than the user adjusting to the computer. Yet, in this case, it appears to be the other way around.
It is time for Apple to update the auto-sleep function so that it takes into account websites that auto-refresh. When I set my computer to auto-sleep after so many minutes, I want it to do so, regardless of whether I have a browser with auto-updating websites open. Apple must take this issue seriously, as the wasted electricity is too important to ignore any longer.
Sincerely,
An Energy-Conscious User

I am obviously talking to Apple AND I posted this letter here, because a lot users seem confused about why their computers won't sleep. Even most AppleCare reps are confused. In the past, I couldn't find much in the way of explanations pointing to this issue, so I thought I post it here in case other people are looking for an explanation.
The auto-sleep function was built before websites auto-updated and needs to be updated to accomodate them. For the average user, it doesn't make sense for the computer not to sleep just because Gmail is open. Just because some website auto-refreshes in my browser, doesn't mean I never want my computer to sleep. By the same token, if I wanted to turn off auto-sleep I could easily do so from within Energy Saver Preferences. The two should be independent, so the user has the choice.
Why should I have to close my browser every time I walk away from my computer in order for it to sleep? I've acknowledged that in certain circumstance it makes sense for the computer not to auto-sleep: watching a movie, uploading, etc, but Apple has already accounted for those instances because the computer does not auto-sleep when those programs are running. All I'm suggesting is making the auto-sleep mechanism more sophisticated so that it isn't overridden by websites auto-refreshing.
Why the negative attitude, dwb? Based on the amount of time you spend in these discussion forums, you obviously never turn your computer off, so this doesn't really affect you. Maybe it's time to step outside and get some fresh air?

Auto Sleep broken by ATI Firmware update?

Since the ATI firmware update for my Alum 24" iMac 2.4 GHz, the auto sleep function is no longer working. I can sleep the computer manually via the apple menu, but the auto sleep controlled from the energy saver panel in system preferences never seems to kick in.
I tried trashing the plist for energy management. Tried un-checking "wake when modem detects a ring", "wake for Ethernet administrator access" boxes, but no dice.
Is anyone else out there facing a similar issue, or have a solution?

By retracing my steps, I began removing items that had been added before the restart which was required by the firmware update. There was a widget from appleinsider.com that I deleted, and auto sleep now functions normally. Curiously, the same widget is on my iBook G4 running Leopard 10.5.1 with no conflicts.
I think the key is that whatever request the widget was making was preventing the autosleep, and that it had not developed into a problem until after the restart following the update.
If others are having an issue, don't forget to check your widgets.

Mac pro crashes about every hour since updating to 10.7.4. Seems to be /usr/sbin/automount. Can anyone tell me what's going on? .crash attached

Process:
automount [303]
Path:
/usr/sbin/automount
Identifier:
automount
Version:
Code Type:
X86-64 (Native)
Parent Process: autofsd [91]
Date/Time:
2012-07-09 12:22:09.831 -0600
OS Version:
Mac OS X 10.7.4 (11E53)
Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
Assertion failed: (strlcat((mntops_out), (","), (optlen)) < (optlen)), function process_fstab_mntopts, file /SourceCache/autofs/autofs-207.1/automountlib/ns_fstab.c, line 171.
objc[303]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib
0x00007fff8c601ce2 __pthread_kill + 10
1   libsystem_c.dylib
0x00007fff879dc7d2 pthread_kill + 95
2   libsystem_c.dylib
0x00007fff879cda7a abort + 143
3   libsystem_c.dylib
0x00007fff87a005de __assert_rtn + 146
4   automount
0x0000000102a41e21 0x102a3b000 + 28193
5   automount
0x0000000102a41f22 0x102a3b000 + 28450
6   automount
0x0000000102a4053a 0x102a3b000 + 21818
7   automount
0x0000000102a42468 0x102a3b000 + 29800
8   automount
0x0000000102a3cd1f 0x102a3b000 + 7455
9   automount
0x0000000102a3c5d0 0x102a3b000 + 5584
Thread 1:
0   libsystem_kernel.dylib
0x00007fff8c602192 __workq_kernreturn + 10
1   libsystem_c.dylib
0x00007fff879dc594 _pthread_wqthread + 758
2   libsystem_c.dylib
0x00007fff879ddb85 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib
0x00007fff8c6027e6 kevent + 10
1   libdispatch.dylib
0x00007fff8bccf78a _dispatch_mgr_invoke + 923
2   libdispatch.dylib
0x00007fff8bcce31a _dispatch_mgr_thread + 54
Thread 3:
0   libsystem_kernel.dylib
0x00007fff8c602192 __workq_kernreturn + 10
1   libsystem_c.dylib
0x00007fff879dc594 _pthread_wqthread + 758
2   libsystem_c.dylib
0x00007fff879ddb85 start_wqthread + 13
Thread 4:
0   libsystem_kernel.dylib
0x00007fff8c602192 __workq_kernreturn + 10
1   libsystem_c.dylib
0x00007fff879dc594 _pthread_wqthread + 758
2   libsystem_c.dylib
0x00007fff879ddb85 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff62637dc8 rdx: 0x0000000000000000
rdi: 0x0000000000000303 rsi: 0x0000000000000006 rbp: 0x00007fff62637df0 rsp: 0x00007fff62637dc8
   r8: 0x00007fff76848fb8   r9: 0x00000000000000ab r10: 0x00007fff8c601d0a r11: 0xffffff80002da8d0
r12: 0x0000000102a449b8 r13: 0x0000000102ab6000 r14: 0x00007fff7684b960 r15: 0x0000000102a449ce
rip: 0x00007fff8c601ce2 rfl: 0x0000000000000246 cr2: 0x0000000102ab6000
Logical CPU: 0
Binary Images:
0x102a3b000 -
0x102a45fff automount (??? - ???) <E1A801C7-AA80-30A4-A164-E86E07CF94E8> /usr/sbin/automount
0x7fff6263b000 -
0x7fff6266fbaf dyld (195.6 - ???) <0CD1B35B-A28F-32DA-B72E-452EAD609613> /usr/lib/dyld
0x7fff8665a000 -
0x7fff86668ff7 libkxld.dylib (??? - ???) <C2FC894F-3716-32C3-967E-6AD5E2697045> /usr/lib/system/libkxld.dylib
0x7fff86669000 -
0x7fff86699ff7 com.apple.DictionaryServices (1.2.1 - 158.2) <3FC86118-7553-38F7-8916-B329D2E94476> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x7fff8669a000 -
0x7fff8671dfef com.apple.Metadata (10.7.0 - 627.32) <38735923-2EB5-3133-BE36-BDD65A7E47DB> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x7fff86783000 -
0x7fff8681dff7 com.apple.SearchKit (1.4.0 - 1.4.0) <4E70C394-773E-3A4B-A93C-59A88ABA9509> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x7fff8684f000 -
0x7fff8688efff com.apple.AE (527.7 - 527.7) <B82F7ABC-AC8B-3507-B029-969DD5CA813D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x7fff868f0000 -
0x7fff869f2fff libxml2.2.dylib (10.3.0 - compatibility 10.0.0) <AFBB22B7-07AE-3F2E-B88C-70BEEBFB8A86> /usr/lib/libxml2.2.dylib
0x7fff86da9000 -
0x7fff86de4fff libsystem_info.dylib (??? - ???) <35F90252-2AE1-32C5-8D34-782C614D9639> /usr/lib/system/libsystem_info.dylib
0x7fff87319000 -
0x7fff87635fff com.apple.CoreServices.CarbonCore (960.24 - 960.24) <6F99A26B-788F-37B9-860F-508906EC06D7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x7fff876a1000 -
0x7fff87714fff libstdc++.6.dylib (52.0.0 - compatibility 7.0.0) <6BDD43E4-A4B1-379E-9ED5-8C713653DFF2> /usr/lib/libstdc++.6.dylib
0x7fff87923000 -
0x7fff87936ff7 libCRFSuite.dylib (??? - ???) <034D4DAA-63F0-35E4-BCEF-338DD7A453DD> /usr/lib/libCRFSuite.dylib
0x7fff8798c000 -
0x7fff87a69fef libsystem_c.dylib (763.13.0 - compatibility 1.0.0) <41B43515-2806-3FBC-ACF1-A16F35B7E290> /usr/lib/system/libsystem_c.dylib
0x7fff87d71000 -
0x7fff87d73fff libquarantine.dylib (36.6.0 - compatibility 1.0.0) <0EBF714B-4B69-3E1F-9A7D-6BBC2AACB310> /usr/lib/system/libquarantine.dylib
0x7fff87e47000 -
0x7fff87e74fe7 libSystem.B.dylib (159.1.0 - compatibility 1.0.0) <7BEBB139-50BB-3112-947A-F4AA168F991C> /usr/lib/libSystem.B.dylib
0x7fff87f31000 -
0x7fff87f32fff liblangid.dylib (??? - ???) <CACBE3C3-2F7B-3EED-B50E-EDB73F473B77> /usr/lib/liblangid.dylib
0x7fff87fa2000 -
0x7fff87fa4fff com.apple.TrustEvaluationAgent (2.0 - 1) <1F31CAFF-C1C6-33D3-94E9-11B721761DDF> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
0x7fff88a50000 -
0x7fff88a5efff com.apple.NetAuth (1.0 - 3.0) <F384FFFD-70F6-3B1C-A886-F5B446E456E7> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff88b11000 -
0x7fff88c18fe7 libsqlite3.dylib (9.6.0 - compatibility 9.0.0) <EE02BB01-64C9-304D-9719-A35F5CD6D04C> /usr/lib/libsqlite3.dylib
0x7fff88fe1000 -
0x7fff88fe1fff com.apple.CoreServices (53 - 53) <043C8026-8EDD-3241-B090-F589E24062EF> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff8912c000 -
0x7fff89445fff com.apple.Foundation (6.7.2 - 833.25) <22AAC369-B63C-3C55-8AC6-C3ECBA44DA7B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff89487000 -
0x7fff89593fff libcrypto.0.9.8.dylib (44.0.0 - compatibility 0.9.8) <3A8E1F89-5E26-3C8B-B538-81F5D61DBF8A> /usr/lib/libcrypto.0.9.8.dylib
0x7fff89c70000 -
0x7fff89e44ff7 com.apple.CoreFoundation (6.7.2 - 635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff8a1fe000 -
0x7fff8a21aff7 com.apple.GenerationalStorage (1.0 - 126.1) <509F52ED-E54B-3FEF-B3C2-759387B826E6> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
0x7fff8a227000 -
0x7fff8a231ff7 liblaunch.dylib (392.38.0 - compatibility 1.0.0) <6ECB7F19-B384-32C1-8652-2463C1CF4815> /usr/lib/system/liblaunch.dylib
0x7fff8a286000 -
0x7fff8a28afff libmathCommon.A.dylib (2026.0.0 - compatibility 1.0.0) <FF83AFF7-42B2-306E-90AF-D539C51A4542> /usr/lib/system/libmathCommon.A.dylib
0x7fff8a576000 -
0x7fff8a57cfff com.apple.DiskArbitration (2.4.1 - 2.4.1) <CEA34337-63DE-302E-81AA-10D717E1F699> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff8a57d000 -
0x7fff8a57efff libDiagnosticMessagesClient.dylib (??? - ???) <3DCF577B-F126-302B-BCE2-4DB9A95B8598> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff8aa06000 -
0x7fff8aa07ff7 libsystem_blocks.dylib (53.0.0 - compatibility 1.0.0) <8BCA214A-8992-34B2-A8B9-B74DEACA1869> /usr/lib/system/libsystem_blocks.dylib
0x7fff8aa1d000 -
0x7fff8aa6bfff libauto.dylib (??? - ???) <D8AC8458-DDD0-3939-8B96-B6CED81613EF> /usr/lib/libauto.dylib
0x7fff8b6ff000 -
0x7fff8b74bff7 com.apple.SystemConfiguration (1.11.3 - 1.11) <0A7F1982-B4EA-3424-A0C7-FE46C6224F03> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff8b74c000 -
0x7fff8b74dfff libdnsinfo.dylib (395.11.0 - compatibility 1.0.0) <853BAAA5-270F-3FDC-B025-D448DB72E1C3> /usr/lib/system/libdnsinfo.dylib
0x7fff8b74e000 -
0x7fff8b756fff libsystem_dnssd.dylib (??? - ???) <D9BB1F87-A42B-3CBC-9DC2-FC07FCEF0016> /usr/lib/system/libsystem_dnssd.dylib
0x7fff8b941000 -
0x7fff8b947fff libmacho.dylib (800.0.0 - compatibility 1.0.0) <D86F63EC-D2BD-32E0-8955-08B5EAFAD2CC> /usr/lib/system/libmacho.dylib
0x7fff8bccc000 -
0x7fff8bcdafff libdispatch.dylib (187.9.0 - compatibility 1.0.0) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
0x7fff8c5eb000 -
0x7fff8c60bfff libsystem_kernel.dylib (1699.26.8 - compatibility 1.0.0) <1DDC0B0F-DB2A-34D6-895D-E5B2B5618946> /usr/lib/system/libsystem_kernel.dylib
0x7fff8cc33000 -
0x7fff8ccd4ff7 com.apple.LaunchServices (480.33 - 480.33) <45EF2044-3396-3910-9B5B-C8F7777D5F56> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x7fff8cd86000 -
0x7fff8cd8bfff libpam.2.dylib (3.0.0 - compatibility 3.0.0) <D952F17B-200A-3A23-B9B2-7C1F7AC19189> /usr/lib/libpam.2.dylib
0x7fff8d8d9000 -
0x7fff8d8ebff7 libz.1.dylib (1.2.5 - compatibility 1.0.0) <30CBEF15-4978-3DED-8629-7109880A19D4> /usr/lib/libz.1.dylib
0x7fff8d920000 -
0x7fff8d98bff7 com.apple.framework.IOKit (2.0 - ???) <6C604894-7F61-3130-8499-20791D14577F> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff8db1b000 -
0x7fff8db46ff7 libxslt.1.dylib (3.24.0 - compatibility 3.0.0) <E71220D3-8015-38EC-B97D-7FDB383C2BDC> /usr/lib/libxslt.1.dylib
0x7fff8e15b000 -
0x7fff8e15ffff libdyld.dylib (195.5.0 - compatibility 1.0.0) <F1903B7A-D3FF-3390-909A-B24E09BAD1A5> /usr/lib/system/libdyld.dylib
0x7fff8e2a6000 -
0x7fff8e2b1ff7 libc++abi.dylib (14.0.0 - compatibility 1.0.0) <8FF3D766-D678-36F6-84AC-423C878E6D14> /usr/lib/libc++abi.dylib
0x7fff8e2c0000 -
0x7fff8e2cdff7 libbz2.1.0.dylib (1.0.5 - compatibility 1.0.0) <8EDE3492-D916-37B2-A066-3E0F054411FD> /usr/lib/libbz2.1.0.dylib
0x7fff8e2d4000 -
0x7fff8e2d9fff libcompiler_rt.dylib (6.0.0 - compatibility 1.0.0) <98ECD5F6-E85C-32A5-98CD-8911230CB66A> /usr/lib/system/libcompiler_rt.dylib
0x7fff8e323000 -
0x7fff8e335ff7 libbsm.0.dylib (??? - ???) <349BB16F-75FA-363F-8D98-7A9C3FA90A0D> /usr/lib/libbsm.0.dylib
0x7fff8e3b5000 -
0x7fff8e3b9fff libutil.dylib (??? - ???) <28672328-B738-38CE-B231-8A93CA6E6EA4> /usr/lib/libutil.dylib
0x7fff8e3e3000 -
0x7fff8e3e8fff com.apple.OpenDirectory (10.7 - 146) <A674AB55-6E3D-39AE-9F9B-9865D0193020> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff8f3fe000 -
0x7fff8f403fff libcache.dylib (47.0.0 - compatibility 1.0.0) <B7757E2E-5A7D-362E-AB71-785FE79E1527> /usr/lib/system/libcache.dylib
0x7fff8f636000 -
0x7fff8f64dfff com.apple.CFOpenDirectory (10.7 - 144) <9709423E-8484-3B26-AAE8-EF58D1B8FB3F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x7fff8f917000 -
0x7fff8f9fbe5f libobjc.A.dylib (228.0.0 - compatibility 1.0.0) <871E688B-CF57-3BC7-80D6-F6476DFF109B> /usr/lib/libobjc.A.dylib
0x7fff8ff71000 -
0x7fff90173fff libicucore.A.dylib (46.1.0 - compatibility 1.0.0) <38CD6ED3-C8E4-3CCD-89AC-9C3198803101> /usr/lib/libicucore.A.dylib
0x7fff90174000 -
0x7fff90258fff com.apple.CoreServices.OSServices (478.46 - 478.46) <70BEE269-8F4D-3FDC-B1AD-A591C0CB37E5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff9067d000 -
0x7fff906bfff7 libcommonCrypto.dylib (55010.0.0 - compatibility 1.0.0) <A5B9778E-11C3-3F61-B740-1F2114E967FB> /usr/lib/system/libcommonCrypto.dylib
0x7fff906c0000 -
0x7fff906c1ff7 libremovefile.dylib (21.1.0 - compatibility 1.0.0) <739E6C83-AA52-3C6C-A680-B37FE2888A04> /usr/lib/system/libremovefile.dylib
0x7fff9097e000 -
0x7fff9098dff7 libxar-nossl.dylib (??? - ???) <A6ABBFB9-E4ED-38AD-BBBB-F9958B9CEFB5> /usr/lib/libxar-nossl.dylib
0x7fff90d1a000 -
0x7fff90d1bfff libunc.dylib (24.0.0 - compatibility 1.0.0) <C67B3B14-866C-314F-87FF-8025BEC2CAAC> /usr/lib/system/libunc.dylib
0x7fff90d1c000 -
0x7fff91005ff7 com.apple.security (7.0 - 55148.1) <E9C46204-1336-3D90-BC67-5162FC7079D2> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff91c39000 -
0x7fff91ca9fff com.apple.datadetectorscore (3.0 - 179.4) <9C01D16F-75A9-3BDD-B91A-F0F32261A2E7> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x7fff91d26000 -
0x7fff91d9cfff libc++.1.dylib (28.1.0 - compatibility 1.0.0) <DA22E4D6-7F20-3BEA-9B89-2FBA735C2EE1> /usr/lib/libc++.1.dylib
0x7fff926a1000 -
0x7fff926befff libxpc.dylib (77.19.0 - compatibility 1.0.0) <9F57891B-D7EF-3050-BEDD-21E7C6668248> /usr/lib/system/libxpc.dylib
0x7fff926bf000 -
0x7fff926c0ff7 libsystem_sandbox.dylib (??? - ???) <96D38E74-F18F-3CCB-A20B-E8E3ADC4E166> /usr/lib/system/libsystem_sandbox.dylib
0x7fff926c1000 -
0x7fff92828fff com.apple.CFNetwork (520.4.3 - 520.4.3) <31D7A595-375E-341A-8E97-21E73CC62E4A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x7fff931d3000 -
0x7fff931dcff7 libsystem_notify.dylib (80.1.0 - compatibility 1.0.0) <A4D651E3-D1C6-3934-AD49-7A104FD14596> /usr/lib/system/libsystem_notify.dylib
0x7fff931de000 -
0x7fff931defff libkeymgr.dylib (23.0.0 - compatibility 1.0.0) <61EFED6A-A407-301E-B454-CD18314F0075> /usr/lib/system/libkeymgr.dylib
0x7fff931df000 -
0x7fff931e6fff libcopyfile.dylib (85.1.0 - compatibility 1.0.0) <172B1985-F24A-34E9-8D8B-A2403C9A0399> /usr/lib/system/libcopyfile.dylib
0x7fff9322c000 -
0x7fff93232ff7 libunwind.dylib (30.0.0 - compatibility 1.0.0) <1E9C6C8C-CBE8-3F4B-A5B5-E03E3AB53231> /usr/lib/system/libunwind.dylib
0x7fff93233000 -
0x7fff9323afff com.apple.NetFS (4.0 - 4.0) <B9F41443-679A-31AD-B0EB-36557DAF782B> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff9361f000 -
0x7fff93624ff7 libsystem_network.dylib (??? - ???) <5DE7024E-1D2D-34A2-80F4-08326331A75B> /usr/lib/system/libsystem_network.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 21
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=75.1M resident=35.4M(47%) swapped_out_or_unallocated=39.7M(53%)
Writable regions: Total=72.6M written=572K(1%) resident=880K(1%) swapped_out=0K(0%) unallocated=71.8M(99%)
REGION TYPE
VIRTUAL
===========
=======
MALLOC
62.3M
MALLOC guard page
32K
STACK GUARD
56.0M
Stack
10.0M
VM_ALLOCATE
40K
__DATA
3036K
__LINKEDIT
47.7M
__TEXT
27.4M
__UNICODE
544K
shared memory
12K
===========
=======
TOTAL
207.1M

autofsd: /usr/sbin/automount terminated...: Apple Support Communities
NFS not mounted (Lion): Apple Support Communities

10.5.2 combo update - auto sleep no longer works

Since performing this upgrade yesterday, auto sleep no longer functions. The screen saver blanks the screen at the correct time but that's as far as it goes.
I've repaired permissions, tried resetting the Energ Saver defaults, resetting the SMC and deleting the com.apple.PowerManagement.plist file and am no further forward.
Is anyone else experiencing auto sleep issues after the 10.5.2 upgrade?

Okay. I think I've solved auto-sleep. At least for my system. It requires going into to terminal and changing the minutes of 'disksleep'. It's very easy and non-invasive. First check your pmset settings in termnal by typing: pmset -g
You should see something like this:
Active Profiles:
Battery Power -1
AC Power -1*
Currently in use:
sleep 10
sms 1
displaysleep 5
hibernatefile /var/vm/sleepimage
halfdim 1
lidwake 1
ttyskeepawake 1
acwake 0
autorestart 0
hibernatemode 3
Hibernate Free Ratio 5
womp 0
disksleep 12
First, you want to be sure your hibernatemode is set at 3 (the default in Leopard). If it isn't you can change it by typing: sudo pmset -a hibernatemode 3
This is the command that you will now use to change what I think fixes auto-sleep. If you notice 'sleep' and 'displaysleep' are set at the minutes you have set them at in your Energy Preferences (5 and 10 in my example above). You can just leave these settings. 'Disksleep' is the command that should tell your computer to hibernate (auto-sleep) and it is by default set at whatever your 'sleep' setting is. What I did was change 'disksleep' to 12 (again the command in terminal for this would be: sudo pmset -a disksleep 12).
My theory is that by seperating the 'disksleep' setting from the 'sleep' setting by a couple of minutes, the command to hibernate is somehow stronger or clearer. At any rate it worked for me when nothing else would. If for some reason the computer doesn't hibernate at exactly 12 minutes, give it an hour and see if it does sleep in that time. You can test this with AC power and then with battery. Sometimes the AC is easier to get auto-sleep working for some reason.
If you want to save your pmset settings just copy your pmset -g query in a text file and you can revert to whatever your default was by then using the sudo pmset -a command.
The first step before you change the pmset settings is to make sure that no third party software is keeping your system awake. Console activity should display that, whether it's a program or a widget. Obviously you need to either uninstall or deactivate the offending program or widget before moving forward. Also make sure you've completely followed all the previous suggestions for troubleshooting lack of auto-sleep (pmu, pram, safe mode resetting... de-selecting preferences (for example: uncheck all boxes in advanced settings for Bluetooth if you use bluetooth devices or uncheck Wake for Ethernet network administrator access in Energy Preferences Adaptor Options).
Hope this helps someone else. I've been struggling with this issue since leopard came out. And through trial and error worked my way up to this. Let me know if it works for you.

Correlation: no auto sleep & console entries?

Hello.
Recently I get only very sporadic auto sleeps with my iMac (OS 10.5.6).
While looking for possible causes I found the following entry in the console (every 15 minutes):
08.01.09 12:30:25 /usr/sbin/ocspd[228] starting
08.01.09 12:45:33 /usr/sbin/ocspd[242] starting
08.01.09 13:00:40 /usr/sbin/ocspd[258] starting
08.01.09 13:15:48 /usr/sbin/ocspd[269] starting
Might this be the reason for the iMac not to go to sleep?

Hi V.K.,
in the recent days I tried a lot of things (there are also other threads about the auto sleep problem where differnt reasons are being discussed).
I don't think there exists "the one and only" reason for Macs' insomnia. But it looks like in most cases running processes disturb the auto sleep.
I recognized my Mac's problem is user-indepedent. Therefore a "global process" must have been the trouble maker.
It might be the case that the ntpd settings have been corrupted (is that possible? To be honest, I don't know.) It might also have been a problem with Little Snitch. I reset LS's rules recently and had to allow the ntpd access again. In this time period I recognized the auto sleep problems but I don't know if there is a correlation between these processes.
Nevertheless De- and Reactivation of ntpd solved the issue for me.
BR
bruegge

Dual 2.5 G5 won't auto sleep

Ever since I updated to 10.4.7, my dual G5 won't automatically sleep after any amount of time I set it to. The computer will sleep if I force it to either using the keyboard shortcut or through the Apple menu. The computer will also auto sleep in the other computer accounts on the same machine. For whatever reason, it will not auto sleep on my account. I few weeks ago, I created a brand new alias and moved all my files from my non-sleeping account to the new one. The auto sleep for for a few days before it stopped working.
I've tried trashing plists, preferences, removing USB devices, stopped file sharing, and more. I changed all my settings and active programs to exactly mirror the ones on the working account - but, nothing seems to be working.
I haven't tried flashing the PRAM yet, but I figure the problem is elsewhere since the computer will sleep on other accounts. Under my System Preferences, the extra panes I have are ATI Displays, DivX, Little Snitch, Nortorn Antivirus, Stuffit, and WMV Player. These panes also exist on the other accounts.
Anyone have any ideas what else may be causing this problem? I'm almost positive it's software related, but I don't know how to troubleshoot further given that I've already tried to make my account mirror that of a working one.
Thanks in advance.
Dual 2.5 G5 Mac OS X (10.4.7)

Well Norton is famous for causing problems for Mac users, just search, but perhaps it could be another problem.
Open the System Prefs>Energy Saver and set the auto-sleep to something really low.
Now leave the pane open and unlocked and just wait for the sleep to kick in.
Wake it up and set the time to a little bit longer, enough that you know it's not the minimum and this time close the pane.
If this fails, offload Norton and try again.
Norton has had a few application exploits, something to think about, also most anything from Microsoft seems to continously have security exploits.
Also you should be cloning your boot drive occassionally, visit Carbon Copy Cloners forums for donationware software and read the "Before you clone" in their forums.

The mysteries of auto sleep

When I purchased my iMac it came with Leopard 10.5.6 and auto sleep worked without problems, but after updating to 10.5.7 my iMac no longer went to sleep automatically and this continued after 10.5.8. Updated my iMac to Snow Leopard 10.6, everything went perfectly and to my surprise auto sleep worked absolutely perfectly, whatever I set it too. But, I updated to 10.6.1 and auto sleep has gone again. It's not a big deal, but I've been really impressed with Snow Leopard and so surprised to see this problem come back. Tried most of the suggestions that people make, without success and beyond Apple programs, have very little installed on my system. Just wondered if anyone had any brilliant ideas on this?

This is for a Mac that won't sleep.
Here is Apple's KB article HT1776 with their tips.
Mine follow;
USB devices and hubs often cause Macs to not sleep or wake quickly from sleep (notably HP printers and scanners, HP all in ones, and Cannon scanners). Disconnect all USB except for keyboard and mouse and try. If it sleeps, add one back at a time testing after each one to find the culprit.
If you've set your Mac to receive faxes, it may not be able to sleep. It might also have a damaged preferences file.
If you use your Mac for faxing, open System Preferences. click Print & Fax, click the Faxing tab, and uncheck the Receive Faxes On This Computer box.
If that doesn't work or you've never faxed on your Mac, go to Finder/Hard Drive /Library/Preferences/SystemConfiguration and delete the com.apple.PowerManagement.plist and com..apple.AutoWake.plist files (if your Mac asks, type your admin. password).
If the latter file isn't present in the folder, go to user name(probably your name)/Library/Preferences, delete the com.apple.systemuiserver.plist file, and reboot your Mac.
Hope this helps!
P.S. One member here reported this (Michael Gleason);
"I have had this problem with my IMac G5. It is surprisingly irritating. LaCie's Silverkeeper backup software was the cause. By default it gave itself permission to wake up the computer to check if a backup was needed. Do you have this or a similar program installed which has scheduled activities including wake-up permissions as an option?"
Dave Hamilton provided this link, xlr8yourmac.com, to a member, which addresses failure of deep sleep with some users that updated and added new FireWire and USB card.
Also, here is Apple KB article TA2469 about PCI cards and sleep.
tomhorvat adds this; After few days of messing around I found out that I had desktop background (wallpaper) set to change every 1 minute.
After unchecking "Change picture..." in system preferences (under Desktop/Screen saver), my powerbook went to sleep all by itself.
Tristan Currier noticed this; "I have a Canon printer(shared) and my imac would not sleep. I opened up printer/fax in system prefs and noticed it said the printer was in use when it was off. Opened up the printer queue and noticed about 7 pending documents. Deleted them all and now it sleeps.
Check the printer queue!"
Allan Jones says "sometimes there is Network activity: launch System Preferences > Energy Saver > "Options" tab and uncheck "Wake for Ethernet network administrator access."
Good Luck!  DALE

/usr/sbin/eeprom

I have re-installed Solaris 10 on an x4200, but after I finished the install I receive this errors:
SunOS Release 5.10 Version Generic_118855-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: BIOS microcode patch for AMD Athlon(tm) 64/Opteron(tm) processor
erratum 131 was not detected; updating your system's BIOS to a version
containing this microcode patch is HIGHLY recommended or erroneous system
operation may occur.
Aug 13 18:12:47 svc.startd[7]: svc:/platform/i86pc/eeprom:default: Method "/usr/sbin/eeprom -I" failed with exit status 255.
Aug 13 18:12:47 svc.startd[7]: svc:/platform/i86pc/eeprom:default: Method "/usr/sbin/eeprom -I" failed with exit status 255.
Aug 13 18:12:47 svc.startd[7]: svc:/platform/i86pc/eeprom:default: Method "/usr/sbin/eeprom -I" failed with exit status 255.
Aug 13 18:12:47 svc.startd[7]: platform/i86pc/eeprom:default failed: transitioned to maintenance (see 'svcs -xv' for details)
# svcs -xv
svc:/platform/i86pc/eeprom:default (EEPROM emulation)
State: maintenance since Thu Aug 14 14:33:57 2008
Reason: Start method failed repeatedly, last exited with status 255.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/share/man -s 1M eeprom
See: /var/svc/log/platform-i86pc-eeprom:default.log
Impact: This service is not running.
Does anyone know how to fix this issue or why this happened? I've never seen this before.
THanks
Edited by: wb on Aug 14, 2008 11:31 AM
Edited by: wb on Aug 15, 2008 5:09 AM

What is the impact and which other services are dependent on VT-x AMD in XVM? We have been using the same procedure to install Solaris 10 to all our servers, and we have never experienced this issue. Does anyone know the source of this?

IPad doesn't auto sleep

Since 2-3 updates ago, my iPad won't auto sleep, despite having it set to 10-5-2 minute auto sleep (I've tried all 3). I've seen other online posts for similar issues but no resolution. Thanks for any suggestions.

Hi ljc,
Try a reset - hold down the Home and Power buttons at the same time and continue to hold until the Silver Apple appears. Once the Home screen is back up, go in and set your Auto Lock timer to the lowest number and see if it starts working again.
Cheers,
GB

/usr/sbin/PasswordService - no more terminal windows; no ssh connections

Hi ! I'm using OS X server 10.4.6
it's the second time I see this behaviour.
A while ago I coun't connect to my server via ssh and I kept getting a
"/usr/sbin/PasswordService: Client response doesn't match what we generated". I introduced the password but the client seemed to hang after I type it.
Also I've noticed that for some reason I couln't open more terminals.
I always got [Process Completed].
I rebooted the server and everything seems ok, except the fact that when
I type "w" on a terminal, I get 29 admin entries on tty's:
p1 -> p9
pa -> pf
q0 -> q9
qa -> qf
I don't have a clue about what happened here but at least I can open more terminals, and ssh connections are ok.
Can anyone help me with is ?
Thanks !
David
This is the Exited process.crash.log
Host Name: myserver
Date/Time: 2006-05-04 16:42:29.238 +0100
OS Version: 10.4.6 (Build 8I127)
Report Version: 4
Command: Exited process
Path: Exited process
Parent: kernel_task [0]
Version: ??? (???)
PID: 1213
Thread: Unknown
Exception: EXCBADACCESS (0x0001)
Codes: KERNINVALIDADDRESS (0x0001) at 0x5f353233
(null)
Unknown thread crashed with PPC Thread State 64:
srr0: 0x0000000000098618 srr1: 0x100000000200f030 vrsave: 0x0000000000000000
cr: 0x48000242 xer: 0x0000000000000000 lr: 0x000000000008e70c ctr: 0x00000000000985fc
r0: 0x0000000000000001 r1: 0x00000000f0182480 r2: 0x00000000014bf0d4 r3: 0x0000000000000000
r4: 0x0000000000000048 r5: 0x0000000000000054 r6: 0xffffffffffffffff r7: 0x000000000000001e
r8: 0x00000000000985fc r9: 0x000000005f353237 r10: 0x00000000014bf0dc r11: 0x00000000f018248c
r12: 0x0000000090008aa0 r13: 0x00000000015e9004 r14: 0x00000000014bf0d8 r15: 0x00000000014bf0bc
r16: 0x00000001015e8f10 r17: 0x00000000018676ac r18: 0x00000000014bf0d4 r19: 0x00000000015e8f5c
r20: 0x0000000000000000 r21: 0x0000000000000000 r22: 0x0000000000000000 r23: 0x0000000000000000
r24: 0x0000000000000000 r25: 0x0000000001867778 r26: 0x0000000000000000 r27: 0x00000000015e9004
r28: 0x00000000015e9004 r29: 0x0000000000118000 r30: 0x00000000015e9004 r31: 0x000000000008c914
Binary Images Description:

/dev/zero wrote:
virusso80 wrote:I just updated the system
Please show the output of this:
tail --lines=+$(grep -on Running /var/log/pacman.log | tail -2 | head -1 | awk -F':' '{print $1}') /var/log/pacman.log
It will show the logs from your last couple of pacman updates.
Thanks for the answer. Just to be more complete I reported all the logs related to the update, in such a way to understand what happened...maybe. You'll see some errors with grep. I reinstalled grep and that error was no more there...i think:
ngoonee wrote:You're trying all the alsa-based trouble-shooting techniques while running pulse? What's pavucontrol show?
I installed pavucontrol and this is the output while playing an mp3 file:
** (pavucontrol:25504): DEBUG: Error reading config file /home/virus/.config/pavucontrol.ini: No such file or directory
** (pavucontrol:25504): DEBUG: Failed to initialize device manager extension: No such extension
** (pavucontrol:25504): DEBUG: Ignoring sink-input due to it being designated as an event and thus handled by the Event widget
... more line like this...
I don't know if it is useful but it seems that when i play something i can hear some little noise...like a mosquito.
Thanks again
Last edited by virusso80 (2012-03-02 09:35:17)

Crond error: unable to exec /usr/sbin/sendmail: cron output for user .

I have cronjobs running as a normal user.
shadyabhi@ArchLinux ~/cronjobs $ crontab -l
#CronJobs located in $HOME/cronjobs/*
0 * * * * /home/shadyabhi/cronjobs/snailmail.sh
* 5 * * * /home/shadyabhi/cronjobs/backup_pkgs.sh
* 5 * * * /home/shadyabhi/cronjobs/backup_songs.sh
shadyabhi@ArchLinux ~/cronjobs $ sudo tail -f -n 10 /var/log/crond.log
Oct 16 09:00:12 ArchLinux crond[13410]: unable to exec /usr/sbin/sendmail: cron output for user shadyabhi /home/shadyabhi/cronjobs/snailmail.sh to /dev/null
Oct 16 09:40:01 ArchLinux crond[1552]: FILE /var/spool/cron/root USER root PID 13622 job sys-hourly
Oct 16 10:00:01 ArchLinux crond[1552]: FILE /var/spool/cron/shadyabhi USER shadyabhi PID 13739 /home/shadyabhi/cronjobs/snailmail.sh
Oct 16 10:00:13 ArchLinux crond[13806]: mailing cron output for user shadyabhi /home/shadyabhi/cronjobs/snailmail.sh
Oct 16 10:00:13 ArchLinux crond[13806]: unable to exec /usr/sbin/sendmail: cron output for user shadyabhi /home/shadyabhi/cronjobs/snailmail.sh to /dev/null
Oct 16 10:40:01 ArchLinux crond[1552]: FILE /var/spool/cron/root USER root PID 14418 job sys-hourly
Oct 16 11:00:01 ArchLinux crond[1552]: FILE /var/spool/cron/shadyabhi USER shadyabhi PID 15527 /home/shadyabhi/cronjobs/snailmail.sh
Oct 16 11:00:13 ArchLinux crond[15593]: mailing cron output for user shadyabhi /home/shadyabhi/cronjobs/snailmail.sh
Oct 16 11:00:13 ArchLinux crond[15593]: unable to exec /usr/sbin/sendmail: cron output for user shadyabhi /home/shadyabhi/cronjobs/snailmail.sh to /dev/null
Oct 16 11:07:01 ArchLinux crond[1552]: reading /var/spool/cron/cron.update
^C
shadyabhi@ArchLinux ~/cronjobs $ pacman -Q | grep sendmail
sendmail 8.14.4-1
shadyabhi@ArchLinux ~/cronjobs $
Why am I getting that error?

loafer wrote:The AUR package doesn't install the sendmail binary for some reason. There are quite a few comments about this on the AUR page. I just built it myself. The sendmail binary is there in the src but it doesn't get installed as part of the package. Better ask the maintainer about why this is.
But, I have sendmail binary in /usr/sbin
shadyabhi@ArchLinux ~ $ whereis sendmail
sendmail: /usr/sbin/sendmail /usr/share/man/man1/sendmail.1.gz
shadyabhi@ArchLinux ~ $

Leopard hangs starting /usr/sbin/ocspd after both upgrade and clean install

I have a clean SuperDuper backup, so I can always go back to Tiger, but since I've paid for Leopard, it sure would be nice to run it!
I've got a MacBookPro with 4GB of RAM that's only a few months old. It has been happily running 10.4.10.
Earlier today, I tried an Upgrade to Leopard, which appeared to work, though the system would not boot. The gray screen with the Apple logo and the spinner appears, and then the spinner stops. Powering off and restarting hangs at the same place. Booting off the external drive properly boots Tiger and mounts the internal drive on the Tiger desktop, so the internal drive appears to be fine. Disk Utility says it's fine. It just hangs.
Since I have a perfect bootable backup, I go for the clean install. This first appears to work, and lets me boot Leopard. I restore Documents and Music and begin to install apps, and I notice that some apps appear to be hung. After installing each app, I run it, enter whatever license information is required and update to the latest rev, and quit it. At some point I realized that the last few apps I'd quit are still running. A quick check of top reveals that none of them are chewing up a lot of CPU, but when I quit top, I can't get back to a shell prompt, either. Opening a new Terminal tab doesn't get me to a prompt, either. I finally hold down the power key to reboot.
It hangs at the same gray screen. Disk Utility still says the disk is clean.
I use Command-V to boot in verbose mode, and I note that the last line that appears is:
/usr/sbin/ocspd[86]: starting
I've rebooted several times, and that's always the last line that displays. Apparently something has scrambled ocspd?
I'm going to try another clean install, and avoid GlowWorm FW Lite this time around. I'd installed a bunch of apps, but I think that was the first one to hang on me.
Anyone else with similar experiences? I've never had trouble with OSX upgrades before, so I'm still kinda in shock about this.

I restarted in Safe Mode (hold down shift), which did start!
I then removed GlowWorm 1.5.3beta by simpy dragging it to the trash (couldn't find an uninstaller anywhere).
Now when I boot, it still hangs, but ocspd is no longer the last message displayed. Instead, I get 'Login Windows Application Started' last sometimes, and mds complaining that there was an unclean shutdown of /.Spotlight-V100/long/path/name sometimes.
I'm trying Safe Boot again, but I'm not sure what else to try to remove! I think I'm back to Clean Install again after all.

/usr/sbin/update VS. auto sleep

Similar Messages

Maybe you are looking for