Spotlight mds bringing down system, constantly leaking RAM & disk access

Spotlight is going rampant here.
The mds (metadata server, aka Spotlight) process is constantly accessing the disk and writing some data to it, filling it until there is no space left on the device. I cannot find out what file it is writing to. I've tried with fsevener which sadly didn't help.
mds is also eating up all the CPU cycles it can get leaving my system fully loaded at all times.
The mds process is also taking up inceasingly huge amounts of memory, causing permanent swapping of memory and bringing the system to a grinding halt. (Cache Hits go down below 1%, About 250.000 pageins happen per minute.) Memory Footprint is going up to several hundred MB or real RAM.
$ vm_stat
Mach Virtual Memory Statistics: (page size of 4096 bytes)
Pages free: 53166.
Pages active: 275736.
Pages inactive: 135633.
Pages wired down: 59698.
"Translation faults": 10217862.
Pages copy-on-write: 136166.
Pages zero filled: 5983710.
Pages reactivated: 96772.
Pageins: 1236330.
Pageouts: 77113.
Object cache: 24391 hits of 1183451 lookups (2% hit rate)
(This is 95 minutes after reboot. Only running: Finder, Terminal, LaunchBar, Safari, Mail)
This bahaviour goes until the disk is full and I get a "low disk space" warning. Then mds crashes, the system frees up the (temporary?) files written by the process and also frees the RAM taken up by it. Resulting in even more swapping, as the system tries to page-in other processes now. Subseqently the system launches a new mds process and the game starts over.
Things I've tried to remedy:
Rebuilt spotlight index several times. Including totally deleting the .Spotlight-V100 folder on local volumes. Doesn't help, takes about 16 to 20 hours to rebuild on my machine, so is not a thing one wants to just-try.
Reinstalled 10.5.5 Combo Update, doesn't help. Privileges are repaired.
Turn off spotlight completely: Does indeed stop the madness, but now I cannot find anything on my system. So this is not a solution at all.
I've tried to keep the index small by excluding more and more stuff in the privacy settings of the Spotlight PreferencePane. This doesn't solve the problem either.
My System:
PowerBook G4 1.5GHz
2GB RAM (Maximum) (Tested with ASD ok, Rember ok. Different RAM modules, also ok.)
160GB HD (5GB free) (SMART ok, Blockscan ok, Filesystem ok, File privileges ok)
Mac OS X 10.5.5 (9F33) including Security Update 2008/007 (no further updates available)
Any help or suggestions are welcome. I'm happy to provide any further details you may need.
Best regards
Pepi

J D McIninch wrote:
This probably isn't Spotlight so much as one of the index plugins (mdimporters). Spotlight itself is very robust, however, all it takes is a single bad indexing plugin. MDS, basically, identifies a file type and loads in a list of plugins that are registered for that file type and executes a routine in the plugin to grab the metadata. If the plugin is improperly written, it can go haywire.
Thanks for the suggestion, I already had checked that.
I don't have any custom (read non-apple provided) Spotlight or QuickLook Plug-Ins on my system. So it is unlikely that it is related to a custom .mdimporter Plug-In. (Might be a buggy Apple one going rampant though.)
I've personally found Spotlight to be quite a solid technology as well. Just the user interface provided by Apple is terrible and especially useless in the Finder (Taking away functionality, or making it horrific to use since Tiger… but that is another story.)
What was the last application that you installed prior to it going crazy? Perhaps one of the last 2-3...
Failing that, you can wipeout the metadata database for a Volume like so (from Terminal.app):
*sudo mdutil -E /Volumes/yourvolumehere*
... or '/' in place of '/Volumes/...' for the local disk. You can turn off metadata indexing for a volume entirely like so:
As I already said, rebuilding the index from scratch doesn't help. Completely deleting it, and rebuilding doesn't remedy as well.
*sudo lsof | grep mdimporter*
... which might help you understand what's being used to index, and this:
/System/Library/Spotlight/Chat.mdimporter/Contents/MacOS/Chat
/System/Library/Spotlight/iCal.mdimporter/Contents/MacOS/iCal /System/Library/Spotlight/Mail.mdimporter/Contents/MacOS/Mail
Nothing fancy here.
I ran a diff on my daily installation report and it gives me these app, that have been modified (Installed or updated in the last 31 days.)
/Applications/Address Book.app
/Applications/Adium.app
/Applications/AppleScript/Script Editor.app
/Applications/Automator.app
/Applications/Carbon Copy Cloner.app
/Applications/Dashboard.app
/Applications/Dictionary.app
/Applications/DVD Player.app
/Applications/Expose.app
/Applications/Flip4Mac/WMV Player.app
/Applications/iCal.app
/Applications/iChat.app
/Applications/iPhoto.app
/Applications/iSync.app
/Applications/iTunes.app
/Applications/JollysFastVNC.app
/Applications/Mail.app
/Applications/OmniFocus.app
/Applications/Photo Booth.app
/Applications/Preview.app
/Applications/Safari.app
/Applications/Skitch.app
/Applications/Spaces.app
/Applications/StuffIt/StuffIt Expander.app
/Applications/StuffIt 12/StuffIt Expander.app
/Applications/Time Machine.app
/Applications/Utilities/Activity Monitor.app
/Applications/Utilities/Bluetooth File Exchange.app
/Applications/Utilities/ColorSync Utility.app
/Applications/Utilities/Directory Utility.app
/Applications/Utilities/Directory.app
/Applications/Utilities/Disk Utility.app
/Applications/Utilities/Keychain Access.app
/Applications/Utilities/Migration Assistant.app
/Applications/Utilities/Network Utility.app
/Applications/Utilities/Podcast Capture.app
/Applications/Utilities/RAID Utility.app
/Applications/Utilities/Remote Install Mac OS X.app
/Applications/Utilities/Terminal.app
/Applications/Utilities/VoiceOver Utility.app
/Applications/Utilities/X11.app
/System/Library/CoreServices/Apple80211Agent.app
/System/Library/CoreServices/AppleFileServer.app
/System/Library/CoreServices/Automator Launcher.app
/System/Library/CoreServices/Automator Runner.app
/System/Library/CoreServices/AVRCPAgent.app
/System/Library/CoreServices/Bluetooth Setup Assistant.app
/System/Library/CoreServices/BluetoothAudioAgent.app
/System/Library/CoreServices/BluetoothUIServer.app
/System/Library/CoreServices/CCacheServer.app
/System/Library/CoreServices/CoreServicesUIAgent.app
/System/Library/CoreServices/DiskImageMounter.app
/System/Library/CoreServices/Dock.app
/System/Library/CoreServices/File Sync.app
/System/Library/CoreServices/FileSyncAgent.app
/System/Library/CoreServices/Finder.app
/System/Library/CoreServices/Help Viewer.app
/System/Library/CoreServices/Installer.app
/System/Library/CoreServices/Kerberos.app
/System/Library/CoreServices/KerberosAgent.app
/System/Library/CoreServices/loginwindow.app
/System/Library/CoreServices/ManagedClient.app
/System/Library/CoreServices/NetAuthAgent.app
/System/Library/CoreServices/Network Diagnostics.app
/System/Library/CoreServices/Network Setup Assistant.app
/System/Library/CoreServices/OBEXAgent.app
/System/Library/CoreServices/ODSAgent.app
/System/Library/CoreServices/PreferenceSyncClient.app
/System/Library/CoreServices/Problem Reporter.app
/System/Library/CoreServices/RemoteManagement/ARDAgent.app
/System/Library/CoreServices/Screen Sharing.app
/System/Library/CoreServices/Spotlight.app
/System/Library/CoreServices/SystemUIServer.app
/System/Library/CoreServices/VerifiedDownloadAgent.app
As you can see, there is nothing special in there as well. Just Apple Apps, and a few non-suspicious ones from my point of view.
Tom in London wrote:
rather than mess around with all of this and maybe fix it until the next Spotlight problem manifests itself, why not just disable Spotlight with Spotless, and use EasyFind instead? Easyfind finds everything, has more options, is reliable, and doesn't cause problems .... and doesn't eat up any space on your hard drive.
...and doesn't find what I need. Thanks for the suggestions though. As I said, totally disabling Spotlight is not an option. I'll stay far away from mysterious tools, as I know what I am doing in a Terminal.
Best regards
Pepi

Similar Messages

HT3576 I have many apps where i must swipe down and it constantly brings down the notification screen. Is there anyway to disable this or activate it a different way because this really bugs me.

I have many apps where i must swipe down and it constantly brings down the notification screen. Is there anyway to disable this or activate it a different way because this really bugs me.

I don't have that problem. Perhaps I touch the screen lower when I wipe down? I don't know for sure but there's got to be some difference in the way that we wipe down. you might wish to do some experimenting.

Spotlight - MDS - Crashing over and over

A few days ago I did a Spotlight search and it froze. Since then my Mac has been Windows unstable. Mail crashes some times, Excel others times, Console, Activity Monitor, Safari, WebKit, iPhoto - all crash now. MDS is running almost constantly and crashes over and over - never finishes. In fact in Console I currently have 27 mds crash logs, 14 in the last hour. The computer is becoming unusable. Oh, no APE etc...
Steps I have taken:
Repair Permissions, verify disk, repair disk, CCCed to a new disk, REinstalled 10.5.4 combo, rerepaired disk, etc. And before I did all the mutil /E type "stuff".
Net net; mds is running and crashing over and over. This seems to be causing other apps to crash as well. Other oddity - most of the time when an application crashes, it does not quit/shutdown - it just is hung in the Not Responding state. Multiple ReportCrash processes will run but never complete and cannot be quit or forced quit - including sudo kill -9. Then the Not Responding application cannot be killed off either and the system will not shutdown - requires hard stop on power.
If this were a DELL I would understand. But this is a Quad Core G5 Mac running 10.5.4 and 4.5 gigs of Apple RAM.
Note - just while writing this, I have 5 more mds crash logs - of of which refer to a KERNPROTECTIONFAILURE and EXCBADACCESS.
Ideas?

Hi Ashler, I think baltwo is right, and you need to reinstall the OS (Archive & Install) because your Spotlight system is "hosed". If you read about the A&I first and perhaps print or write the steps out (very simple, really), I think you will be pleasantly surprised by how easy Apple has made the process. It's nothing as bad as doing a Windows re-install.
But first, we should try to think of the reason for the problem. Have you been running anything that tries to duplicate or otherwise modify the behaviour of Spotlight? In my experience, I have found that everything from Google Desktop to Microsoft Office 2008 have caused Spotlight/indexing/MDS problems on Macs recently. A Spotlight plugin (like any of the .mdimporter plugins from Office, for example) could cause problems; or perhaps Google Desktop's efforts to duplicate Spotlight's services. Or perhaps any other bit of software.
In any case, BEFORE you do the Archive & Install, be sure to go through your main root Library and also your user home Library, and look for items that might be running and causing problems. Also, use Activity Monitor to show all processes and see if there's an app running at startup or login. Then disable the things that might be the cause. Somehow, try to make sure that whatever has got jammed in your system is not going to get transferred by the Archive & Install and end up doing the same thing again when you are done. Try removing the Privacy Spotlight settings and then running from a fresh newly created user account to see if the problem lies with the System as a whole, or just within your own user home folder.
Let us know how you do. Good luck anyway - your Archive & Install will fix you right up.

How to upload files in cluster without bringing down the cluster.

Hi,
Here is my problem:
My weblogic portal 7.0 application should run in 24x7 environment. The production
system is running in a cluster mode with external staging. Both the managed servers
are pointing to the same application sync database.
So to give a solution to this problem, we are trying to bring down one managed
server down and apply the patches into that managed server without bringing down
the other. Since webflow files and entitlements needs to be synchronized with
the portal database. If we perform a sync on the portal database, there might
be a chance that it might corrupt the existing portal database state. Our deployment
would not be complete unless we perform a sync on the other managed servers. So
we could not able to update the latest pathces into the cluster without bringing
down the cluster.
What I would like to know is "Is there any work around to get rid of this problem?".
I would be delighted if any one provides the solution.
Thanks & Regards,
Ratnakar

Hi Ratnakar,
When you perform sync you do it against the admin server which in turn does it
to the managed server. If you want to apply any changes to webflow you can do
it on the live system itself. I mean apply the new webflow and entitlements and
do the sync on the live system. Also while doing sync there are two modes. One
mode will sync only the modified changes and the other will apply all of it. You
can opt for the first option by which you can sync only the modified changes.
This may bring a small disturbance but it will be unnoticed.
The other option is to have two separate domains(each having one admin & one or
more managed servers) which may be having two separate portal databases. In this
way you can apply patches to one domain while other domain may provide the service.
Regards
Shaan
"Ratnakar Sonti" <[email protected]> wrote:
>
Hi,
Here is my problem:
My weblogic portal 7.0 application should run in 24x7 environment. The
production
system is running in a cluster mode with external staging. Both the managed
servers
are pointing to the same application sync database.
So to give a solution to this problem, we are trying to bring down one
managed
server down and apply the patches into that managed server without bringing
down
the other. Since webflow files and entitlements needs to be synchronized
with
the portal database. If we perform a sync on the portal database, there
might
be a chance that it might corrupt the existing portal database state.
Our deployment
would not be complete unless we perform a sync on the other managed servers.
So
we could not able to update the latest pathces into the cluster without
bringing
down the cluster.
What I would like to know is "Is there any work around to get rid of
this problem?".
I would be delighted if any one provides the solution.
Thanks & Regards,
Ratnakar

Spotlight (mds) crashes after running TimeMachine

Hi!
As other posted in this forum I faced several freeze ups after running TimeMachine. I had a closer look into the console logs and found the process "mds" (meta data search aka Spotlight) crashes after every backup performed by TimeMachine:
===== cut =====
Process: mds [22]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
Identifier: mds
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1]
Date/Time: 2007-11-19 19:48:46.771 +0100
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x000000000000047c
Crashed Thread: 5
===== cut =====
It's always thread no. 5. My next try will be to disable Spotlight, but has anybody the same problem?
Mattes

I googled some posts in the net, e. g. <http://automators.net/news/macosxhints-com/10-5-disable-spotlight-completely/> about disabling Spotlight, but tried a less intrusive way: First by dragging the backup volume in the Privacy tab (Spotlight system preferences), but the mounted network share wasn't selectable. So my second try was running "sudo mdutil -i off <volume>".
Sorry guys, I should have mentioned that my TimeMachine backup is located on an AEBS-attached USB drive (TM's unsupported network device) and Spotlight seems to have problems with this volume (not the mounted sparse image) ...
Mattes
Message was edited by: Matthias Arndt

Running ios5.1.1 on original iPad. system constantly crashes and returns to home page when on the web. using safari.

Running IOs 5.1.1 on original Ipad. System constantly crashes returning to the home screen when in internet. Using Safari browser. is there anything I can upgrade or clear to help??

There are a few things that you could try. First try clearing Safari's cache : Settings > Safari > Clear Cookies And Data and also Clear History
If that doesn't work then try closing Safari completely and then re-open it : from the home screen (i.e. not with Safari 'open' on-screen) double-click the home button to bring up the taskbar, then press and hold any of the apps on the taskbar for a couple of seconds or so until they start shaking, then press the '-' in the top left of the Safari app to close it, and touch any part of the screen above the taskbar so as to stop the shaking and close the taskbar.
A third option is a reset : press and hold both the sleep and home buttons for about 10 to 15 seconds (ignore the red slider), after which the Apple logo should appear - you won't lose any content, it's the iPad equivalent of a reboot.

ASE instance not available *** ERROR:ASE instance possibly left running when system went down(system crash?). Notify Database Administrator

Hi Gurus,
I made some changes in rz10 for client copy like:
icm/host_name_full [email protected]
login/accept_sso2_ticket 1
login/create_sso2_ticket 2
icm/server_port_1
PROT=HTTPS,PORT=443$$,PROCTIMEOUT=600,TIMEOUT=600
icm/server_port_0
PROT=HTTP,PORT=80$$,PROCTIMEOUT=600,TIMEOUT=600
login/no_automatic_user_sapstar 0
After to make changes effective, i stopsap & startsap.
But unfortunately db is not coming up. I checked startdb.log it showing
error as " ASE instance not available
*** ERROR:ASE instance possibly left running when system
went down(system crash?).
Notify Database Administrator."
Please help us to resolve this issue, i have also added startdb.log for
your reference.
Regards,
Piyush

Hi Piyush,
Did you solved this issue.
We are facing the same issue and only this thread is there in SCN for this issue.
If you solved this issue,Kindly share the solution.
Thanks and Regards,
Mathan A

Best solution for bringing new systems up to date with software updates

I have read that I can create a non-deployed software update group that contains previous months patches and use that for reporting purposes to find out which systems do not have all the updates, but that is where my understanding falls short.
For some reason I am not getting how I can update new systems with all the updates before its existence in a domain, wrapped around my brain.
Can someone help me get this through my noggin please?
Thank you

I understand how to deploy SUGs to a dynamic collection.
This is my dilemma:
I currently piloting SCCM 2012 and bringing new systems into SCCM 2012 every 2 weeks to a month
I have a monthly Patch Tuesday ADR configured that creates the SUG, but does not enable deployment, so I can ensure everything is in order before I enable it
I then enable the deploy and target a collection that includes all of my pilot collections that consist of computers from remote sites so I do not have to deploy a SUG to each collection\
Now this works great for me, BUT many of these systems that I bring into SCCM 2012 every 2 weeks to a month do not have the patches installed on them, so I am trying to understand how I am supposed to get all of those previous patches deployed to them.
Can you tell me if this solution would work:
Put previous month's patches in a non-deployed compliance SUG and name it something like "2014 - Compliance Reporting" and use that for reporting purposes.
Create another SUG and name it something like "2014 - Compliance Deployment". Then deploy the "2014 - Compliance Deployment" SUG to a collection containing systems that do not have the updates installed on them from the "2014
- SUM Compliance Deployment" SUG.
OR
Do I just simply deploy the "2014 - SUM Compliance Deployment" SUG without running any report and let the clients figure out what to install?
OR
Do I tell the remote site admins to manually update the system by going to the Windows Update site and after that, allow SCCM to take over after the systems have all been updated that way?

WLS -JDBC sql server 2005, if sql server down bringing down entire cluster

Hi ,
From 4 WLS we connect to 4 indivudual SQL Servers 2005 (non clustered) , if one sql server goes down it is bringing down the 4 WLS servers. Tried all the possible parameter tuning in WLS nothing helped.
Is there any solution, if there is one sql server down can we mark the bad sql server down and don't create STUCK threads to all 4 WLS.
Thanks
Manu

Hi Weinstein,
when one sql server went down we saw the SQL server SHUTDOWN in progress. We use the DRIVER weblogic.jdbc.sqlserver.SQLServerDriver. When one server is going down connection pool is keep going to the same server and creating stuck threads.
<Info> <JDBC> <[ACTIVE] ExecuteThread: '150' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1327597605889> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: [OWLS][SQLServer JDBC Driver][SQLServer]SHUTDOWN is in progress.
     at weblogic.jdbc.sqlserverbase.BaseExceptions40.createAppropriateSQLExceptionInstance(Unknown Source)
     at weblogic.jdbc.sqlserverbase.BaseExceptions40.createSQLException(Unknown Source)
     at weblogic.jdbc.sqlserverbase.BaseExceptions.createException(Unknown Source)
     at weblogic.jdbc.sqlserverbase.BaseExceptions.getException(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSLoginRequest.submitRequest(Unknown Source)
     at weblogic.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at weblogic.jdbc.sqlserverbase.BaseConnection.doConnect(Unknown Source)
     at weblogic.jdbc.sqlserverbase.BaseConnection.connect(Unknown Source)
     at weblogic.jdbc.sqlserverbase.BaseConnection.setupImplConnection(Unknown Source)
     at weblogic.jdbc.sqlserverbase.BaseConnection.open(Unknown Source)
     at weblogic.jdbc.sqlserverbase.BaseDriver.connect(Unknown Source)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:320)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:412)
     at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1717)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1606)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1507)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496)
     at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:1942)
     at weblogic.common.resourcepool.ResourcePoolImpl.access$800(ResourcePoolImpl.java:40)
     at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2368)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
In .net they have Retry Wait and connection will not go to the failed server until certain time, do we have any parameters like this in weblogic connection pool.
http://support.microsoft.com/kb/169470
1.     Q. With ODBC 3.0 Service Pack 1, will the ODBC driver manager try to connect to the database server repeatedly when the server is not available?
A. ODBC 3.0 Service Pack 1 introduced a new API, ODBCSetTryWaitValue, to prevent the ODBC driver manager from connecting to an unavailable server repeatedly. ODBCSetTryWaitValue takes a DWORD parameter and saves the information in the registry at the following location:
HKEY_LOCAL_MACHINE\Software\Odbc\Odbcinst.ini \ODBC Connection Pooling\Retry Wait
Once the diver manager detects a bad database server, it returns an error message and marks the connection with the time. From that point until the RetryWait value expires, the driver manager returns a failure without trying to reconnect to the database server
Thanks for your help.
Thanks
Manu

Network outage don't bring down layer3 isdn

Hi Everyone,
Just wondering if someone ran through this case over the years...
Scenario :
2 routers in mgcp with 1 T1 on each. The DMS switch cascade the calls to the second T1 if the first one fail.
In a case you lose network connectivity on the first router, thus having the mgcp in a down state the calls should go to the second T1 but having mgcp down doesn't bring down the layer3 on the isdn link... I still ses the isdn status as MULTIFRAME ESTABLISHED...
I tried the busyout command but this only put channels in a busy state ... the first T1 still receive the incomming calls thus not cascading...
Anyone have an idea of what I could do to make the isdn link go down when the mgcp go dwon as well ?

Look into busy-out monitor feature:
http://www.cisco.com/en/US/docs/ios/12_0t/12_0t7/feature/guide/busy_t7.html#wp30177
HTH,
Chris

HT1338 Unable to shut down - won't close down system preferences

Unable to shut down - won't allow me to close down system preferences

Hello jdreed3,
The error message you are receiving is usually because of a failing hard drive. Can you go into the BIOS and run hard drive tests?
Here is a similar thread in regards to the same issue where the user discovered it was indeed the hard drive that has fried that has been giving him the issues.
recieving a 0x4001100200000100a when using the factory recovery DVDs
If I have helped you in any way click the Kudos button to say Thanks.
The community works together, click Accept as Solution on the post that solves your issue for other members of the community to benefit from the solution.
- Friendship is magical.

HT201365 I just downloaded IOS 7. In my old software if I wanted to get to spotlight to find something I just scrolled from left to right from my home screen. That doesn't work now...so how the heck to I get to spotlight with this new system???

I just upgraded to IOS 7. Prior to that upgrade if I wanted to get to spotlight search I just scrolled left to right from my home page and got it. Now...that doesn't work. How do I get to spotlight/search with IOS 7? Sheesh...why change such an easy basic thing anyway??? Can someone let me know please.

Now, you get to Spotlight by swiping down from the home screen, but do not start the swipe at the top of the screen. Start it in the middle somewhere.

ArchTaz Live: boot and run an Arch system entirely in RAM

ArchTaz Live Boot: A method to boot and run an Arch system entirely in RAM using tmpfs.
As the name suggests it was inspired by (copied entirely from) SliTaz http://www.slitaz.org/ and boots in exacly the same way.
It needs a custom init script in the root directory and for some reason that I can't work out a hook for sysinit_premount in rc.sysinit to remount / rw.
The /usr/bin/archfs script is just a chunk of Slitaz's Tazusb utility with some minor changes (and I haven't properly tested the lzma or no compression).
The /init script is modified from the usual initramfs /usr/lib/initcpio/init with hints from the SliTaz /init script (and some personal additions for my system).
Copy init to the root directory, run archfs (eg. # archfs writefs gzip) and move the resulting archfs.gz to your boot partition/directory and boot with archfs.gz as your initrd.
I run a fairly light system (Openbox, Firefox, Gnome-Mplayer, SpaceFM, no dev packages) and gzip compression gives me an archfs.gz just over 230MB that boots in just over 30 seconds using 138MB RAM on startup, and most applications start instantly (2GHz Core2Duo, 4G RAM). Lzma compression generally gives a smaller archfs.gz but takes longer to boot. I have a persistent home partition, I install packages as I need them and then they're gone on next reboot if I don't do a new archfs.gz to keep them. I delete man pages, unneeded locales, etc. Obviously if you're running a hefty install on a limited box you may run into problems.
Any tips, cleanups, corrections welcome. It's been a mostly copy and paste and mash stuff together process so it isn't neat. And I think I may need some serious help when systemd becomes default.
/usr/bin/archfs:
#!/bin/sh
# Archfs - entirely copied from part of the Tazusb utility supplied with
# SLiTaz GNU Linux - with some cosmetic changes.
### Tazusb - SliTaz LiveUSB
### Tazusb is an utility to generate, configure and manipulate SliTaz LiveUSB
### bootable media and/or USB /home partition, such as flash keys, SD card or
### USB harddisk.
### Authors : Christophe Lincoln (Pankso) <[email protected]>
### Andrew Miller (Spode) <[email protected]>
COMMAND=$1
case $COMMAND in
writefs)
# Writefs to rootfs.gz
if [ -z $2 ]; then
COMPRESSION=none
else
COMPRESSION=$2
fi
# Start info
echo ""
echo -e "\033[1mWrite filesystem\033[0m
===============================================================================
The command writefs will write all the current filesystem into a suitable cpio
archive (rootfs.gz) usable on a bootable LiveUSB media.
Archive compression: $COMPRESSION"
echo ""
# Create list of files
find /bin /etc /init /sbin /var /lib /lib64 /root /usr >/tmp/list
for dir in /boot /dev /home /proc /sys /tmp /mnt /media /run
do
echo $dir >>/tmp/list
done
# Generate initramfs with specified compression
if [ "$COMPRESSION" = "lzma" ]; then
echo -n "Creating archfs.gz with lzma compression... "
cat /tmp/list | cpio -o -H newc | lzma > /archfs.gz
elif [ "$COMPRESSION" = "gzip" ]; then
echo -n "Creating archfs.gz with gzip compression... "
cat /tmp/list | cpio -o -H newc | gzip -9 > /archfs.gz
else
echo -n "Creating archfs.gz without compression... "
cat /tmp/list | cpio -o -H newc > /archfs.gz
fi
# Get initramfs size
size=`du -sh /archfs.gz | cut -f 1`
echo "==============================================================================="
echo "Root filesystem size: $size"
echo ""
echo -en "----\nENTER to continue..."; read i
esac
exit 0
/init:
#!/bin/bash
PATH=/bin:/usr/bin:/usr/sbin:/sbin
udevd_running=0
if [ -x /usr/bin/systemd-timestamp ]; then
RD_TIMESTAMP=$(systemd-timestamp)
fi
. /usr/lib/initcpio/init_functions
mount -t proc proc /proc -o nosuid,noexec,nodev
mount -t sysfs sys /sys -o nosuid,noexec,nodev
mount -t devtmpfs dev /dev -o mode=0755,nosuid
mount -t tmpfs run /run -o nosuid,nodev,mode=0755
mkdir -m755 /run/initramfs
# parse the kernel command line
parse_cmdline
for d in ${disablehooks//,/ }; do
[ -e "/hooks/$d" ] && chmod 644 "/hooks/$d"
done
#. /config
run_hookfunctions 'run_earlyhook' 'early hook' $EARLYHOOKS
[ -n "${earlymodules//[[:space:]]}" ] && modprobe -qab ${earlymodules//,/ }
[ -n "${MODULES//[[:space:]]}" ] && modprobe -qab $MODULES
# If rootdelay is empty or not a non-negative integer, set it to 10
if [ -z "${rootdelay}" ] || ! [ "${rootdelay}" -ge 0 ]; then
rootdelay=10
fi
run_hookfunctions 'run_hook' 'hook' $HOOKS
# honor the old behavior of break=y as a synonym for break=premount
if [ "${break}" = "y" ] || [ "${break}" = "premount" ]; then
echo ":: Pre-mount break requested, type 'exit' to resume operation"
launch_interactive_shell
fi
rootdev=$(resolve_device "$root") && root=$rootdev
unset rootdev
#fsck_root
# Make /new_root
mkdir /new_root
# Mount root at /new_root
#${mount_handler:-default_mount_handler} /new_root
echo -e "Switching / to tmpfs..."
mount -t tmpfs tmpfs /new_root
run_hookfunctions 'run_latehook' 'late hook' $LATEHOOKS
run_hookfunctions 'run_cleanuphook' 'cleanup hook' $CLEANUPHOOKS
# Stop udevd if is running
if [ "${udevd_running}" -eq 1 ]; then
udevadm control --exit
udevadm info --cleanup-db
fi
# Copy root
echo -e "Copying root..."
for i in $(ls -a /); do
case "$i" in
.|..) ;;
mnt) mkdir /new_root/mnt;;
proc) mkdir /new_root/proc;;
sys) mkdir /new_root/sys;;
dev) mkdir /new_root/dev;;
run) mkdir /new_root/run;;
new_root) ;;
*) cp -a /$i /new_root
esac
done
# Create mountpoints
mkdir /new_root/mnt/sda1
mkdir /new_root/mnt/sda2
mkdir /new_root/mnt/sda3
mkdir /new_root/mnt/sda4
init=${init:-/sbin/init}
echo -e "Switching root..."
exec env -i \
"TERM=$TERM" \
"RD_TIMESTAMP=$RD_TIMESTAMP" \
/sbin/switch_root /new_root $init "$@"
## Mount root at /new_root
#${mount_handler:-default_mount_handler} /new_root
#run_hookfunctions 'run_latehook' 'late hook' $LATEHOOKS
#run_hookfunctions 'run_cleanuphook' 'cleanup hook' $CLEANUPHOOKS
init=${init:-/sbin/init}
if [ "$(stat -c %D /)" = "$(stat -c %D /new_root)" ]; then
# Nothing got mounted on /new_root. This is the end, we don't know what to do anymore
# We fall back into a shell, but the shell has now PID 1
# This way, manual recovery is still possible.
err "Failed to mount the real root device."
echo "Bailing out, you are on your own. Good luck."
echo
launch_interactive_shell --exec
elif [ ! -x "/new_root${init}" ]; then
# Successfully mounted /new_root, but ${init} is missing
# The same logic as above applies
err "Root device mounted successfully, but ${init} does not exist."
echo "Bailing out, you are on your own. Good luck."
echo
launch_interactive_shell --exec
fi
if [ "${break}" = "postmount" ]; then
echo ":: Post-mount break requested, type 'exit' to resume operation"
launch_interactive_shell
fi
exec env -i \
"TERM=$TERM" \
"RD_TIMESTAMP=$RD_TIMESTAMP" \
/sbin/switch_root /new_root $init "$@"
# vim: set ft=sh ts=4 sw=4 et:
/etc/rc.d/functions.d/root_rw:
root_rw() {
mount -o remount,rw /
add_hook sysinit_premount root_rw
archfs:
http://pastebin.com/RNTDWhFc
init:
http://pastebin.com/n4vcqG62
root_rw:
http://pastebin.com/i1LV61SV
Last edited by 0ddba11 (2012-12-30 10:12:35)

Oh yes any man directory was symlinked to /tmp long ago, so they don't even get installed.
Right, new boot process:
Using hooks in normal initramfs-linux.img to unpack archfs.gz into tmpfs and boot it.
Create an initcpio preset file /etc/mkinitcpio.d/archfs.preset:
# mkinitcpio preset file for the 'archfs' package
ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux"
PRESETS=('archfs')
archfs_config="/etc/mkinitcpio.conf"
archfs_image="/boot/archfs-linux.lzo"
archfs_options="-S fsck -A tmpfs -z lzop"
Or append to the standard 'linux.preset' file so the initramfs is created automatically when you upgrade your kernel. Or alter /etc/mkinitcpio.conf to add options.
Create the file /lib/initcpio/hooks/tmpfs:
#!/usr/bin/ash
run_latehook() {
# Mount tmpfs root
mount -t tmpfs tmpfs /mnt
# Unpack rootfs
msg "Unpacking rootfs..."
cd /mnt
# parse the kernel command line
parse_cmdline
for archfs in ${archfs//,/ }; do
if [ "$archfs" = "xz" ]; then
xz -d < /new_root/boot/archfs.xz | cpio -imd --no-absolute-filenames > /dev/null 2>&1
elif [ "$archfs" = "gzip" ]; then
gzip -dc /new_root/boot/archfs.gz | cpio -imd --no-absolute-filenames > /dev/null 2>&1
elif [ "$archfs" = "lzo" ]; then
lzop -d < /new_root/boot/archfs.lzo | cpio -imd --no-absolute-filenames > /dev/null 2>&1
elif [ "$archfs" = "img" ]; then
cpio -imd --no-absolute-filenames /new_root/boot/archfs.img > /dev/null 2>&1
fi
done
# Switch tmpfs to new root
umount /new_root
mount -M /mnt /new_root
# vim: set ft=sh ts=4 sw=4 et:
And the file /lib/initcpio/install/tmpfs:
#!/bin/bash
build() {
add_dir /mnt
add_module ext3
add_binary cpio
add_binary xz
add_binary gzip
add_binary lzop
add_binary fsck.ext4
add_symlink /usr/bin/fsck.ext2 fsck.ext4
add_symlink /usr/bin/fsck.ext3 fsck.ext4
add_runscript
help() {
cat <<HELPEOF
This hook creates the tmpfs root, mounts the device that contains the
rootfs and extracts it into the tmpfs root.
HELPEOF
# vim: set ft=sh ts=4 sw=4 et:
This loads modules and fsck binaries for the filesystem of my /boot partition into the initramfs. It also adds all the relevant compression binaries (some which can also be compiled into busybox or left out if not needed). I'm working on automatically reading the filesystem from your /boot partition based on the "root=" kernel command line option and adding the appropriate modules.
Create a new archfs.gz (or new extensions) with new cleaned up /usr/bin/archfs:
http://pastebin.com/xiqgyYyL
Now run with:
# archfs lzo
(or whichever crompression you choose). It also takes care of any mounting directories you have in /mnt. And "writefs" is no longer needed, that's all it does anyway.
Then simply add the "root=(your boot partition)" and "archfs=lzo" (or whichever compression you chose) command line options to your grub.cfg.
Run:
# mkinitcpio -p archfs
That'll create an initramfs: archfs-linux.lzo that you need to move to your boot partition with your kernel and archfs.gz. Then point grub to that as your initrd.
This will boot and the tmpfs hook will do it's work just after init has mounted your boot partition and then init will switch roots and run /sbin/init as it would on any normal install.
Mix and match as needed. You can remove the /init file from the root of your filesystem or leave it there and all but an xz compressed archfs.gz will boot the old way aswell (the kernel can't handle the xz version). It should all be fairly upgrade proof, barring any major changes to mkinitcpio.
Boot for me with lzo compression is at least twice as fast as old method. Partly due to lzo compression which is super fast (especially creating the archfs.lzo). It makes for a bigger file but it's still only 350MB (pretty much half my uncompressed root filesystem).

Does adding 100Mbps Switch bring down the speed of a 1000Mbps network?

I have a wired Airport Extreme network where a 1000Mbps Ethernet switch in one room adds connections to other peripherals.
Now I want to add a switch in a different room for wired connections that are now operating wirelessly. And I have available a 10/100Mbps Ethernet switch. If I add that to the network do I bring down the speed of the entire thing? I realize that the connections directly from that 2nd switch can only be 100Mbps.
But will I affect the speed of the other connections?
Thanks in advance.

And I have available a 10/100Mbps Ethernet switch. If I add that to the network do I bring down the speed of the entire thing?
No
I realize that the connections directly from that 2nd switch can only be 100Mbps.
Correct

My MBP is bringing down network connections

When I connect my MBP either by ethernet cable or wireless I eventually bring down the network. I've connected to different networks with different routers and I always get the same result. After a brief period of time I lose my internet conncetion and I can't even communicate with the router. The router needs to be reset in many cases before it recovers. I have posted this issue before and the response was that it really couldn't be the Mac. However, once I tried connecting to other networks and got the same results I became certain that it is due to my computer. Is there anyway that I could be sending some corrupt packet? Hardware is failing? Is there a way to nuke all network settings and have it start from scratch w/o putting on a fresh install?

I found a solution that seems to work for the linksys WRT54GS v.6 router. Apparently many others have had the same issues with this brand. Under router settings I disabled UPnP and limited the MTU to 1480. Everything seems to work so far, knock on wood.

Spotlight mds bringing down system, constantly leaking RAM & disk access

Similar Messages

Maybe you are looking for